-
-
Notifications
You must be signed in to change notification settings - Fork 233
Server crash with built in function LPAD with string as second parameter [CORE3517] #3875
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
Comments
Commented by: @livius2 this is related to LPAD select LPAD('abc', '0', 3) FROM RDB$DATABASE |
Commented by: @livius2 i change summary info because i found what exactly cause the server crash |
Modified by: @livius2summary: Server crash with built in function combination => Server crash with built in function LPAD with string as second parameter |
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Commented by: @asfernandes In 2.1 non-exact-numeric length argument will fall back to describe result string with 32K length. |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1.5 [ 10420 ] |
Commented by: @livius2 will be this fix available in some snapshot build? |
Modified by: @dyemanovVersion: 2.1.5 [ 10420 ] => |
Modified by: @pmakowski |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Done successfully |
Submitted by: @livius2
Is related to QA459
i simplify query for system tables only
and test on FB2.1.4.408 and on recent snapshot FB2.1.5.18427
after run this query server crash
SELECT LPAD(SUBSTRING(R.RDB$CHARACTER_SET_NAME FROM 1 FOR POSITION('.', R.RDB$CHARACTER_SET_NAME)-1), '0', 3)
FROM
RDB$DATABASE R
in firebird.log
PROGRAMISTAKB (Client) Tue Jun 07 09:22:14 2011
"C:\Program Files\Firebird\Firebird_2_1\bin\fbserver.exe": terminated abnormally (4294967295)
Commits: 80584e7
The text was updated successfully, but these errors were encountered: