Modify ↓
Opened 8 years ago
Last modified 5 years ago
#12893 new defect
Empty time values should be stored as NULL
| Reported by: | Ryan J Ollos | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-dev-1.7.x |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
Empty time values in the ticket system are stored as 0. They should probably be stored as NULL instead. Example: Version.update
sqlite> SELECT time FROM version; 0 1496041616000000 1472327798000000 0 0
The issue is caused by behavior of to_utimestamp. We should add a helper function:
def _to_timestamp(time): return to_utimestamp(time) if time else None
Timestamps are stored in the following fields:
attachment.timewiki.timerevision.timeticket.timeticket.changetimeticket_change.timemilestone.duemilestone.completedversion.timenotification_subscription.timenotification_subscription.changetime
Attachments (0)
Change History (5)
comment:1 by , 8 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 6 years ago
comment:4 by , 6 years ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.



See also comment:20:ticket:11018. Empty time ticket custom field values are stored as NULL rather than an empty string.