Inserted FLOAT32 value has invalid precision

[ikenox]

Please make sure you have searched for information in the following guides.

• Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
• Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
• Check our Troubleshooting guide: https://github.com/googleapis/google-cloud-node/blob/main/docs/troubleshooting.md
• Check our FAQ: https://github.com/googleapis/google-cloud-node/blob/main/docs/faq.md
• Check our libraries HOW-TO: https://github.com/googleapis/gax-nodejs/blob/main/client-libraries.md
• Check out our authentication guide: https://github.com/googleapis/google-auth-library-nodejs
• Check out handwritten samples for many of our APIs: https://github.com/GoogleCloudPlatform/nodejs-docs-samples

A screenshot that you have tested with "Try this API".

N/A

Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.

https://gist.github.com/ikenox/5d774d4da8bfb5e33ddbd114d514aff7

A step-by-step description of how to reproduce the issue, based on the linked reproduction.

1. Execute the test code (gist)
2. Test will fail:

   AssertionError: expected 3.140000104904175 to be 3.14 // Object.is equality
   
   - Expected
   + Received
   
   - 3.14
   + 3.140000104904175
   

A clear and concise description of what the bug is, and what you expected to happen.

When inserting JavaScript number values into FLOAT32 columns using the Node.js Spanner client, the values seems not to be properly converted to 32-bit floating point precision before insertion. This results in unexpected values being stored in the database.

For example, inserting the FLOAT32 value 3.14 results in the following database state:

A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

The correct value should be inserted to the database.

[alkatrivedi]

@ikenox Thanks for pointing out the bug! It slipped under my radar, but I will get a PR ready to fix it soon.

[alkatrivedi]

@ikenox Thank you for your patience. We have confirmed this isn't a client-side bug. The issue is on the UI side, and we have raised a ticket with the responsible team. I will provide an update here once it gets fixed.

[surbhigarg92]

@ikenox As Alka confirmed this is not an issue on the client side. Data is getting inserted in the database as expected. Closing this bug as its not related to client library.