Jump to content

TDateTime type without timezone conversion

Recommended Posts

TDateTime datatypes are always compensated by their timezone when using the buildin RTTI conversion that Curiosity has.


So, when you want to transfer a JSON datetime like "2019-09-01T00:00:00", because of the timezone compensating, the variable in the application will be 2019-09-01T01:00:00+0100 depending on your timezone.

It is not possible to disable this, because the ISO8601xxx functions that are not used always have the UTC parameter value FALSE.


Would it possible to add a feature that we can define if the conversion routines should handle the TDateTime type with or without UTC ?

Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now