Closed sellotape closed 2 months ago
That's because we didn't know it was a break. This is related to the GetValue change for strings, to mitigate against a npgsql behaviour.
I've unlisted - will think of best path forward, probably a revert.
Xref #2049 #2050
I have the same problem with decimal to string. Thanks
Yup, we need to revert a change there (which is why 2.1.37 is hidden); I'll do that now
Might be intentional, but worked in 2.1.35, and I suspect a lot of people will be depending on it and pretty surprised, as there's no mention of a breaking change in the release notes.
To replicate, simply (I'm using Azure SQL Server):
In 2.1.35, this returns e.g. "42". In 2.1.37 it throws
System.InvalidCastException : Unable to cast object of type 'System.Int32' to type 'System.String'.
Fuller exception: