Within 3.1 changelog, there is mentioned something about using ISO-8601 standards for date and time types:
"CURRENT_TIME, CURRENT_DATE, and CURRENT_TIMESTAMP
These keywords resolve into ISO-8601 time strings. You can use them anywhere but they are especially useful as the default value for columns in a table definition."
Some background: Within KexiDB (application layer on top of SQLite), I stored datetime values as "yyyy-mm-dd hh:mm:ss" but now I store that as defined by ISO: "yyyy-mm-ddThh:mm:ss". I am still acepting " " instead ot "T" for compatibility (and even whatever you can put instead of "T").
Question for SQLite devs: I noticed that (at least as for version 3.0.6) SQLite's datetime() function requires " " between date and time functions. Could we change this to more tolerant behaviour, I mentioned above? Or at least accept both "T" and " ".
-- regards / pozdrawiam, Jaroslaw Staniek / OpenOffice Polska / Kexi Team Developers Wanted! Kexi 0.1 Beta 5 Released: http://www.kexi-project.org KDElibs/Windows: http://wiki.kde.org/tiki-index.php?page=KDElibs+for+win32
