Bug 92604

Summary: mysql41-client broken with non-default character set
Product: Ports & Packages Reporter: Blaz Zupan <blaz>
Component: Individual Port(s)Assignee: Alex Dupre <ale>
Status: Closed FIXED    
Severity: Affects Only Me CC: ale
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Blaz Zupan 2006-01-31 13:10:02 UTC 
The databases/mysql41-client and probably databases/mysql50-client don't
work correctly on a machine where only the client port is installed and you
set the character set with WITH_CHARSET and/or WITH_XCHARSET.

Fix: 

Temporary workaround is to install the mysql41-server port on the client
machine. The correct fix is to move the installation of
/usr/local/share/mysql/charsets from mysql41-server to mysql41-client.
How-To-Repeat: 
Install databases/mysql41-server on a server and databases/mysql41-client on
the client machines. Both should be compiled with WITH_CHARSET=latin2 and
WITH_XCHARSET=all. Try to run a query on the client by connecting to the
server. Here is an example notice from a PHP script running on the client:

Warning: mysql_connect() [function.mysql-connect]: Can't initialize
character set latin2 (path: /usr/local/share/mysql/charsets/) in
somescript.php on line 16
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2006-01-31 21:32:08 UTC 
Class Changed
From-To: maintainer-update->change-request

Fix category (submitter is not maintainer)
Comment 2 Edwin Groothuis freebsd_committer freebsd_triage 2006-01-31 21:32:20 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ale

Over to maintainer
Comment 3 Martin Wilke freebsd_committer freebsd_triage 2009-05-17 11:49:09 UTC 
State Changed
From-To: open->feedback

Is this still an issue particularly in 50,51,60 ?
Comment 4 Martin Wilke freebsd_committer freebsd_triage 2009-05-17 11:58:56 UTC 
State Changed
From-To: feedback->closed

submitter mail reject.