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
Maximum key size using PXW_CSY collation [CORE1802] #873
Comments
Modified by: @dyemanovassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Commented by: @asfernandes You're correct. Changes to allow ACCENT INSENSTIVE and CASE INSENSITIVE for all collations incorrectly changed the rules of level calculation. |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1.1 [ 10223 ] Fix Version: 2.5 Alpha 1 [ 10224 ] |
Commented by: @pmakowski Q/A test ok |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: prenosil (prenosil)
Is related to QA211
In FB2.0 it is possible to create index on
VARCHAR(499) CHARACTER SET WIN1250 COLLATE PXW_CSY
column, while in FB2.1 the maximum is only 330.
(seems FB2.1 considers that collation as 3-level, while 2.0 as 2-level)
RECREATE TABLE TAB21(
ID INTEGER,
A VARCHAR(330) CHARACTER SET WIN1250 COLLATE PXW_CSY,
CONSTRAINT CU UNIQUE(A) );
RECREATE TABLE TAB20(
ID INTEGER,
A VARCHAR(499) CHARACTER SET WIN1250 COLLATE PXW_CSY,
CONSTRAINT CU UNIQUE(A) );
Commits: 62ea4dc ff80913
The text was updated successfully, but these errors were encountered: