Adminer uses wrong timezones when exporting data. Numeric specification of timezone breaks TIMESTAMP columns. Correct value is for example 'Europe/Prague', never '+01:00'.
The string time zones may not be available on the target server. Can you specify what do you mean by "breaks TIMESTAMP columns"? What happens to them?
In timezones with daylight saving the offset changes twice a year. When you specify time half of a year in future, you must convert it to another timezone. When timezone is specified using numeric offset, this does not happen. For example if you set alarm today (2014-02-14) to ring at 2014-06-01 12:00:00 and store it in TIMESTAMP column using "+01:00" timezone, it will ring at 2014-06-01 11:00:00, because in summer the timezone will be "+02:00". But if you store the same date in "Europe/Prague" timezone, it will be stored using "+02:00" offset (even if current offset is "+01:00") and alarm will ring at 12:00 as expected.
If string timezones are not available, Adminer should consider the database server broken, switch to UTC and show big fat warning with link to manual.
I've solved it by setting the timezone to +00:00 both in the connection and in the dump.
Setting +00:00 will not corrupt data, so it is good as a fallback, but ... see https://github.com/jkufner/adminer/commit/2ba1640ac9be423473e098fe7203c4d5f95e977b
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.