Hi! Quoting README.time_zone.md:
------- The session time zone, as the name implies, can be a different one for each database attachment. It can be set with the isc_dpb_session_time_zone DPB, and if not, it starts by default defined to be the `firebird.conf` parameter `DefaultTimeZone` or the same time zone used by the Firebird OS process when the parameter is not defined. A change in `DefaultTimeZone` configuration or the OS time zone does not changes the default of a running Firebird process. ------- And firebird.conf: ------- # # Default session or client time zone. # # If empty, the default is the OS time zone. # When set in the server, it defines the default session time zone for attachments. # When set in the client, it defines the default time zone used with client-side API functions. # # Type: string # #DefaultTimeZone = ------- I'm wondering if this is clear enough and even if it's the best possible behavior. On the README, when it says about firebird.conf, it's saying about *server* firebird.conf. And in firebird.conf, when it says about client, it means when (if) descriptors involving *-tz types are used, for example, moving string 'NOW' to a timestamp-tz descriptor. That should be uncommon and when happen, requires ICU in the client. What I want to ask about if it's clear/good is that DefaultTimeZone set in client does not implicitly pass isc_dpb_session_time_zone in the attachment. Also note that no implicit client time zone is passed when DefaultTimeZone is not set. Doing so would create compatibility problems with date/time functions for who is not interested in time zones. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
