Hi:
Saving the Now value adds exactly 4 hours to the saved time in a TimeStamp field. For example:

------------------------------------------
dtTme := Now;    // time as 2016-10-28 17:15:02... (5:15 PM)
ds.Columns['theDateTime'].AsDateTime := dtTme;   // this saves the time as 2016-10-28 21:15:02... (9:15 PM)
------------------------------------------

Note: Setting the field as Generated with 'Generate As Expression' to 'CURRENT_TIMESTAMP' results in the correct time being saved.

Is this a bug when saving a TimeStamp field type from EWB to EDB?

No Bug - Localization - Time Zone.

Walter


Trinione wrote:

Hi:
Saving the Now value adds exactly 4 hours to the saved time in a TimeStamp field. For example:

------------------------------------------
dtTme := Now;    // time as 2016-10-28 17:15:02... (5:15 PM)
ds.Columns['theDateTime'].AsDateTime := dtTme;   // this saves the time as 2016-10-28 21:15:02... (9:15 PM)
------------------------------------------

Note: Setting the field as Generated with 'Generate As Expression' to 'CURRENT_TIMESTAMP' results in the correct time being saved.

Is this a bug when saving a TimeStamp field type from EWB to EDB?

Walter Matte wrote:
<< No Bug - Localization - Time Zone.>>


How is this addressed though?

On 10/29/2016 5:25 AM, Trinione wrote:
>
> How is this addressed though?
>

EWB (javascript) works in UTC so you'd need to take that into account
when displaying in general.

Similarly on EDB side use CURRENT_TIMESTAMP(UTC) for EDB to default UTC
timestamp vs local.

Raul

So, how can the value of Now be converted to seconds since that 1970 date so it will be accepted by EDB properly?

function NowLocal : DateTime;
begin
 result := Now - (TimeZoneOffSet(now) * 60 * 1000);
end;

Walter:
Thank you very much, that works perfectly.

<< Saving the Now value adds exactly 4 hours to the saved time in a TimeStamp field. For example: >>

If you're using the EWB Web Server with the dataset support, make sure that the....damn, I just realized something - in the switch to the new database design in EWB, I forgot to add the LocalizeDateTimeColumns option back in for the datasets.  That option is the option that you can use to specify that you want dates/times localized/converted to UTC when the EWB web server reads from or writes to the dataset on the back-end.

I'll need to add this back in as part of the new build I'm doing this week.

Tim Young
Elevate Software
www.elevatesoft.com