Damon Courtney wrote:
Hrmm... I really hate date fields in SQL. I usually go with an integer field and store [clock seconds]. It's more of a pain in the ass to me to let the SQL server try and do the work when I can just as easily do it myself with little-to-no loss of performance. We'll have to decide on the best way to handle this.
I would like that. As I posted a week ago, also sqlite doesn't know about a keyword 'now' in timestamp or datetime fields. In fact, due to to the 'typeless' behavior of sqlite there isn't even a datetime type, but sqlite has a number of date and time functions.
Why not saving [clock seconds] as an integer or so? Just my two cents Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
