error - when opening the table using field type of TIMESTAMP. When I click ASQLite3Table1 to active I get the error. It switches active to True but continues to warn/error when managing the data in the ASQLite3Table1 component.
Is there native support for this type within ASQLite3Table1 or perhaps a workaround? Of coarse I can manage a string field manually but I thought I would ask and bring this up.
Delphi Version D6. DB SQLite3.dll Aducom Latest DL set
Table SQL: CREATE TABLE [DLTable] ( [RecNo] INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, [Subject] TEXT NULL, [Body] TEXT NULL, [Account] TEXT NULL, [MsgNo] NUMERIC NULL, [TDStamp] TIMESTAMP DEFAULT CURRENT_TIMESTAMP NULL )
Geregistreerd: wo jan 25 2006, 04:34 Woonplaats: groningen (NL) berichten: 1561
To see how timestamp is supported you should look into the source. Keep in mind that SQLite is typeless, which means that all data is stored as string. To convert correctly to- and from any database you need to have set the correct datetime values or specify your own. I suspect that your stored data does not match the Delphi settings. albert
Thank you, I did. I read the section for SQLite3 that describes the typeless storage of DATE, TIME and TIMESTAMP as strings as well. I am not sure what I expected but activating the ASQLite3Table1 causes the error. The seamless conversion within the component is what I was hoping for. I am not getting to the point to manage it my self, the ASQLite3Table1 simply does not like the TIMESTAMP type that SQLite3 utilizes upon activation when it pulls and parses the schema it seems.
DATE type within SQLite seems to be fine but now am getting eConvert errors on TIME when I try and specify DATE and TIME as 2 fields within the database/table as a workaround.
if FSQLiteDateFormat then begin
shorttimeformat := 'hh":"nn":"ss"."zzz';
TempT := DateTimeToNative(FieldType, StrToTimeX(Buffer)) // aducom 2006 <--- errors at this line
also, ASqlite3Null200711A is the version I am using.
Well, that's a good question. Every version after that one has UNICODE compile issuese that I don't have time to work through. Best example would be to load the 2009 version in D6 and do a build. 2008 for that matter would illustrate the same. You'll see a number of unsupported backward compatibility calls and vars. For example CharInSet(), THandle incompatible types, pAnsichar, pWidechar come to mind. Does this makes sense?
Geregistreerd: wo jan 25 2006, 04:34 Woonplaats: groningen (NL) berichten: 1561
Considering old versions I'm depending on the community. I don't have all (old) Delphi versions installed. All in maintained in D2007 now. But you should not get CharInSet issues since this is a D2009 dependency and I suspect that you have tried the wrong download. albert
