On 05.09.2019 17:25, Adriano dos Santos Fernandes wrote:
On 05/09/2019 10:59, Alex Peshkoff via Firebird-devel wrote:
On 05.09.2019 16:52, Adriano dos Santos Fernandes wrote:
Looks like finally you agreed that return a different tz value is
like
dropping a different database because engine could not drop the
asked
one, and no workaround should be inserted replacing region codes by
wrong offsets.
Why are you so sure that offset will be invalid? What's incorrect in
replacing TZ 'MSK' with offset +3?
Don't use an absurd implementation that returns wrong data, and that
data may be reintroduced in new statements and change correct data.
Just it.
Adriano, I've already asked and repeat once again: Why are you so sure
that offset will be invalid? What's incorrect in replacing (for
example) TZ 'MSK' with offset +3?
You and Vlad have been answered a lot of times by different people:
- Offset is much less information than the region
And I've answered - yes, it contains less information but 'less
information' != 'wrong information'.
- Offset is not remap-able to region (many regions uses same offsets)
That also does not make offset information wrong.
- Offset + "converted time from GMT" is ambiguous (before or after dst
start/end?)
TZ code + "converted time from GMT" (i.e. regional time?) is ambigious.
Offset + any time information is not ambiguous - just subtract it from
regional time and get GMT time.
- It's different than original data, and output of a query may enter as
input of a changing statement later
This is really disadvantage. But first of all that's a disadvantage of
client application which sends back in update non-modified fields.
- It has different meaning from the correct usage: correct usage had GMT
time + offset/region. You want converted time + offset, which would
completely defeat the usage as input
No, I prefer 4 formats:
1. GMT time + offset/region
2. GMT time + offset
3. regional time + offset/region
4. regional time + offset
According to client's choice. One which does use bad application which
sends back in update non-modified fields may be would not like to use
formats 2 & 4.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
