Looking at the db with a hex editor and tracing the sqlite code: your date/time are encoded as strings: e.g.
2013-09-23T16:41:10
which is not identified correctly by the connector:
// Parses string-formatted date into TDateTime value
// Expected format: '2013-12-31 ' (without ')
Function ParseSQLiteDate(S : ShortString) : TDateTime;
Var
Year, Month, Day : Integer;
begin
Result:=0;
If TryStrToInt(NextWord(S,'-'),Year) then
if TryStrToInt(NextWord(S,'-'),Month) then
if TryStrToInt(NextWord(S,' '),Day) then
Result:=EncodeDate(Year,Month,Day);
end;
// Parses string-formatted time into TDateTime value
// Expected format '23:59:59.999' (without ')
Function ParseSQLiteTime(S : ShortString; Interval: boolean) : TDateTime;
Var
Hour, Min, Sec, MSec : Integer;
begin
Result:=0;
If TryStrToInt(NextWord(S,':'),Hour) then
if TryStrToInt(NextWord(S,':'),Min) then
if TryStrToInt(NextWord(S,'.'),Sec) then
begin
MSec:=StrToIntDef(S,0);
if Interval then
Result:=EncodeTimeInterval(Hour,Min,Sec,MSec)
else
Result:=EncodeTime(Hour,Min,Sec,MSec);
end;
end;
(note: sqlite newb here)
Went digging into sqlite docs:
http://www.sqlite.org/datatype3.html [^]
1.2 Date and Time Datatype
date/time can be stored as integer (unix epoch), real as Julian day numbers and (ISO 8601 subset string as defined in
http://www.sqlite.org/lang_datefunc.html [^]
A time string can be in any of the following formats:
1 YYYY-MM-DD
2 YYYY-MM-DD HH:MM
3 YYYY-MM-DD HH:MM:SS
4 YYYY-MM-DD HH:MM:SS.SSS
5 YYYY-MM-DDTHH:MM
6 YYYY-MM-DDTHH:MM:SS
7 YYYY-MM-DDTHH:MM:SS.SSS
8 HH:MM
9 HH:MM:SS
10 HH:MM:SS.SSS
11 now
12 DDDDDDDDDD
So it would make sense to extend current support for 4 and 10 with 1-10.