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
Currently when creating a DECFLOAT(16) or DECFLOAT(34) column, the RDB$FIELD_PRECISION is left NULL. I think it would be helpful if this column is populated with the specified precision (16 or 34).
This has the advantage of forwards compatibility, if we ever decide to support DECFLOAT(n) with values other than 16 or 34, but backed by the current Decimal64 or Decimal128 storage.
Submitted by: @mrotteveel
Currently when creating a DECFLOAT(16) or DECFLOAT(34) column, the RDB$FIELD_PRECISION is left NULL. I think it would be helpful if this column is populated with the specified precision (16 or 34).
This has the advantage of forwards compatibility, if we ever decide to support DECFLOAT(n) with values other than 16 or 34, but backed by the current Decimal64 or Decimal128 storage.
Commits: dce2f10
The text was updated successfully, but these errors were encountered: