You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the implementation of FLOAT(p) with 1 <= p <= 24 being FLOAT (or REAL), and 25 <= p <= 53 being DOUBLE PRECISION from CORE6109, the precision for binary floating point types should probably be fixed for FB4+ to be reported with NUM_PREC_RADIX = 2 and the right values.
This would be in the various DatabaseMetaData methods, ResultSetMetaData, ParameterMetaData, etc.
description: With the implementation of FLOAT(p) with 1 <= p <= 24 being FLOAT (or REAL), and 25 <= p <= 53 being DOUBLE PRECISION from CORE6109, the precision for binary floating point types should probably be fixed for FB4+ to be reported with NUM_PREC_RADIX = 2 and the right values.
This would be in the various DatabaseMetaData methods, ResultSetMetaData, ParameterMetaData, etc.
Submitted by: @mrotteveel
Jira_subtask_inward JDBC466
Relate to CORE6109
With the implementation of FLOAT(p) with 1 <= p <= 24 being FLOAT (or REAL), and 25 <= p <= 53 being DOUBLE PRECISION from CORE6109, the precision for binary floating point types should probably be fixed for FB4+ to be reported with NUM_PREC_RADIX = 2 and the right values.
This would be in the various DatabaseMetaData methods, ResultSetMetaData, ParameterMetaData, etc.
Commits: 0fb5a02
The text was updated successfully, but these errors were encountered: