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

Procedure text is stored truncated in system tables if any variable have default value [CORE1837] #2266

Closed
firebird-automations opened this issue Apr 15, 2008 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

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

@firebird-automations
Copy link
Collaborator Author

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Fix Version: 2.5 Alpha 1 [ 10224 ]

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Done successfully

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