Skip to content
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

Support SERVER_PS_OUT_PARAMS #840

Open
bgrainger opened this issue Jun 29, 2020 · 0 comments
Open

Support SERVER_PS_OUT_PARAMS #840

bgrainger opened this issue Jun 29, 2020 · 0 comments

Comments

@bgrainger
Copy link
Member

If MySqlConnector sets the ProtocolCapabilities.PreparedStatementMultiResults (CLIENT_PS_MULTI_RESULTS) flag, then prepared CALL statements will automatically provide a extra result set (flagged with ServerStatus.PsOutParams = SERVER_PS_OUT_PARAMS) with the contents of the out parameters.

This would remove the need to explicitly SELECT them in order to populate ParameterDirection.Output parameters after executing a CommandType.StoredProcedure command. (Split from #742.)

However, since this is an optional protocol feature (since MySQL 5.5.3, and TBD support from cloud providers), the client would still need to support both ways of retrieving output parameters. The CALL statement would still have to be parsed so that the order of parameters is known so that they can be assigned correctly.

(Perhaps a lot of the existing logic can be reused by setting ResultSet.ContainsCommandParameters based on the ServerStatus.PsOutParams flag?)

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

No branches or pull requests

1 participant