Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98472
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADyq6sKixuVZVebpz3dMvn2Db-OnaHrCNQiAG=MeBK977XcEyw@mail.gmail.com>
References: <CADxrgCP4Mt=Jh_zi2qOXEyt2DTbnDFUb2gkxHg8NgeECL5j8_A@mail.gmail.com>
 <CADxrgCNXyWQ+3Uhiq7NECtVMi4EP29Kq_Qryr5rLDgfwGw93xQ@mail.gmail.com>
 <afae454c-3df4-7fa2-cf11-111e37d72184@beccati.com> <CADyq6sLPjVtENtpTJHYx2=oH7Qn=-XFiYDbzUNwjTVduDVUYTg@mail.gmail.com>
 <CADxrgCP0-fCsvYrCPTssF__WEcqp4ep67xyLksEme3MZKwVS-A@mail.gmail.com> <CADyq6sKixuVZVebpz3dMvn2Db-OnaHrCNQiAG=MeBK977XcEyw@mail.gmail.com>
Date: Fri, 10 Mar 2017 10:53:36 -0500
Message-ID: <CADxrgCOu5iW4q418ccotqds98bYfa_ZNBSZqS2HJza49jrPc+w@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: Matteo Beccati <php@beccati.com>, "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c088fb85c6658054a625db8
Subject: Re: [PHP-DEV] Re: [RFC] Extended String Types For PDO
From: adam.baratz@gmail.com (Adam Baratz)

--94eb2c088fb85c6658054a625db8
Content-Type: text/plain; charset=UTF-8

>
> I've read the links, hence my skepticism and me labeling this as "yet
> another way that SQL Server decides to make things harder and buggy". It is
> a bug in SQL Server, unless I'm missing the reason for this to exist (or
> maybe there was such a reason in 1991).
>

One of the links is MySQL specific. Apart from that, it's not accurate to
characterize this as a bug with MSSQL. They used part of the SQL spec in an
intended way. Yes, it's a little more cumbersome than having a single
string type, but it doesn't help PDO users to wish other designs onto DBs.

As for BC compliance, this will still break code, as current overrides to
> prepared statements (in DBAL, specifically) directly compare the parameter
> type to a constant (no bitmask comparison).
>

I meant that this change won't break existing code. But yes, others may
need to modify their code to be compatible with this new feature. Within
pdo, a bitmask is applied -- see uses of the PDO_PARAM_TYPE macro. It's
probably worth replicating that in DBAL.

Thanks,
Adam

--94eb2c088fb85c6658054a625db8--