>it just seems very inefficient to store a date as a string in a database.
I agree. But why would you store it as a string?? I personally store my times as ints (__time64_t, or time_t). When I read it back my app formats it however I want. Simple :) Doug > -----Original Message----- > From: [email protected] [mailto:sqlite-users- > [email protected]] On Behalf Of jonwood > Sent: Saturday, February 28, 2009 5:17 PM > To: [email protected] > Subject: Re: [sqlite] DateTime Objects > > > > Jonas Sandman wrote: > > > > So store your time as a 64-bit integer. Sqlite has support for that. > > > > Yeah, I can either do something like that or do parsing with existing > column. I was just taking advantage of some of the properties provided > by > the DATETIME column and it just seems very inefficient to store a date > as a > string in a database. > > Thanks. > > Jonathan > > > -- > View this message in context: http://www.nabble.com/DateTime-Objects- > tp22264879p22268085.html > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
