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
When reading from Oracle via ConnectorX, NUMBER columns with scale = NULL are always inferred as Float64.
However, in Oracle a NULL scale behaves like scale = 0 in most cases — meaning values are integers.
This results in unnecessary floats in downstream systems like Polars, causing type mismatches, slower operations, and the need for explicit casting.
Would it be possible for ConnectorX to treat scale = NULL as 0 when inferring types (mapping to integer instead of float)?
In many Oracle schemas, this matches actual usage and avoids unnecessary float conversions.
An optional environment variable or config flag could control this behavior for backward compatibility.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When reading from Oracle via ConnectorX, NUMBER columns with scale = NULL are always inferred as Float64.
However, in Oracle a NULL scale behaves like scale = 0 in most cases — meaning values are integers.
This results in unnecessary floats in downstream systems like Polars, causing type mismatches, slower operations, and the need for explicit casting.
Would it be possible for ConnectorX to treat scale = NULL as 0 when inferring types (mapping to integer instead of float)?
In many Oracle schemas, this matches actual usage and avoids unnecessary float conversions.
An optional environment variable or config flag could control this behavior for backward compatibility.
Beta Was this translation helpful? Give feedback.
All reactions