Timestamp in different regions

[zoran]

kbmMW 5.10.20 Ent, Firebird 3.0.5, Delphi 10.3.3

In a table I have TIMESTAMP column. If I read that table from the client in the same Region as server all is ok. If I read the same table where client is in the different region than server, I get error message ‘Could not parse SQL TimeStamp string’.

In another words if server is in US and client is in US all is ok. If server is in Europe and client is in Europe, all is ok. But, if server is in US and client is in Europe (and vice-versa) I get this error.

This happens right after I execute ‘qry.Open;’ statement in client. I know I could keep timestamp as a number of seconds (BIGINT), but I would like to avoid conversions back and fourth.

Does anyone experience this, or am I missing something here?

Thank you

Zoran

• This topic was modified 5 years, 7 months ago by zoran.

[zoran]

Forget it.

It’s Delphi’s handling of Timestamp column. Both server and client use regional (local) FormatSettings to process Timestamp column, so different regions cause this error.

[Author]

Posts