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
Create a spanner table in a database with a FLOAT64 data type.
try to insert/update with 1.00 or 1 through nodejs.
Use-case: User sends us data to insert as a JSON message, we do not have any knowledge of the table schema, we try to insert the same data as-it-is, so we are facing this error when the user is trying to insert/update the FLOAT64 cloumn with either an integer or value ends with .00 spanner is throwing following error: Error: 9 FAILED_PRECONDITION: Invalid value for column score in table test1: Expected FLOAT64.
But our problem is that we have no context of table schema, there is no Spanner API available to check the column types (as of my knowledge), I have created a FR: googleapis/nodejs-spanner#368, but it was closed due to insufficient info.
Please suggest a way to over come this. As you are accepting JSON data please fix this accordingly.
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
The text was updated successfully, but these errors were encountered:
Environment details
Steps to reproduce
google-cloud
Use-case: User sends us data to insert as a JSON message, we do not have any knowledge of the table schema, we try to insert the same data as-it-is, so we are facing this error when the user is trying to insert/update the FLOAT64 cloumn with either an integer or value ends with .00 spanner is throwing following error:
Error: 9 FAILED_PRECONDITION: Invalid value for column score in table test1: Expected FLOAT64.
I have gone through the suggestion here: #2307
But our problem is that we have no context of table schema, there is no Spanner API available to check the column types (as of my knowledge), I have created a FR: googleapis/nodejs-spanner#368, but it was closed due to insufficient info.
Please suggest a way to over come this. As you are accepting JSON data please fix this accordingly.
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
The text was updated successfully, but these errors were encountered: