Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39734
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain phpdoc.de from 212.227.126.188 cause and error)
Message-ID: <489B03FB.9070308@phpdoc.de>
Date: Thu, 07 Aug 2008 16:17:31 +0200
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Stanislav Malyshev <stas@zend.com>
CC: 'PHP Internals' <internals@lists.php.net>
References: <4899D1F2.2060101@zend.com> <4899F71D.8010306@phpdoc.de>
In-Reply-To: <4899F71D.8010306@phpdoc.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] mysql_set_charset
From: ulf.wendel@phpdoc.de (Ulf Wendel)

Ulf Wendel schrieb:
> I don't recall why I added "usage not recommended" to the test. Let me 
> check with Georg. He had some concerns on the function as far as I 
> remember.

I checked with Georg. My memories regarding Georg's position are totally 
wrong. He once introduced mysql_set_charset to the MySQL Client Library 
(AKA "libmysql" - marketing gets confused when I use libmysql, sorry).

He explained to me that using SET NAMES is what is not recommended when 
using libmysql because:

  - there is no verification if the client knows the charset
  - the internal mysql->charset field will not be set properly

I don't know how that "usage not recommended" comment has crept in the 
test. Probably my fault...

Ulf