Skip to content

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

Open

Description

@firebird-automations

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.

Activity

  1. firebird-automations commented on Feb 16, 2019

    @firebird-automations
    Author
    Modified by: @mrotteveel

    Fix Version: Jaybird 5 [ 10871 ]

  2. mrotteveel commented on Jan 21, 2023

    @mrotteveel
    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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions