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 Pipelining #143

Closed
Michael-A-McMahon opened this issue May 9, 2024 · 0 comments · Fixed by #145
Closed

Support Pipelining #143

Michael-A-McMahon opened this issue May 9, 2024 · 0 comments · Fixed by #145
Assignees

Comments

@Michael-A-McMahon
Copy link
Member

The 23.4 release of Oracle Database and Oracle JDBC allow database calls to be pipelined. See: https://docs.oracle.com/en/database/oracle/oracle-database/23/jjdbc/pipelined-database-operations.html#GUID-E1DBDC02-D3F3-4601-A38D-A25159EB98BE).

Reactive programmers should be able to access these benefits, but Oracle R2DBC is currently designed in a way which prevents that. Specifically, the AsyncLock class basically implements a local pipeline, ensuring that database calls are executed sequentially. This was useful for the 21.x releases of Oracle JDBC, which did not support pipelining, and would block any thread that attempted concurrent database calls.

To fix this issue, Oracle R2DBC needs to update the ojdbc11 dependency to 23.4 (or newer), and it needs to get the AsyncLock out of the way.

@Michael-A-McMahon Michael-A-McMahon self-assigned this May 9, 2024
@Michael-A-McMahon Michael-A-McMahon linked a pull request May 9, 2024 that will close this issue
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 a pull request may close this issue.

1 participant