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

Substring of multi-byte BLOBs can fail [CORE1466] #1883

Closed
firebird-issue-importer opened this issue Sep 16, 2007 · 5 comments
Closed

Substring of multi-byte BLOBs can fail [CORE1466] #1883

firebird-issue-importer opened this issue Sep 16, 2007 · 5 comments

Comments

@firebird-issue-importer

Submitted by: @asfernandes

Is related to QA230

Attachments:
SEARCH.FDB.bz2

SUBSTRING function tries to convert MBCS BLOB to UTF16, and depending on BLOB content, the value passed by the engine to SUBSTRING may be a multi-byte truncated string.

Database attached. Test case:
select substring(document from 4 for 1) from t_documents where id = 1;

Commits: fdd74de

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Sep 16, 2007

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Sep 16, 2007

Modified by: @asfernandes

Attachment: SEARCH.FDB.bz2 [ 10570 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 28, 2008

Modified by: @pcisar

Workflow: jira [ 13070 ] => Firebird [ 13946 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 16, 2009

Modified by: @pcisar

Link: This issue is related to QA230 [ QA230 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 19, 2016

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants