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
A query could produce different results, depending on the presence of an index [CORE1056] #1475
Comments
Commented by: @pcisar Adriano, can you provide a test case for this issue please? I would like write a test for it. |
Commented by: @asfernandes The test case for the first (fbintl) issue, fixed in V2.0 is: select * from t where c starting with 'c'; create index t_c on t (c); Test case for UNICODE issue I can't write. I could not write these unicode chars to reproduce problem in V2. |
Commented by: @pcisar Fix verified for 2.0.0, test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 11401 ] => Firebird [ 15420 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Done successfully |
Submitted by: @asfernandes
Is related to QA134
When the last character of a string is the first character of a compression pair, a query could produce different results depending on the presence of an index.
This bug was fixed in FB2 for intl collations, but it exist in UNICODE collation too.
Commits: ca0de4e
The text was updated successfully, but these errors were encountered: