You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have numerous inconsistencies related to partial date & time information in unicsv.
Perhaps we should store a date only as an invalid QDateTime with a valid QDate, and invalid QTime, and an indeterminate Qt::TimeSpec.
Perhaps we should store a time only as an invalid QDateTime with a invalid QDate, a valid Qtime, and an indetrminate Qt::TimeSpec.
unicsv interprets a date only as relative to UTC start of day and displays it translated to local time.
unicsv interprets a date and time as relative to local time.
unicsv regards zero time without date as invalid.
unicsv echos a non zero time without date as relative to the unix epoch and displays it translated to local time.
a date alone is interpreted as UTC start of day.
a date and time is interpreted as local
a time alone is interpreted as relative to the unix epoch
We have numerous inconsistencies related to partial date & time information in unicsv.
Perhaps we should store a date only as an invalid QDateTime with a valid QDate, and invalid QTime, and an indeterminate Qt::TimeSpec.
Perhaps we should store a time only as an invalid QDateTime with a invalid QDate, a valid Qtime, and an indetrminate Qt::TimeSpec.
unicsv interprets a date only as relative to UTC start of day and displays it translated to local time.
unicsv interprets a date and time as relative to local time.
unicsv regards zero time without date as invalid.
unicsv echos a non zero time without date as relative to the unix epoch and displays it translated to local time.
a date alone is interpreted as UTC start of day.
a date and time is interpreted as local
a time alone is interpreted as relative to the unix epoch
The text was updated successfully, but these errors were encountered: