Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 129716

Summary: MySQL defaults to utf-8
Product: Gentoo Linux Reporter: Aury Fink Filho <nuny>
Component: EclassesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED INVALID    
Severity: normal    
Priority: High    
Version: 2005.1   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Aury Fink Filho 2006-04-12 10:30:21 UTC
I recently upgraded to mysql-4.1.14-r1, and all my PHP applications started to display strange chars when displaying queries returned by mysql.

I found that in mysql.eclass, was changed from latin1 to utf8. The problem is that  PHP doesn't honors my.cnf and uses the default charset compiled in mysql.

A way to change the default charset that mysql is compiled is needed.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-04-12 10:42:10 UTC
You can complain upstream, it's their default value, nothing prevents you from setting a different one in my.cnf or per-databases or whatever. This is not a bug. 

File a new bug about php if you wish (though we are already aware of the issue).
Comment 2 Aury Fink Filho 2006-04-12 11:42:49 UTC
But how can I change the default compiled language ? AFAIK, the only way is to change mysql.eclass
Comment 3 Maik Eichel 2006-04-12 14:17:36 UTC
Same problems here, but i think it isn't a mysql or php bug.

Some error:

illegal mix of collations (latin1_swedish_ci,implicit) and (utf8_general_ci,coercible) for operation '='

---8<--------

The 'my.cnf' is configured to latin1.
On my Webpage they print '
Comment 4 Maik Eichel 2006-04-12 14:17:36 UTC
Same problems here, but i think it isn't a mysql or php bug.

Some error:

illegal mix of collations (latin1_swedish_ci,implicit) and (utf8_general_ci,coercible) for operation '='

---8<--------

The 'my.cnf' is configured to latin1.
On my Webpage they print 'ä' as "ä" aso.

Thats since i upgrade three packets on 11.04.2006 with the daily portage-tree.
A downgrade to mysql-4.1.14 didn't change the situation.