Use the Sqlite method, a floating point number. Inbuilt functions support that technique.
Rich Rattanni wrote: > All: > > I was wondering if there was any way to reduce the 'cost' of storing a > timestamp on entries in a SQLite database. I performed a hexdump of > the file and it showed me the timestamp is stored as a 19-byte ASCII > string. One quick thing I thought of was to store the unix timestamp > in each field, then when I wanted an actual date use > datetime(mytimeField,'unixepoch','localtime') to convert it back. > This would save me 9 bytes per record, but I would (greedily) like to > save more... any thoughts? > > -- > TIA, > Richard Rattanni > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
