expo/troggle
2
0
Fork 1
mirror of https://expo.survex.com/repositories/troggle/.git synced 2026-02-12 23:29:04 +00:00
Code Issues 18 Projects 3 Activity

to-do comments updated

Browse Source
This commit is contained in:
Philip Sargent
2024-07-15 12:41:58 +02:00
parent 11756fa0bb
commit 2cb665e141
3 changed files with 0 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
core/models/caves.py
View File

@@ -25,16 +25,7 @@ Gcave_count = None
"""
todo = """
- Find out why we have separate objects CaveSlug and why
these are not just a single field on the Model. This was Martin's idea,
but we are using text aliases now so we only need one slug in the data model
- Can we rewrite things to eliminate the CaveSlug and objects? Surely
foreign keys work fine ?!
- Why do we have CaveAndEntrance objects ? These do not need to be explcit for a many:many relationship these days
- move the aliases list from the code and put into an editable file
- Restore constraint: unique_together = (("area", "kataster_number"), ("area", "unofficial_number"))
or replace by a unique 'slug' field, better.

4
core/models/logbooks.py
View File

@@ -15,10 +15,6 @@ from troggle.core.models.troggle import Expedition, TroggleModel
"""
todo = """
Foreign keys do not allow for there being multiple ways to refer to a cave, eg 1623-1999-03 aka 1623-204
Having slugs allows for much more loose coupling to caves, which removes alot of the need to reset the database, which interupts work flow.
It also means we do not have to be creating temporary cave objects in the database, where we do not have the underlying file in cave_data.
"""