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
You could bisect between v1.14.0 and v1.14.1. As far as I can tell there are only 2 commits that should have affected numeric support so it should be pretty trivial to determine which is the problem.
I've been trying to do a test without dependencies, and I am not able to replicate.
I am still able to replicate with my project/DB. I am unsure where the problem is.
I'll need to do your second suggestion and debug both versions. Will do sometime later this week.
I have a stored procedure that returns many columns and after the update.
Some of those columns are Numeric (both nullable and not nullable).
Before the update (using 1.14.0 all was good), but after update and release, we have had some complaints from some customers.
I am using:
I've created some tests to see what was happening.
I am using the following struct:
If I execute the following query directly in PostgreSQL 15.4:
The result is:
In
v.1.14.1
all values for AccountID, AmountBase and AmountVat are correct. But some of the values scanned for Amount are wrong:If I roll back to
v1.14.0
the values are correct:Let me know if you need further details.
I am going to rollback to v1.14.0, but it would be great if someone could take a look into this issue.
Thank you!
The text was updated successfully, but these errors were encountered: