From 8c56a45e7c89f580afc59f670443bc1eb9812e36 Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Tue, 10 Dec 2024 20:09:25 +0000 Subject: preserving expoer order in logbook entries attempt 1 --- core/models/logbooks.py | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'core/models/logbooks.py') diff --git a/core/models/logbooks.py b/core/models/logbooks.py index 326a097..5b6c469 100644 --- a/core/models/logbooks.py +++ b/core/models/logbooks.py @@ -136,8 +136,8 @@ def writelogbook(year, filename): # print(f'Logbook exported to {filepath}') class PersonLogEntry(TroggleModel): - """Single Person going on a trip, which may or may not be written up. - It could account for different T/U for people in same logbook entry. + """Single Person going on a trip. + In future it could account for different T/U for people in same logbook entry. CASCADE means that if the personexpedition or the logbookentry is deleted, then this PersonLogEntry is deleted too @@ -150,8 +150,11 @@ class PersonLogEntry(TroggleModel): nickname_used = models.CharField(max_length=100,default="") # e.g. "Animal" or "Zonker", as it appears in the original logbook class Meta: - ordering = ("-personexpedition",) - # order_with_respect_to = 'personexpedition' + ordering = ("nickname_used", "-personexpedition") + # order_with_respect_to = 'personexpedition' and then with nickname + # within the same logbook entry (which will always be the same expedition) this will + # now not re-order the participants in a trip every time we save the logbook. + # but this does not work.. need a function def next_personlog(self): futurePTs = ( -- cgit v1.2.3