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.
FIX: bind executemany money-range Decimals as SQL_NUMERIC #752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
FIX: bind executemany money-range Decimals as SQL_NUMERIC #752
Changes from all commits
13147b204a6ab7b19607609b2414977654fef13ce4File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this uses sql numeric precision as the array's character-buffer width too. precision only counts digits, but the fixed-point string also needs space for the sign, decimal point, leading zero, and terminator.
Decimal("1E-38")gets(38, 38)here but formats to 40 characters, soPyStringArrayDataBufferrejects it before sql server sees it.I ran the same cases on this head and the exact merge base.
Decimal("1E-38")and[-12.34, 56.78]both complete on the base; this head raisesRuntimeError: Input string exceeds allowed column size at parameter index 0. the linux and windows jobs show the same 13 decimal failures too.can we keep sql precision and scale separate from the
SQL_C_CHARbuffer stride, sizing the buffer from the longest encoded fixed-point value plus its terminator?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
batch_precisionis applied tocolumnSizewithout a <=38 check. The sample-level guard in_map_sql_typedoesn't cover the whole batch, so a mixed batch (many integer digits in one row, many fractional in another) can producebatch_precision > 38even when each value is individually storable, and the driver then fails with an opaque message. Consider raising the existing "precision too high"ValueErrorwhenbatch_precision > 38. Don't clamp, since that would silently truncate.Uh oh!
There was an error while loading. Please reload this page.