|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #16619 mysql module build-in binary-release doesn't support GBK charset
Submitted: 2002-04-15 08:57 UTC Modified: 2003-03-13 03:15 UTC
Avg. Score:4.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: Xuefer at 21cn dot com Assigned: zak (profile)
Status: Wont fix Package: MySQL related
PHP Version: 4.2.0 OS: win
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
From: Xuefer at 21cn dot com
New email:
PHP Version: OS:


 [2002-04-15 08:57 UTC] Xuefer at 21cn dot com
when MYSQL use GBK as default charset

the following error logged in apache

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

error.log get bigger and bigger by filling these rubbish message!

multi-byte charset in mysql-client can only be build in
not charsets\gbk.conf

binary-release should provoide as much as possible ability, right ?


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-04-15 12:40 UTC]
I think this is a MySQL problem, not a PHP problem.
 [2002-04-15 12:40 UTC]
I think this is a MySQL problem, not a PHP problem.
 [2002-04-15 22:28 UTC] Xuefer at 21cn dot com
Sorry, I don't agree with u, so I open it again

it's really the problem of client, not MySQL-server

i've tested in linux, source-package
installed MySQL with GBK support
and install php using bundled MySQL lib


PHP 4: Include MySQL support. DIR is the MySQL base directory. If _unspecified_, the _bundled_ MySQL library will be used. This option is turned on by default. 

there's no ctype-gbk.c in ext/mysql/libmysql.

and the client complain about "no such charset"
this is how the binary-package of php for win built, right?

is this problem i described clear enough?

but another relative problem:
build-in charset is so big, with a huge array,
i don't know if the build-in charset is a MUST in client, but it DID complain about it!
maybe this is MySQL problem not PHP :(

temp-solution for php-win:
"copy charset\latin1.conf to charset\gbk.conf"

this should have been told to users who prefer to GBK charset, agree?
 [2002-06-18 05:32 UTC]
Should be working as soon as the MySQL client libs are upgraded. Assigning this to Zak as he's going to update it.
 [2003-03-13 03:15 UTC]
This will be fixed in PHP 5 (with a new bundled lib).

If you need other charsets like default latin1 use an external libmysql.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Mon Jul 15 20:01:29 2024 UTC