13.02.2021 13:41, Mark Rotteveel wrote:
However if we're going to change this, we need to ensure that data type binding to WITHOUT TIME ZONE types will still work correctly (AFAIK, it currently uses the same code path as a cast), that is: render in the session time zone.
Unfortunately it has another problem: SET BIND affects only data type reported to client by info calls. The rest is up to general data type coercion mechanic which cannot (should not) be different from CAST one. The only way to settle it that I see is to introduce one more client-only data type (SQL_LOCAL_TIMESTAMP?) with separate coercion rules. It would fit to the family of "extended" timestamps.
-- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
