expo/troggle
2
0
Fork 1
mirror of https://expo.survex.com/repositories/troggle/.git synced 2024-11-22 07:11:52 +00:00
Code Issues 19 Projects 3 Activity

More todos

Browse Source
This commit is contained in:
Philip Sargent 2023-02-08 23:37:00 +00:00
parent 28f87e82e9
commit 0740f9ea5a
2 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
core/models/caves.py
View File

@ -28,6 +28,11 @@ todo = """
these are not just a single field on the Model. Do we ever need more these are not just a single field on the Model. Do we ever need more
than one slug per cave or entrance? Surely that would break everything?? than one slug per cave or entrance? Surely that would break everything??
- Can we rewrite things to eliminate the CaveSlug and EntranceSlug Classes and objects? Surely
foreign keys work fine ?!
- Why do we have CaveAndEntrance objects ? Surely entranceletter belong son the Entrance object?
- Restore constraint: unique_together = (("area", "kataster_number"), ("area", "unofficial_number")) - Restore constraint: unique_together = (("area", "kataster_number"), ("area", "unofficial_number"))
""" """

2
core/models/logbooks.py
View File

@ -11,6 +11,8 @@ from troggle.core.models.troggle import Expedition, TroggleModel
""" """
todo = """ todo = """
- Can we rewrite things to eliminate the CaveSlug and EntranceSlug Classes and objects? Surely
foreign keys work fine ?!
""" """