From e532b15c1d48947c6934995ed470e81293949de8 Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Sun, 15 Dec 2024 21:59:54 +0000 Subject: comments --- core/models/caves.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'core/models/caves.py') diff --git a/core/models/caves.py b/core/models/caves.py index 12941d0..f1dd769 100644 --- a/core/models/caves.py +++ b/core/models/caves.py @@ -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
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) -- cgit v1.2.3