On 30.08.2019 15:46, Dimitry Sibiryakov wrote:
30.08.2019 14:29, Dmitry Yemanov wrote:
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.
In the past such incompatibilities used to be handled with a
configuration parameter.
.conf parameter is for all database attachments but if we expect _all_
clients to use same backward-compatibility style - why use new datatype
at all?
I don't mind MS SQL way with tons of SET options but they used to
complicate support and troubleshooting.
I see only one problem with SQL-style management - if old application
can't issue arbitrary SQL how to tune it to use legacy/char format? On
the other hand: how at all will such application use new DB format? SQL
tuning was supposed to be used in something like old version of
IbExpert, etc.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
