You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: