well, yes, it IS a limitation, which I will fix in the next release. the
problem is,
EXP registers its own version of a "date" function, as described in the
readme (I think I did describe it :), which is completely different than the
standard sqlite3 date function. I will make this optional in the next
release.
----- Original Message -----
From: "Clark Christensen" <[EMAIL PROTECTED]>
To: "SQLite List" <sqlite-users@sqlite.org>
Sent: Friday, August 19, 2005 8:09 PM
Subject: [sqlite] SQLite3 Explorer dates
> Mike,
>
> If appropriate for a future rev of SQLite3 Explorer (EXP),
> I'm requesting an update to the handling of date strings.
>
> Using SQLite3 Explorer (EXP) v1.6 under WinXP, "select
> date('2005-08-19')" gives a "not a valid FP number" error.
>
> Using the SQLite3 shell, I get '2005-08-19'.
>
> Maybe I'm mistaken, but shouldn't EXP return the result of
> the valid SQLite3 function (a string, in this case)? It's
> the same if I ask for a date string from a field value.
> "select date(datefield) from t1" (where datefield is a
> julian number), gives a number in EXP, and the expected
> date string in the SQLite3 shell.
>
> For what it's worth, strftime() seems to return the
> expected date string. Which is fine, except I'm using EXP
> to test my queries during development. I don't like having
> to change to strftime() where the app can work with date()
> or datetime() :-))
>
> Is this a limitation in EXP, or am I missing something?
>
> Thanks!
>
> -Clark
>
>
>
