On 13/07/2019 08:09, Mark Rotteveel wrote:
2. Changing how WITH TIME ZONE types fundamentally work in the protocol this late in the development cycle is in my opinion problematic, and the alternatives suggested up to this point are - in my opinion - not better and in some cases worse.
The current implementation is something I will never use so I will probably not even bother switching TO FB4 ... The whole management of timezones is still broken and until there is a fully functional database as a base to build on it would be MUCH better not to add to the mess by yet another hack that fixes very little but adds more things to be patched by real applications ... Timezone data has a one second accuracy and MANY edge cases will hit that so anything built in must be able to process that data!
Simply pull it all until a full solution can be addressed! -- Lester Caine - G8HFL ----------------------------- Contact - https://lsces.uk/wiki/Contact L.S.Caine Electronic Services - https://lsces.uk Model Engineers Digital Workshop - https://medw.uk Rainbow Digital Media - https://rainbowdigitalmedia.uk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
