30.08.2019 15:24, Dimitry Sibiryakov wrote:
3. This solution is for really old clients which anyway can not work
with new time formats - use of alternate binding to character string
(like with decimal float values). Syntax is more or less same:
SET TIME ZONE BIND {NATIVE | LEGACY | CHAR}
Which correspond to sqltype in client XSQLVAR set to SQL_TIME_TZ,
SQL_TYPE_TIME and SQL_VARYING respectively.
Which sqltype value is provided by isc_dsql_prepare/describe_bind is
irrelevant as long as application can override it.
But 99.9% existing (at the moment) applications cannot override unknown
for them data type. So the BIND option may still be good for legacy
applications.
Dmitry
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
