Dear Support!

I want to ask something about automatic DST.

At one of the two changes the clock set from 3:00 to 2:00 as I remember well.

I want to ask that is this reflected in current_timestamp of EDB?

We used "default current_timestamp" frequently to determine the insert order, and for sorting records.

But if the DST setting of Windows restored a previous time point, we would make wrong decision.

It maybe provides this order in records:

1  1:59
2   2:01
3   2:30
4   2:59
---- DST ---
5   2:00
6   2:10

What is your point about this problem?

Thank your for any information:
  dd

On 9/25/2013 3:40 AM, durumdara wrote:
> Dear Support!

These are peer supported forums and not official EDB support. For that
see : http://www.elevatesoft.com/support

> We used "default current_timestamp" frequently to determine the insert order, and for sorting records.
> But if the DST setting of Windows restored a previous time point, we would make wrong decision.
> It maybe provides this order in records:
>
> 1  1:59
> 2   2:01
> 3   2:30
> 4   2:59
> ---- DST ---
> 5   2:00
> 6   2:10
>
> What is your point about this problem?

This would be correct - from application (and OS) perspective time
really is 2:00 again after the change.

If you want to use the timestamp in such a manner you should consider
using UTC version of it (e.g. CURRENT_TIMESTAMP(UTC) ).

Raul

Raul is correct - using UTC is the correct, and only, way to avoid this
issue since it won't ever be subject to clock adjustments for DST.

Tim Young
Elevate Software
www.elevatesoft.com