https://www.sqlite.org/datatype3.html#determination_of_column_affinity
"Time(8)" ends up as numeric affinity for that field. When it's given the string "Thu Jan 01 00:00:00 EST 1970" to store in the numeric field, that string can't be losslessly converted to a number, and thus it leaves it alone and stores it as-given as text. -----Original Message----- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Simon Slavin Sent: Tuesday, February 05, 2019 10:44 AM To: SQLite mailing list Subject: Re: [sqlite] My TimeStamp field keeps populating though I don't write anything to it On 5 Feb 2019, at 3:29pm, Scott <scottvall...@yahoo.com> wrote: > Thanks for the timely response. I provided below the details. "Time(8)" is > the generated description of the structure defined by SQLite3 based upon Data > Type options. So I apologize if I don't understand you comment. SQLite didn't generate "Time(3)". Some other piece of software may have done so, and told SQLite to use it as a datatype. SQLite doesn't have a Time datatype. See the list of datatypes at the top of section 2 of <https://www.sqlite.org/datatype3.html> SQLite is taking "Time(8)" and understanding it as "TEXT". See the table in section 3.1.1 of the above web page. SQLite doesn't recognise limits to the number of characters in text fields. SQLite is ignoring the "(8)" giving it a limit of 8 characters. See the paragraph just above that table. Hope this helps. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
