... | ... | @@ -58,7 +58,7 @@ These variables are known to influence the final accuracy: |
|
|
|
|
|
* __For un-edited `Event` records__: The MySQL server has a default timezone (_either stored in its configuration or inherited from the operating system_). This timezone influences accuracy of _un-edited_ records:
|
|
|
* If the default timezone has __remained the same__, these records should convert __correctly+automatically__.
|
|
|
* If the default timezone has __changed__ (e.g. due to server-migration), these records will convert __incorrectly__.
|
|
|
* If the default timezone has __changed__ (e.g. due to server-migration, or daylight savings), these records will convert __incorrectly__.
|
|
|
* __For recently edited `Event` records__: Editing an event in the web UI may have created an error of +/- 1 hour. This depends on the intended date and the schedule for "Daylight Savings Time" (DST). In 2022, there are DST transitions on March 13 (US+CA), March 27 (EU), and April 2 (AU+NZ).
|
|
|
* If the DST schedule is __consistent among users__ (_the web-user who runs the upgrade has the same DST schedule as all other web-users_), then `Event`s are likely to convert __correctly+automatically__.
|
|
|
* If the DST schedule is __inconsistent among users__ (_some web-users have March 27 and others April 2_), then `Event`s may still have a __+/- 1 hour error__.
|
... | ... | |