On 24-12-2018 21:25, Shawn Wagner wrote:
Using '.mode column" in conjunction with ".headers on" you're already using
makes it a lot more obvious.
like this:
SQLite version 3.21.0 2017-10-24 18:55:49
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> select 1 as X,date() as d union all select 2,date() union all
select 3,datetime();
1|2018-12-25
2|2018-12-25
3|2018-12-25 18:56:41
sqlite> .mode column
sqlite> .headers on
sqlite> select 1 as X,date() as d union all select 2,date() union all
select 3,datetime();
X d
---------- ----------
1 2018-12-25
2 2018-12-25
3 2018-12-25
sqlite> select 1 as X,datetime() as d union all select 2,date() union
all select 3,datetime();
X d
---------- -------------------
1 2018-12-25 18:57:11
2 2018-12-25
3 2018-12-25 18:57:11
sqlite>
the first result seems correct (datetime after the 3)
in the secondresult the third line is casted to date? (or misses time?)
the above seems to be not correct when looking at the last query.
Same result in version 'SQLite version 3.26.0'
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
