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
UNICODE_CI internal gds software consistency check [CORE2457] #2871
Comments
Modified by: @dyemanovassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandes |
Modified by: @asfernandesVersion: 2.5.0 [ 10221 ] Version: 3.0 Initial [ 10301 ] Version: 2.1.3 [ 10302 ] Version: 2.1.0 [ 10041 ] |
Commented by: berny (bernysx11_gmail.com) We have the same problem. Has anybody idea when is resolvig this issue? |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Modified by: @asfernandesFix Version: 2.5.2 [ 10450 ] |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: @asfernandes TEXTTYPE_SEPARATE_UNIQUE: Full key does not define equality class. To be used with multi-level collations which are case- or accent- insensitive. |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Submitted by: Geoff Worboys (gworboys)
Is duplicated by CORE3379
Is related to QA475
Votes: 1
I've run across an odd error that seems to occur when using the UNICODE_CI collation:
Error 335544333: internal gds software consistency check (Invalid expression for evaluation (303), file: evl.cpp line: 820)
I've managed to reduce the problem down to this:
CREATE TABLE ATABLE (
AFIELD VARCHAR(50) CHARACTER SET UTF8 COLLATE UNICODE_CI);
CREATE DESCENDING INDEX ATABLE_BWD ON ATABLE (AFIELD);
COMMIT;
Then try this select (even with no data in the table):
SELECT FIRST 1 T.AFIELD FROM ATABLE T
WHERE T.AFIELD < 'X'
ORDER BY T.AFIELD DESC
and I get the above error. (Both from FlameRobin and from an internal library/app.) Note that after the error occurs the connection becomes useless and has to be dropped and reconnected. The server itself stays running.
Changing to collation UNICODE or using an ASCENDING index avoids the error. A reverse logic query:
SELECT FIRST 1 T.AFIELD FROM ATABLE T
WHERE T.AFIELD > 'X'
ORDER BY T.AFIELD ASC
does not get the error (even when the ascending index is present, as it is in the original problem).
Discussion on the devel list indicated the problem is not only with the UNICODE_CI, apparently it is a problem with collation flag
TEXTTYPE_SEPARATE_UNIQUE. Cross reference with tracker item CORE1997.
Commits: 33b4780 a62c4b1 FirebirdSQL/fbt-repository@e6a772a
The text was updated successfully, but these errors were encountered: