pub const MYSQL_COLLATIONS: &[&str];Expand description
Every collation MySQL 9.7.2 or MariaDB 12.3.3 serves, read from
their own information_schema.collations — 575 names, sorted for
binary_search.
The union, because SPG answers to both. The first version was MySQL’s alone, and MariaDB’s UCA-14.0.0 family — which MySQL does not have, and which the drop-in acceptance suite declares its MariaDB column with — became “no such collation”. Every query against that table then returned nothing: five drop-in cases failed at once, in CI, on a suite the local gates do not run. 289 of these names are MariaDB’s alone and 23 are MySQL’s.
v7.39.2 — the check this replaces was a SUFFIX: any name ending in
_ci, _cs or _bin counted as known. SELECT 'a' COLLATE nosuch_ci was therefore accepted and then silently ignored — the
comparison did whatever the session would have done anyway, and a
client that named a collation got no signal that it had not been
used. MySQL 9.7.2 answers ERROR 1273 (HY000): Unknown collation: 'nosuch_ci'.