We need to get these into the hive database, if that's helpful ________________________________ From: Simon Slavin <slav...@bigfraud.org> Sent: May 17, 2019 8:16 AM To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sqlite] Bug in table_info pragma
On 17 May 2019, at 12:06pm, J. King <jk...@jkingweb.ca> 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 sqlite-users@mailinglists.sqlite.org https://urldefense.proofpoint.com/v2/url?u=http-3A__mailinglists.sqlite.org_cgi-2Dbin_mailman_listinfo_sqlite-2Dusers&d=DwIGaQ&c=SFszdw3oxIkTvaP4xmzq_apLU3uL-3SxdAPNkldf__Q&r=3mFDfHOq-dU1rrQz09cmOjm2rdOZoX-v3kqQ0JKJclY&m=JsYCXwKMIwvuiUtswqJf70eWsb7VKv5Zho6ACWgH43c&s=6CF5uBksQbSaeUGsAgOF2wpKvmXxwo_o6rG9YhRl0qw&e= ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
