On 11/05/2018 19:48, Lester Caine wrote:
>
> There is no information on those pages covering just what way the base
> TZ data is processed. I think it is probably safe to assume that it is
> unusable for providing timezone offsets prior to 1970 which is the
> current target of TZ itself, so it
On 12/05/18 00:32, Adriano dos Santos Fernandes wrote:
On 11/05/2018 19:48, Lester Caine wrote:
There is no information on those pages covering just what way the base
TZ data is processed. I think it is probably safe to assume that it is
unusable for providing timezone offsets prior to 1970
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 to the current situation
without managing
On 11/05/2018 01:20, Vlad Khorsun via Firebird-devel wrote:
>
>>
>> Every range (x-y) must define a displacement.
>
> Good, now it is much more clear (for me, at least).
> It there a way to query\extract this ranges and coresponding
> displacements ?
>
I do not thought about it, but would be
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
11.05.2018 13:22, Adriano dos Santos Fernandes wrote:
I do not thought about it, but would be very good to put them in another
virtual table if possible.
May be a package with a set of procedures would be better then?..
--
WBR, SD.
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
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
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
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/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
On 11-5-2018 18:31, Adriano dos Santos Fernandes wrote:
Hi!
Here is the first README version for the time zone feature.
https://github.com/FirebirdSQL/firebird/blob/work/time-zone-support/doc/sql.extensions/README.time_zone.md
Reading through that, a few questions:
# About the 2 bytes for
On 11/05/18 17:31, Adriano dos Santos Fernandes wrote:
Here is the first README version for the time zone feature.
https://github.com/FirebirdSQL/firebird/blob/work/time-zone-support/doc/sql.extensions/README.time_zone.md
So there is no provision to support the initial LMT offsets for those
Hi!
Here is the first README version for the time zone feature.
https://github.com/FirebirdSQL/firebird/blob/work/time-zone-support/doc/sql.extensions/README.time_zone.md
Adriano
--
Check out the vibrant tech
12.05.2018 1:12, Lester Caine wrote:
On 11/05/18 20:37, Adriano dos Santos Fernandes wrote:
* PST is Pitcairn or Pacific, with the same offset, they are
considered different time zones
ICU data is derived from TZ data hosted by IANA
(http://site.icu-project.org/tznotice).
I really can't
On 11/05/18 23:32, Vlad Khorsun via Firebird-devel wrote:
12.05.2018 1:12, Lester Caine wrote:
On 11/05/18 20:37, Adriano dos Santos Fernandes wrote:
* PST is Pitcairn or Pacific, with the same offset, they are
considered different time zones
ICU data is derived from TZ data hosted by IANA
On 11/05/2018 16:04, Mark Rotteveel wrote:
> On 11-5-2018 18:31, Adriano dos Santos Fernandes wrote:
>> Hi!
>>
>> Here is the first README version for the time zone feature.
>>
>> https://github.com/FirebirdSQL/firebird/blob/work/time-zone-support/doc/sql.extensions/README.time_zone.md
>>
>
>
On 11/05/18 20:37, Adriano dos Santos Fernandes wrote:
* PST is Pitcairn or Pacific, with the same offset, they are
considered different time zones
ICU data is derived from TZ data hosted by IANA
(http://site.icu-project.org/tznotice).
I really can't answer questions about specific time
18 matches
Mail list logo
