[EMAIL PROTECTED] wrote:
>Ralf Junker <[EMAIL PROTECTED]> wrote:
>> SQLite does not recognize "Z" as the zero offset time zone specifier.
>
>SQLite does not currently accept any timezone specifiers, other
>than a hard-coded timezone offset:
>
> 1981-04-06T14:45:15+01:00
>
>If we start accepting any symbolic timezone names, seems like we
>would then need to start accepting them all. If am reluctant to
>open the floodgates....
Yes, I know about your strict policy of adding new features to SQLite, and
please know that I do appreciate it. But this does not mean we have go give up
easily on new features, but provide better arguments instead. Let my try:
1. "Z" is part of the ISO standard and therefore used with external date and
time data. Supporting it makes it much easier to import such data into SQLite.
2. "Z" is not a soft-coded timezone specifier like "CET" or similar. It is just
a special case of the hard-coded "1981-04-06T14:45:15+00:00".
3. Using "Z" explictly distinguises UTC from local time zones and avoids
disambiguities.
4. Asking for "Z" I do not want to open any floodgates. If this was my
intention, I would have asked for
* ±[hh][mm] and ±[hh] -- currently missing but nice to have, IMHO
* named timezones ('MET' or 'Europe/Moscow') -- just a joke
* daylight saving time support -- kidding only
Ralf
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
