Hi, would not recommend anyone to use any "possibly more than one byte per glyph charset" because I need the full content varchar(64000) column to store CERT, RRSIG and long TXT records.
I would recommend to define "content varchar(64000) character set ascii default null" to avoid that people insert TXT records like the following: "“v=spf1 mx ip4:193.168.50.0/24 –all”" It is unlikely that this information can be used by any mailserver. Best regards Thomas On 8/17/19 9:17 PM, Kevin Olbrich wrote: > Hi! > > Why is PDNS explicitly using latin1? > https://github.com/PowerDNS/pdns/blob/master/modules/gmysqlbackend/schema.mysql.sql > > From what I understand, utf8mb4 / utf8mb4_unicode_520_ci is the best > charset / collation for MySQL / MariaDB atm. > Sure, PDNS uses IDNA and does not need unicode but wouldn't it be the > better default than latin1? > > Kind regards > Kevin > > _______________________________________________ > Pdns-users mailing list > Pdns-users@mailman.powerdns.com > https://mailman.powerdns.com/mailman/listinfo/pdns-users > _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
