expo/troggle
2
0
Fork 1
mirror of https://expo.survex.com/repositories/troggle/.git synced 2025-12-17 06:27:34 +00:00
Code Issues 18 Projects 3 Activity

comments

Browse Source
This commit is contained in:
Philip Sargent
2024-12-15 21:59:54 +00:00
parent a836dd2619
commit e532b15c1d
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
core/models/caves.py
View File

@@ -25,6 +25,8 @@ Gcave_count = None
todo = """
- Why do we have CaveAndEntrance objects ? These do not need to be explcit for a many:many relationship these days
now only used to create a <form> for entranceletter
TO DO move entranceletter to Entrance
- Restore constraint: unique_together = (("area", "kataster_number"), ("area", "unofficial_number"))
or replace by a unique 'slug' field, better.
@@ -32,11 +34,11 @@ todo = """
class CaveAndEntrance(models.Model):
"""This class is ONLY used to create a FormSet for editing the cave and all its
entrances in one form.
"""This class is ONLY used to create a FormSet for editing the entranceletter.
CASCADE means that if the cave or the entrance is deleted, then this CaveAndEntrance
is deleted too
NOT NEEDED anymore if we insist that cave:entrances have 1:n multiplicity.
TO DO move entranceletter to Entrance
"""
cave = models.ForeignKey("Cave", on_delete=models.CASCADE)
entrance = models.ForeignKey("Entrance", on_delete=models.CASCADE)