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

Connection property to ignore stored procedure type for call-escape. [JDBC576] #607

Closed
firebird-issue-importer opened this issue Feb 16, 2019 · 4 comments

Comments

@firebird-issue-importer

Submitted by: @mrotteveel

Currently (on Firebird 2.1 and higher), Jaybird will automatically decide whether to generate SQL execute procedure or select based on the procedure type. In some cases stored procedures incorrectly contain SUSPEND, or are used in a context where the handling of selectable procedures breaks (eg spring-data-jpa @procedure is not compatible with how Jaybird handles selectable procedures). For those cases, the automatic inference can be a hindrance.

As a workaround for those cases, add a property (name TBD) which disables automatic inference of selectability and always uses EXECUTE PROCEDURE (essentially, the behavior on Firebird 2.0 and earlier). Simplest way would be to make StoredProcedureMetaDataFactory return DummyCallableStatementMetaData if the property is set.

Commits: a44eccf 8217c32

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 16, 2019

Modified by: @mrotteveel

Fix Version: Jaybird 3.0.6 [ 10883 ]

Fix Version: Jaybird 4 [ 10441 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 6, 2019

Commented by: @mrotteveel

Implemented

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 6, 2019

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 25, 2019

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants