-
Notifications
You must be signed in to change notification settings - Fork 821
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
Investigate exact expected output parameter behavior #2252
Comments
At least do the investigation for 5.0. |
NinoFloris
added a commit
that referenced
this issue
Mar 25, 2024
Including support for generic parameters Fixes #2252
NinoFloris
added a commit
that referenced
this issue
Mar 25, 2024
Including support for generic parameters Fixes #2252
NinoFloris
added a commit
that referenced
this issue
Mar 25, 2024
Including support for generic parameters Fixes #2252
NinoFloris
added a commit
that referenced
this issue
Mar 25, 2024
Including support for generic parameters Fixes #2252
NinoFloris
added a commit
that referenced
this issue
Mar 25, 2024
Including support for generic parameters Fixes #2252
NinoFloris
added a commit
that referenced
this issue
Mar 26, 2024
Including support for generic parameters Fixes #2252
NinoFloris
added a commit
that referenced
this issue
Mar 28, 2024
Including support for generic parameters Fixes #2252
NinoFloris
added a commit
that referenced
this issue
Jun 24, 2024
Including support for generic parameters Fixes #2252
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have some odd population logic for output parameters - if an output parameter was not matched (by name) to a column in the resultset, we currently assign it column values from the row which were matched to any other parameter... Check this against SqlClient and consider removing.
The text was updated successfully, but these errors were encountered: