Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32075
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mysql.com from 213.136.52.68 cause and error)
Message-ID: <46DFB3E6.5070002@mysql.com>
Date: Thu, 06 Sep 2007 10:01:42 +0200
Organization: MySQL AB
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061211 SeaMonkey/1.0.7
MIME-Version: 1.0
To: BuildSmart <buildsmart@daleenterprise.com>
CC: PHP Developers Mailing List <internals@lists.php.net>
References: <CCA533C4-E8E2-4F77-99CD-FDB9ECC5E2EA@daleenterprise.com>
In-Reply-To: <CCA533C4-E8E2-4F77-99CD-FDB9ECC5E2EA@daleenterprise.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] proof of concept or undocumented?
From: hartmut@mysql.com (Hartmut Holzgraefe)

BuildSmart wrote:
> I see that the mysqli extension is essentially a wrapper and it obtains=
=20
> the required libraries from the mysql_config script so if mysql is buil=
t=20
> with ssl support the mysqli module will include this library and=20
> theoretically should work with ssl connections.
>=20
> My question though is related to the mysql module itself which doesn't =

> have any ARGS for ssl support or a method to automatically retrieve=20
> dependant libraries and is more of a client=20

When talking about "the mysql module" itself you're talking about
ext/mysql, right?

ext/mysql development has been discontinued in favor of ext/mysqli,
one of the goals was to integrate support for exactly SSL and the
other new connection options like gzip compressed connections that
are available as of MySQL 4.1.

See also http://php.net/mysql:

   Although this MySQL extension is compatible with MySQL 4.1.0
   and greater, it doesn't support the extra functionality that
   these versions provide. For that, use the MySQLi extension.

By that time the codebase of ext/mysql had become a bit of a mess.
It was one of the first PHP extensions ever and there were a few
design decisions made back then that made it almost impossible to
add new features to the existing functions (e.g. the db handle
being an optional parameter at the *end* of most functions
argument list made it impractical to add any further parameters).
The code was also full of conditional compile branches as it
supported mysql client libraries back to at least MySQL 3.23.

 > so before submitting a
 > feature request , writing a proof of concept or working on code for a
 > capability that might already exists but is undocumented, I thought I'=
d
 > ask first.

It doesn't really make sense to add a feature request for a
deprecated extension. All further development effort will
go into ext/mysqli only.

I just checked the manual pages for ext/mysql and ext/mysqli
and found that we're not really making this clear in the
documentation, i'll bring this up with the ext/mysqli maintainers
today and we'll have http://php.net/mysql be more explicit
about this.

--=20
Hartmut Holzgraefe, Principal Support Engineer
               .
Discover new MySQL Monitoring & Advisory features at:
http://www.mysql.com/products/enterprise/whats_new.html

Hauptsitz: MySQL GmbH, Dachauer Str.37, 80335 M=FCnchen
Gesch=E4ftsf=FChrer: Kaj Arn=F6 - HRB M=FCnchen 162140