Workaround bug in Qt6 ODBC driver #62908
Merged
+5
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use float instead of real for column. Qt6 is incorrectly reading 'real' column values as string values only, leading to truncation of decimals. (It seems that QSqlDatabase may be ignoring the numerical precision policy set on the database for the ODBC driver, at least for 'real' column types)
🪟 Windows Qt6 buildsDownload Windows Qt6 builds of this PR for testing. 🍎 MacOS Qt6 buildsDownload MacOS Qt6 builds of this PR for testing. 🪟 Windows buildsDownload Windows builds of this PR for testing. |
nirvn
approved these changes
Aug 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use float instead of real for column. Qt6 is incorrectly reading 'real' column values as string values only, leading to truncation of decimals.
(It seems that QSqlDatabase may be ignoring the numerical precision policy set on the database for the ODBC driver, at least for 'real' column types)
I don't have the specific SQL Server knowledge to understand if this a critical issue, or whether use of 'real' for the column types implies a low-precision value inherently. All I'm doing here is hiding the issue by changing our CI tests to use float values instead!