We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Submitted by: @hvlad
CREATE PROCEDURE TRUNCATED AS DECLARE X INT = 0; BEGIN EXIT; END;
SELECT P.RDB$PROCEDURE_SOURCE FROM RDB$PROCEDURES P WHERE P.RDB$PROCEDURE_NAME = 'TRUNCATED'
Result is
= 0; BEGIN EXIT; END;
while it must be
DECLARE X INT = 0; BEGIN EXIT; END;
Commits: a8a0a39
The text was updated successfully, but these errors were encountered:
Commented by: @hvlad
This is because of after recent changes in parse.y stay possible nested begin_string\end_trigger rules.
I'll going to fix it replacing single pointer LexerState::beginning by stack
Sorry, something went wrong.
Fix Version: 2.5 Alpha 1 [ 10224 ]
assignee: Vlad Khorsun [ hvlad ]
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
status: Resolved [ 5 ] => Closed [ 6 ]
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: Done successfully
hvlad
No branches or pull requests
Submitted by: @hvlad
CREATE PROCEDURE TRUNCATED
AS
DECLARE X INT = 0;
BEGIN
EXIT;
END;
SELECT P.RDB$PROCEDURE_SOURCE
FROM RDB$PROCEDURES P
WHERE P.RDB$PROCEDURE_NAME = 'TRUNCATED'
Result is
= 0;
BEGIN
EXIT;
END;
while it must be
DECLARE X INT = 0;
BEGIN
EXIT;
END;
Commits: a8a0a39
The text was updated successfully, but these errors were encountered: