Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
currently a collation lookup (collation name to collation id) is done (in get_collation_number_internal()) by linearly scanning the array of collations.
This used to work fine, but the number of collations is constantly growing (MDEV-27009, MDEV-20912) and the linear search is starting to become noticeable.
It would be a good idea to change it to a hash lookup.
Same can be done for character sets, even though the number of charsets didn't grow that much.
Attachments
Issue Links
- is caused by
-
MDEV-20912 Add support for utf8mb4_0900_* collations in MariaDB Server
-
- Closed
-
-
MDEV-27009 Add UCA-14.0.0 collations
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is caused by |
Link |
This issue is caused by |
Link |
This issue is caused by |
Link |
This issue is caused by |
Description |
currently a collation lookup (collation name to collation id) is done (in {{get_collation_number_internal()}}) by linearly scanning the array of collations.
This used to work fine, but the number of collations is constantly growing ( It would be a good idea to change it to a hash lookup. Same can be done for character sets, even though the number of charsets didn't grow that much. |
currently a collation lookup (collation name to collation id) is done (in {{get_collation_number_internal()}}) by linearly scanning the array of collations.
This used to work fine, but the number of collations is constantly growing ( It would be a good idea to change it to a hash lookup. Same can be done for character sets, even though the number of charsets didn't grow that much. |
Labels | tech_debt |
Labels | tech_debt | beginner-friendly tech_debt |
Hi Team,
can I look into this task ?