Comments
3 comments
-
Wow, you wrote this bug in 2018, and it's now 2018 days later and still not fixed! -
It's been 2018 days since you reported this issue, and it's still not resolved. mapquest driving directions
-
Finding relief from back pain starts with expert care and a comprehensive approach to treatment. private pain clinic London combines advanced techniques and personalized strategies to address the root cause of pain, helping patients achieve long-term comfort and improved mobility. Take the first step towards pain-free living!
Add comment
Please sign in to leave a comment.
When you take a results grid which contains float values, and run a "Script as Insert" on the data, the generated SQL seems to always choose the data type "float(8)" to represent the inserted data.
The trouble with this is, the 8 used here means 8 mantissa bits (which SQL Server rounds up to a single-precision float, according to the docs), rather than the 8 bytes you might assume - i.e. a double-precision float.
This means, Script as INSERT loses a huge amount of float precision when the SQL is executed.
Cheers,
Mark