On Fri, 4 Feb 2005 12:09:59 -0800 (PST), you wrote:

>I've been agonizing over the best way to store date/time
>values in my databases (perl will be the app platform).
>
>So, my question is, true or false:, if I want to use
>SQLite's date/time functions against field values, my only
>real option is to store YYYY-MM-DD HH:MM:SS time strings. 
>Any other value, whether YYYYMMDD, julian day number,
>MM/DD/YYYY, etc. (with or without the time portion), would
>leave me with having to do all format conversions in my app
>code.


Store as Julian, and then when you select out of SQLITE, have it do
the conversion for you.  You can also convert when inserting or
updating if you want.

I prefer the julian because it smaller, and I have no worries about
sorting by that column.  Anything fancy and  I use SQLITE to do the
format conversions, which is rare.

Randall Fox

Reply via email to