Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL)
-
None
Attachments
Issue Links
- blocks
-
MDEV-8433 Make field<'broken-string' use indexes
- In Review
- is blocked by
-
MDEV-8214 Asian MB2 charsets: compare broken bytes as "greater than any non-broken character"
- Closed
-
MDEV-8215 Asian MB3 charsets: compare broken bytes as "greater than any non-broken character"
- Closed
-
MDEV-8415 utf8: compare broken bytes as "greater than any non-broken character"
- Closed
-
MDEV-8416 ucs2: compare broken bytes as "greater than any non-broken character"
- Closed
-
MDEV-8417 utf8mb4: compare broken bytes as "greater than any non-broken character"
- Closed
-
MDEV-8418 utf16: compare broken bytes as "greater than any non-broken character"
- Closed
-
MDEV-8419 utf32: compare broken bytes as "greater than any non-broken character"
- Closed
- relates to
-
MDEV-7649 wrong result when comparing utf8 column with an invalid literal
- Closed
-
MDEV-7128 Configuring charsets or collations as utf8 yields surprising result and leads to data loss
- Closed
-
MDEV-8420 UCA: compare broken bytes as "greater than any non-broken character"
- Open