Processing control commands:
> merge -1 886756
Bug #848603 [mariadb-server] Enable innodb_large_prefix
Unable to merge bugs because:
forwarded of #886756 is 'https://jira.mariadb.org/browse/MDEV-14904' not ''
severity of #886756 is 'serious' not 'normal'
blocks of #886756 is '891691' not ''
packag
2016-12-20 3:07 GMT+02:00 Christian Hofstaedtler :
> pdns-backend-mysql
I suggest you file a bug against this package. It should define a
per-database or per-table charset if it depends it to be of a certain
kind. The maintainer of that app knows best that the suitable charset
is, maybe ASCII for
* Otto Kekäläinen [161219 22:21]:
> We live in a world where WordPress sites expect to be able to save
> emojis in comments :)
Sure, but other apps expect their indexes to work.
> We have had utf8mb4 as default in Debian and Ubuntu for a many years.
Possibly, but it's only now the provider for
Severity: normal
We live in a world where WordPress sites expect to be able to save
emojis in comments :)
We have had utf8mb4 as default in Debian and Ubuntu for a many years.
You are experiencing a corner case with a single app (which one?).
On 18/12/2016 23:43, Christian Hofstaedtler wrote:
mariadb-server, the new default-mysql-server, breaks existing
well-functioning applications that need to index columns defined as
VARCHAR(255). This worked fine with mysql-server-5.6.
This is caused by two questionable choices:
* default cha
Package: mariadb-server
Version: 10.0.28-2
Severity: serious
mariadb-server, the new default-mysql-server, breaks existing
well-functioning applications that need to index columns defined as
VARCHAR(255). This worked fine with mysql-server-5.6.
This is caused by two questionable choices:
* def
6 matches
Mail list logo
