289107 - Can't connect to MySQL if charset is UTF-8 and old version of Perl package

Status: RESOLVED DUPLICATE of bug 288539

(Bugzilla :: Documentation, defect)

Description

[Normann Aa. Nielsen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

The documentation is referring to an old version of the Perl package DBD-mysql
that gives problems. When the default charset of MySQL is configured to use
UTF-8 as default charset, you might get troubles with the mentioned package. The
problem results in an error message.


This error can be avoided by using a more recent version of the DBD-mysql
package than.

Reproducible: Always

Steps to Reproduce:
1. Have a MySQl installation with UFT-8 as default charset (for example version
4.1.10nt).
2. Follow the guidelines in the documentation
mozilla-org/html/projects/bugzilla/docs/win32install.html
3. Make sure that the DBD-mysql has a version something like 2.9002


Actual Results:  
The perl-procedure checksetup.pl cannot connect to the MySQL server, but return
the following message:

File 'C:\mysql\\share\charsets\?.conf' not found (Errcode: 2)
Character set '#33' is not a compiled character set and is not
specified in the 'C:\mysql\\share\charsets\Index' file


Expected Results:  
The documentation should refer to a newer version of the Perl-package:

install http://theoryx5.uwinnipeg.ca/ppms/DBD-mysql.ppd

(see also:
http://www.issociate.de/board/post/186815/%5BFwd:_Re:_UTF-8_problem_with_Win32_and_MySQL_4.1.10%5D.html
)

Comment 1

[Max Kanat-Alexander]

Actually, this will be handled simply by our increasing the required DBD::mysql,
which we have to do anyway. :-)

*** This bug has been marked as a duplicate of 288539 ***