#259 closed defect (fixed)
Update order problem when changing DateTimeZero while having autoscale off
Reported by: | ghorwin | Owned by: | ghorwin |
---|---|---|---|
Priority: | critical | Milestone: | 2.3.0 |
Version: | 2.2.x | Keywords: | |
Cc: | Operating System: | all |
Description (last modified by )
Steps to reproduce:
- enable DateTime
- disable autoscale
DateTimeZero = 1.1.2001 Min = 1.1.2001 Max = 1.1.2002
- change DateTimeZero to 1.1.2002
Min/Max times are adjusted correctly
- change DateTimeZero to 1.1.2000 (the default value)
MinMax times are kept and thus become invalid when DateTimeZero is changed next
Change History (6)
comment:1 by , 4 years ago
Description: | modified (diff) |
---|
comment:2 by , 4 years ago
comment:3 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Diagnosis:
Die Spezialbehandlung "Wenn DateTimeZero noch Standardwert, dann liefere das Startjahr des Datensatzes zurück" darf nicht angewendet werden, wenn bereits einmal das DateTimeZero verändert wurde und entsprechend die Minimum/Maximum-Werte angepasst wurden.
Lösungsideen: