On 2007-12-05 Cristóbal Palmer wrote:
> On Tue, Dec 04, 2007 at 11:18:38PM +0100, Norbert Tretkowski wrote:
> > I've read the whole bugreport a few times now, and I think I have to
> > agree with Sean, we should switch the default charset for new databases
> > to utf8, but shouldn't touch existin
On Tue, Dec 04, 2007 at 11:18:38PM +0100, Norbert Tretkowski wrote:
> I've read the whole bugreport a few times now, and I think I have to
> agree with Sean, we should switch the default charset for new databases
> to utf8, but shouldn't touch existing ones.
Agreed. I think the easiest way to acco
Hi,
I've read the whole bugreport a few times now, and I think I have to
agree with Sean, we should switch the default charset for new databases
to utf8, but shouldn't touch existing ones.
Maybe I just don't see the real reason why MySQL decided to not use utf8
as default charset, I'll ask on the
Hi,
Cristóbal with ibiblio.org here. We recently handed off DocSouth
(http://docsouth.unc.edu/) from our servers to UNC libraries'. Because
of such changes and growth, we've been repeatedly exposed to encoding
problems such as the one the original reporter describes. UNC Library
systems has manage
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 b
Package: mysql-server
Version: 5.0.32-7etch1
The default character set for the mysql-server package is currently
latin1. See the server status notice after installing the package:
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
mysql> status;
--
mysql Ver 14.12 Distrib 5.0.38, for
6 matches
Mail list logo
