Skip to content

Handle empty protocol option #112

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

Merged
merged 2 commits into from
Jan 16, 2023
Merged

Handle empty protocol option #112

merged 2 commits into from
Jan 16, 2023

Conversation

Michael-A-McMahon
Copy link
Member

Fixes #111

If the protocol option is set to an empty string, then it is treated the same as if no value had been set. This is done for compatibility with the R2DBC Pool project.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Jan 10, 2023
@jeandelavarene jeandelavarene merged commit 064efea into main Jan 16, 2023
@jeandelavarene jeandelavarene deleted the 111-empty-protocol branch January 16, 2023 20:10
@danielospinap
Copy link

Hi, is it possible to have a new versión with this fix?

@Michael-A-McMahon
Copy link
Member Author

I think we are overdue for one. This fix seems critical as I would consider r2dbc-pool to be the defacto solution for pooling R2DBC connections.

I'll see if I can get the process started on this. Probably a patch release numbered as 1.1.1 would be appropriate, as no major features have been added since 1.1.0 back in November 2022.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error occurs if ConnectionFactoryOptions.PROTOCOL option is an empty string
3 participants