Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57913
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain oracle.com from 148.87.113.117 cause and error)
To: Daniel Convissor <danielc@analysisandsolutions.com>
Cc: PHP Internals List <internals@lists.php.net>,
        Ulf Wendel
 <ulf.wendel@oracle.com>
In-Reply-To: <20120217133811.GA17442@panix.com>
References: <20111118210619.GA13490@panix.com>
	 <1326977447.2722.10.camel@guybrush> <20120121133107.GA7255@panix.com>
	 <1327311604.5972.51.camel@guybrush> <20120124025600.GA337@panix.com>
	 <20120217133811.GA17442@panix.com>
Content-Type: text/plain; charset="UTF-8"
Organization: Oracle Corporation
Date: Tue, 21 Feb 2012 12:37:34 +0100
Message-ID: <1329824254.22794.16.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] mysqli_fetch_field() mysqlnd & libmysql differences
From: johannes.schlueter@oracle.com (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2012-02-17 at 08:38 -0500, Daniel Convissor wrote:
> > A related problem was found by the test script.  libmysql is completely
> > ignoring the character set information in my.cnf.  Plus, if one forces a
> > character set by calling options(SET NAMES utf8) before connecting,
> > character_set_name() still returns unexpected information.
> > 
> > Can you please take a look at this test script:
> > http://www.analysisandsolutions.com/php/libmysql.ignoring.character.set.php
> 
> Can one of you please examine why libmysql is not acting as documented
> and reply here in the near future?

In my tests it worked like I expect:
- the initial charset is the one configured
- changing the charset affects the behavior

Mind two things:

1) You said

 * /etc/my.cnf settings are (no other my.cnf files exist):
 * + default-character-set = utf8
 * + character-set-server = utf8

In which section of the my.cnf file? Both for the server, or for the
client?

2) SET NAMES changes the setting on the server. The client won't know
about this and still assume the old charset was used. Use
mysqli_set_charset().

In summary: charsets and encoding are a mess, especially if you have
many places to configure those. One small oversight and all is messed.

As reference:
http://dev.mysql.com/doc/refman/5.5/en/charset-configuration.html

johannes

> Thanks,
> 
> --Dan
> 
> -- 
>  T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
>             data intensive web and database programming
>                 http://www.AnalysisAndSolutions.com/
>  4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409
>