On 28-4-2019 16:15, Dimitry Sibiryakov wrote:
28.04.2019 14:48, Mark Rotteveel wrote:
For support of clients that don't support the Firebird 4 types, it
would be helpful if the decfloat bind setting also governs the
extended precision numerics, or if a similar setting (both statement +
dpb) is created. Maybe 'decfixed bind', but that might be too unclear
as it references internals rather than external visible type name.
Sorry, I don't understand what exactly is a problem.
The exact same problem that has been fixed for decfloat using set
decfloat bind and isc_dpb_decfloat_bind...
The problem is that if you have a client (eg Jaybird 3 and earlier, FDB,
pyfirebirdsql, etc) that doesn't support precision > 18 for numeric and
decimal, you can't select those values.
Given such a provision is made for decfloat and time zone types, I think
it is perfectly reasonable to expect such a feature for numeric/decimal
with precision > 18.
AFAIU, such client don't need to care about internals as long as they
get everything in desired format on client side.
The problem is exactly that they cannot use those types because these
drivers (clients) do not know about the existence of those types...
BTW: My reference to the term "internals" was with regard to my
suggestion to name the config option 'decfixed bind' (as the type is
internally called dec_fixed).
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
