True, but it seems to me that "Julian dates" (floating-point numbers) in
Universal Time are the least cumbersome way to go if you want a binary
representation, or character strings in one of the supported formats, if
you want a human-readable one.
You can also use Unix timestamps (integers), but those are slightly more
cumbersome, because they require an aditional keyword ('unixepoch') to
process.
g
-----Original Message-----
From: Igor Tandetnik [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2008 11:23 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Dates & SQLite
Brown, Daniel <[EMAIL PROTECTED]> wrote:
> Could someone point me to the documentation regarding dates and
> SQLite?
http://sqlite.org/lang_datefunc.html
> I'm having trouble finding anything about what data type I
> should use to store dates in my SQLite tables, should it be a
> numerical type (integer or real) or a string?
Your choice. SQLite doesn't have a dedicated date type, but it provides
built-in functions that can handle a variety of representations. You can
choose which one to standardize on.
Igor Tandetnik
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
