Hi sqlite devs,

I am using SQLite wrapped by SQLAlchemy ORM and have encountered a weird behavior of CAST of a timestamp string to timestamp type as described at https://bitbucket.org/zzzeek/alembic/issues/391/batch-migration-on-sqlite-truncate :

Steps to reproduce:
sqlite> select CAST('1970-01-02 03:04:00.000000' AS TIMESTAMP);

Expected result:
1970-01-02 03:04:00.000000

Actual result:
1970

Tested versions:
SQLite version 3.7.17 2013-05-20 00:56:22
SQLite version 3.11.0 2016-02-15 17:29:24

Is this "as designed" and I have missed the part of SQLite documentation describing this surprising behavior -- or is it a bug?

Thank you!
Jiri Bajer
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to