10.05.2021 17:12, Adriano dos Santos Fernandes wrote:
On 10/05/2021 11:03, Dimitry Sibiryakov wrote:
10.05.2021 14:55, Adriano dos Santos Fernandes wrote:
May be explicit DefaultTimeZone=Auto can turn on passing implicit
client
time zone? Not to say I treat it as absoluely needed, just possible
solution.
It should be possible, but requiring ICU in the client when that setting
is used.
Should this part be deferred?
May be it would be enough to use system-specific timezone functions
and translate their results to ICU names/ids?..
Do you know such "translator" ? At least for Windows.
It's what ICU does and I see no need to replicate it.
People wanting a functionality should not be worried about a DLL (which
in 99% of cases will be there already).
I can agree about 99% of non-Windows cases, but on Windows it is wrong
assumption.
Despite of presence of ICU in some recent versions of Win10, the non-standard
non-
predictable way of its deployment not allows us to make use of it. According to
https://docs.microsoft.com/en-us/windows/win32/intl/international-components-for-unicode--icu-
a) Win10 before build 1703 - no integrated ICU
b) Win10 1703 : standard, expected deployment of ICU (icuuc.dll, icuin.dll)
c) Win10 1903 : non-standard deployment using "common" library icu.dll
Yes, we could add Windows-specific code to try load icu.dll, but I don't know
what
MS will change in next release and by what reason. Thus I don't think we could
rely
on presence of system ICU in Win10, unfortunately.
And, note, we still support Win7+ where ICU is far not guaranteed to be
present.
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
