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

No longer transform explicit usage of EXECUTE PROCEDURE and SELECT in prepareCall [JDBC577] #608

Open
firebird-automations opened this issue Feb 16, 2019 · 2 comments

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Rework how prepareCall transforms explicit use of EXECUTE PROCEDURE procedure_name or SELECT * FROM procedure_name, as this is currently mapped in the exact same way a {call procedure-name(..)} is handled, which can lead to a EXECUTE PROCEDURE being transformed to SELECT (and vice versa).

This change may have compatibility implications, eg under Firebird 3, transforming SELECT to EXECUTE automatically avoids errors as selecting from an executable procedure is no longer allowed. This may need to have a compatibility property.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 5 [ 10871 ]

@mrotteveel
Copy link
Member

Correction, SELECT * FROM procedure_name in prepareCall doesn't even work, only EXECUTE PROCEDURE and the call-escape is supported.

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

No branches or pull requests

2 participants