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
I've come across an issue where numeric values are parsed as strings but arrays of numerics are parsed as number arrays. Here is a minimal query to reproduce:
SELECT1.11::numericAS single_numeric, '{1.11,2.22,3.33}'::numeric[] AS numeric_array
I would expect numeric arrays to parse as string arrays.
The text was updated successfully, but these errors were encountered:
I am seeing this behaviour in the latest version of pg (8.11.3). Looking at its dependencies though, I see that it is using an old version of pg-types(2.1.0). Apologies, I assumed they would be updated together. Should I raise an issue in the node-postgres repo instead?
Yes it needs to be updated in pg. Check if there's an existing issue as IIRC this has come up previously and if not open an issue. There's some (potentially?) breaking changes that would mandate a major version bump on the pg side to incorporate the newer version of this library but after five years it's probably time we do it.
I've come across an issue where numeric values are parsed as strings but arrays of numerics are parsed as number arrays. Here is a minimal query to reproduce:
I would expect numeric arrays to parse as string arrays.
The text was updated successfully, but these errors were encountered: