Tony (& others),
On 2020-03-09 19:48, Tony Whyman wrote:
The question then arises as to why this is not the normal way of
working? Using the client's local ICU introduces a maintenance headache.
This argument I personally hardly accept. May be for old windows
versions - yes, some problems. All the others upgrade ICU as a part of
regular OS upgrade. I.e. if one already has local ICU extended format is
definitely useless overhead.
On the other hand I know that some people treat installing ICU even
single time as a huge problem - for example a number of users from sql.ru.
Taking into an account that both POVs do exist we have an ability to
change modes. And as long as something should be chosen as default -
shorter format is default. I hope we can finish with this discussion at
least...
If it is out-of-step with the server (or other clients) then
inconsistent results may occur when computing daylight savings time
offsets.
So why shouldn't I just always call "SET BIND..." as soon as a
database connection is opened, support only the EXTENDED
TIME/TIMESTAMP WITH TIME ZONE, and avoid the risk of ICU's getting out
of step?
Certainly if you prefer this way to go you can choose it. Be sure -
nobody is going to remove extended formats as long as they are in use.
BTW, you can add that kind of tuning to DPB with one additional bonus -
bindings from DPB become default for a session, i.e. they are restored
after session reset.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
