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
Cloud Spanner only has INT64, a long. The current V2 behavior is to ignore the requested type and instead only use the type of the retrieved column to decode the value.
In V1, retrieving an Integer column value was supported.
Should we support retrieving integers if the user requested an Integer explicitly? Likely yes, with exceptions thrown if the returned INT64 value does not fit into an integer. The alternative would be to disallow this scenario, but that's a regression from V1.
The text was updated successfully, but these errors were encountered:
Remove TCK test overrides that were necessary due to DML syntax requiring column list in Spanner.
R2DBC SPI 0.8.3 containing the TCK changes was released. I also upgraded Reactor to the same version that's in SPI.
There are still two reasons for overrides:
1) Spanner returning `Long` even when `Integer` is requested -- work tracked in #276.
2) the driver breaking R2DBC spec by treating columns as case insensitive -- decision pending on #271.
Cloud Spanner only has INT64, a long. The current V2 behavior is to ignore the requested type and instead only use the type of the retrieved column to decode the value.
In V1, retrieving an Integer column value was supported.
Should we support retrieving integers if the user requested an Integer explicitly? Likely yes, with exceptions thrown if the returned INT64 value does not fit into an integer. The alternative would be to disallow this scenario, but that's a regression from V1.
The text was updated successfully, but these errors were encountered: