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

roji opened this Issue Dec 5, 2018 · 0 comments


None yet
1 participant

roji commented Dec 5, 2018

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.

@roji roji added this to the 4.1 milestone Dec 5, 2018

@roji roji self-assigned this Dec 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment