On 4/28/19 5:46 PM, Mark Rotteveel wrote:
On 28-4-2019 16:42, Dimitry Sibiryakov wrote:
28.04.2019 16:31, Mark Rotteveel wrote:
The problem is exactly that they cannot use those types because
these drivers (clients) do not know about the existence of those
types...
In this case it is enou
On 28-4-2019 16:42, Dimitry Sibiryakov wrote:
28.04.2019 16:31, Mark Rotteveel wrote:
The problem is exactly that they cannot use those types because these
drivers (clients) do not know about the existence of those types...
In this case it is enough to execute "SET DECFLOAT BIND DOUBLE
PRE
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
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
Currently, the decfloat bind settings do not control behaviour of the
extended precision numerics.
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 statem
overflow warings in some collations
---
Key: CORE-6056
URL: http://tracker.firebirdsql.org/browse/CORE-6056
Project: Firebird Core
Issue Type: Bug
Components: Charsets/Collation
Affects Versions:
