Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50107
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain openmv.com from 64.15.152.204 cause and error)
To: "'Stanley Sufficool'" <ssufficool@gmail.com>
Cc: <internals@lists.php.net>
References: <AANLkTikKybPrGWLj3rT3ydvf8H0N6O6mHP=MEmnL58Yh@mail.gmail.com>	<24c7fdf08ac80c097306908d0c4b5512.squirrel@www.l-i-e.com>	<AANLkTikifSrLNFu+Ui6ZtdkyOtmgbEF60=J-0UhRXEnJ@mail.gmail.com>	<ec385a4a428945f591e5748d6af8053f.squirrel@www.l-i-e.com> <AANLkTinFk6TC5OmUHExE7rwLKFh6mo_DWpbwP6dc2Pjw@mail.gmail.com>
In-Reply-To: <AANLkTinFk6TC5OmUHExE7rwLKFh6mo_DWpbwP6dc2Pjw@mail.gmail.com>
Date: Fri, 5 Nov 2010 09:26:45 -0400
Message-ID: <006101cb7ced$17dc5480$4794fd80$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: Act8phueZiX9KnKaT3OcUrgb/Gy4hgAMwxQg
Content-Language: en-ca
Subject: RE: [PHP-DEV] PDO_DBLIB Native PHP Type binding
From: jbondc@openmv.com ("Jonathan Bond-Caron")

On Fri Nov 5 12:57 AM, Stanley Sufficool wrote:
> >
> > And why is PHP client library using latin1 for data that just isn't=20
> > latin1? =A0That's just asking for problems...
>=20
> Theoretically I could ask for UTF8, but then I don't want to have to=20
> run utf8_decode/utf8_encode on all query strings, returned data, etc=20
> when the other drivers do not return unicode to PHP.
>=20

Have a look at:
https://open-mv.googlecode.com/svn/trunk/classes/database/drivers/

I've solved most of these problems though not with PDO* drivers.

I think you'll get the consistency you need for "2 interchangeable and =
have
PHP/PDO applications run the same on Win32 and Linux" only minus the
PDO/PDO_DBLIB part.

In my opinion, PDO already does too much "abstraction magic", it would =
be
great if PDO2? could expose somehow:

static inline void fetch_value()

so that in userland you could deal with custom data types and override =
how
the data type bindings happen.

That would be some much needed flexibility to actually create a =
"database
abstraction" layer vs the pdo "data-access" layer.

> >
> > My only answer to that is to change your code to not ask for =
'latin1'
> > in the first place, when the data isn't latin1. =A0Change the PHP
> client
> > charset to what it ought to be, and get the data you wanted, not=20
> > some lossy down-sampled useless conversion of the data you wanted.
> >
> > I cannot comment on SQL Server behaviour with respect to the=20
> > "servers code page" [sic], whatever that is, except to say that=20
> > MySQL lets you define your charset on a table by table basis, and, I =

> > think, in
> recent
> > versions, even on a field by field basis. OpenSource ftw, perhaps?=20
> > :-
> )
>=20
> MSSQL allows per table and per column code pages in recent versions.
> As far as OpenSource DBMS', I support what my clients run, not what I=20
> want them to run. If I had my choice, I would be running PostgreSQL.
>=20

Per column code pages / collation is actually part of SQL92 (postgresql
doesn't support it, mysql, mssql,.. does)

In windows, the SQL native driver will properly convert everything to =
UTF-8.
In unix, FreeTDS should do the conversion correctly, have you run into
problems? Is this related to the PDO driver?