Skip to content

Conversation

NinoFloris
Copy link
Member

@NinoFloris NinoFloris commented Mar 25, 2024

Moved the output reading into the command itself and added support via a virtual for reading values as a generic type for generic parameters.

Probably want to add some tests for the latter, TODO.

Regarding

    // Not sure where this odd behavior comes from: all output parameters which did not get matched by
    // name now get populated with column values which weren't matched. Keeping this for backwards compat,
    // opened #2252 for investigation.

I've added commentary on why it exists, people likely depend on this behavior as well. An unfortunate holdover from when we didn't have positional parameters.

We also have a test depending on it https://github.com/npgsql/npgsql/blob/main/test/Npgsql.Tests/FunctionTests.cs#L119.
Note how the set consists of named parameters while the columns are unnamed.

Related to #2252

@NinoFloris NinoFloris added this to the 9.0.0 milestone Mar 25, 2024
@NinoFloris NinoFloris force-pushed the output-parameter-handling branch 4 times, most recently from 2a86b31 to 5fb2d86 Compare March 28, 2024 18:21
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants