On 11/05/18 16:07, Adriano dos Santos Fernandes wrote:
On 11/05/2018 11:55, Lester Caine wrote:
On 11/05/18 15:44, Adriano dos Santos Fernandes wrote:
If the machine clock goes back one hour because of a DST transition,
the current time overlaps and the same set of numbers are used twice.
No.
On 11/05/2018 11:55, Lester Caine wrote:
> On 11/05/18 15:44, Adriano dos Santos Fernandes wrote:
>>> If the machine clock goes back one hour because of a DST transition,
>>> the current time overlaps and the same set of numbers are used twice.
>> No.
>
> We are talking currently with a normal 64bi
On 11/05/18 15:44, Adriano dos Santos Fernandes wrote:
If the machine clock goes back one hour because of a DST transition,
the current time overlaps and the same set of numbers are used twice.
No.
We are talking currently with a normal 64bit TIMESTAMP ...
The comparison with Oracle is that t
On 11/05/2018 11:16, Lester Caine wrote:
>
> If the machine clock goes back one hour because of a DST transition,
> the current time overlaps and the same set of numbers are used twice.
No.
Adriano
--
Check out the vib
On 11/05/18 14:27, Adriano dos Santos Fernandes wrote:
On 11/05/2018 10:10, Lester Caine wrote:
Forgot to hit reply list ...
On 11/05/18 12:30, Adriano dos Santos Fernandes wrote:
On 11/05/2018 06:54, Lester Caine wrote:
I was having a proper look through the Oracle timezone documentation
and
On 11/05/2018 10:10, Lester Caine wrote:
> Forgot to hit reply list ...
>
> On 11/05/18 12:30, Adriano dos Santos Fernandes wrote:
>> On 11/05/2018 06:54, Lester Caine wrote:
>>> I was having a proper look through the Oracle timezone documentation
>>> and thinking 'how can you get it so wrong'. Doe
Forgot to hit reply list ...
On 11/05/18 12:30, Adriano dos Santos Fernandes wrote:
On 11/05/2018 06:54, Lester Caine wrote:
I was having a proper look through the Oracle timezone documentation
and thinking 'how can you get it so wrong'. Does it REALLY have a
ERROR_ON_OVERLAP_TIME flag because
On 11/05/2018 06:54, Lester Caine wrote:
> I was having a proper look through the Oracle timezone documentation
> and thinking 'how can you get it so wrong'. Does it REALLY have a
> ERROR_ON_OVERLAP_TIME flag because it allows the server local clock to
> be used raw. Actually this is no different t