On 17 May 2019, at 12:06pm, J. King <[email protected]> wrote: > Then there would be no differentiating "default CURRENT_TIMESTAMP" from > "default 'CURRENT_TIMESTAMP'".
That interesting. If you supply "default CURRENT_TIMESTAMP" I would expect SQLite to evaluate CURRENT_TIMESTAMP, find a string value like '2019-05-17 12:10:43', and store that string in the schema. If you supply "default 'CURRENT_TIMESTAMP'" I would expect SQLite to evaluate 'CURRENT_TIMESTAMP', arrive at the string value of mostly upper-case letters, and store that string in the schema. Neither of those are the result that programmers would normally want. I withdraw my suggestion. Thanks for the heads-up. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
