diff options
| author | Edward Welbourne <edward.welbourne@qt.io> | 2023-03-31 11:40:42 +0200 |
|---|---|---|
| committer | Thiago Macieira <thiago.macieira@intel.com> | 2023-04-14 13:23:50 +0000 |
| commit | 76075aa3a96c05afd2f6877af5b612adec325bb2 (patch) | |
| tree | eabd4b6dbe0d19bd71cb1e5ba0f8d57a1361c2e2 /src/sql/doc/snippets/sqldatabase | |
| parent | b906796af62fb23e592625c7c86b31c98a08162b (diff) | |
QDate: enable {start,end}OfDay() to make second-adjustments
Previously it only got the answer correct to the minute. That's good
enough for most transitions, but those involving local solar mean time
(LMT) may have second deviations. So check the second before or after,
that'll usually be the other side of the transition; if it isn't, do a
further binary chop on seconds to hit the correct value.
Most zones' canonical locations are only specified to the size of a
city, so second precision is all anyone cares about; a few hundred
metres difference in location would change that. The one exception is
Europe/Amsterdam, which had its own Royal Observatory and time
standard, hence had an offset known to greater precision; but the IANA
DB duly approximates that, too, so we won't have data with millisecond
precision even in that case, so don't try to refine beyond second.
Change-Id: I20fb355f8113c32387ed8a84fbf5a41004273978
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Konrad Kujawa <konrad.kujawa@qt.io>
Diffstat (limited to 'src/sql/doc/snippets/sqldatabase')
0 files changed, 0 insertions, 0 deletions
