reopen 438970 thanks hey guys,
guess i missed the bug and initial discussion, i must have been automatically
unsubscribed from pkg-mysql-maint when my mail server went down a few weeks
ago.
anyway, first things first, i'm reopening the bug since even if it will never
be implemented it would be more proper to tag it wontfix and leave it open as
opposed to closing it.
however, i would argue that we *should* switch default charsets, and as far as
where we are in the release cycle i think approximately now is a really good
time to do so. after all, wasn't pervasive utf8 support a release goal of
debian >= etch?
of course, the devil is in the details, since we would need to make sure that
any such switch didn't cause problems for existing users. assuming that it
doesn't introduce any problems, i'd propose something like the following:
- make whatever modifications are necessary to the initial bootstrapping code
for first-time installs so that default databases/tables are utf8
- have my.cnf default to utf8 (this shouldn't affect existing tables/databases
right?)
- not attempt to convert anything from existing installs
- place lots of scary warnings in the changelog and NEWS.Debian
- make sure the release notes for lenny address this
sean
signature.asc
Description: This is a digitally signed message part.
