Hi Tim!
"Time(8) has no meaning to SQLite"
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.
Thanks!
Column Data Type Size----------------------------------------CommentID INTEGER
PKSummary VARCHAR 120Comment BLOBPage VARCHAR 10TimeStamp TIME 8Hyperlink BLOB
Scott Vallery
Ecclesiastes 4:9-10
On Tuesday, February 5, 2019, 8:23:53 AM EST, Tim Streater
<[email protected]> wrote:
On 05 Feb 2019, at 13:08, Scott <[email protected]> wrote:
> I have a Comment table with the fields: CommentID, Summary, Comment, Pages,
> TimeStamp, Hyperlink. The TimeStamp field is setup as a Time(8), time with 8
> characters only. Not every comment in this table requires a timestamp, so it
> should remain null. However, it has started adding "Thu Jan 01 00:00:00 EST
> 1970" and it will not let me clear it. This is being populated with the
> following Java code, in the past, it would just remain null. I included a
> Regular Expression to check the GUI field data when it is used. But, I can't
> even manually clear it now and I haven't changed the setup of the database,
> the table or TimeStamp field.
> Any thoughts or suggestions?
1) Please show your whole table definition for the comment table.
2) Time(8) has no meaning to SQLite, your timestamp field will probably default
to TEXT.
See: https://www.sqlite.org/datatype3.html
--
Cheers -- Tim
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users