Invalid parameter values passed in, due to size mismatch. #21
Conversation
This file contains 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
mkleehammer
added a commit
that referenced
this pull request
Oct 13, 2013
Invalid parameter values passed in, due to size mismatch.
|
Thanks. The Microsoft ODBC documentation indicates that the C_SBIGINT are the right choice, but I tested SQL_C_LONG in Python 2.7 32-bit and 64-bit builds with SQL Server. It makes sense on 64-bit builds to use long for BIGINT, but I'm still not sure why C_BIGINT didn't work. ODBC drivers are not very consistent. |
This was referenced Sep 23, 2016
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.
Thank you very much for the last correction.
This one is quite important:
we get very wrong parameter values. I still have to write a test case for it, but I thought you should run your own testcases against it as-is.