Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98407
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADxrgCNXyWQ+3Uhiq7NECtVMi4EP29Kq_Qryr5rLDgfwGw93xQ@mail.gmail.com>
References: <CADxrgCP4Mt=Jh_zi2qOXEyt2DTbnDFUb2gkxHg8NgeECL5j8_A@mail.gmail.com>
 <CADxrgCNXyWQ+3Uhiq7NECtVMi4EP29Kq_Qryr5rLDgfwGw93xQ@mail.gmail.com>
Date: Mon, 6 Mar 2017 08:40:02 +0100
Message-ID: <CADyq6sJYvrQt9fYz-LZfPYZ68ibjUP4pkCCaRTYX+0uLyTVuLw@mail.gmail.com>
To: Adam Baratz <adam.baratz@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114a8baae1b522054a0b003f
Subject: Re: [PHP-DEV] Re: [RFC] Extended String Types For PDO
From: ocramius@gmail.com (Marco Pivetta)

--001a114a8baae1b522054a0b003f
Content-Type: text/plain; charset=UTF-8

Reading some random documents online (bear with me, doing it from the
phone), this seems to be irrelevant for MySQL, and an edge case dealing
with MSSQL. Is there a runnable functional test case demonstrating the
practical issue behind this addition?

Asking because of the same reasons I posted above.

On 3 Mar 2017 4:47 p.m., "Adam Baratz" <adam.baratz@gmail.com> wrote:

> >
> > Based on some pain points with my team and things I've heard from others,
> > I created an RFC to handle "national" character sets for emulated
> prepared
> > statements:
> > https://wiki.php.net/rfc/extended-string-types-for-pdo
> >
>
> Thanks all for the feedback so far. I updated the RFC based on what I
> heard. Hopefully it clarifies some of the ambiguities mentioned and the
> motivation for making this change. It's ultimately about helping PDO
> articulate part of the SQL spec.
>
> Let me know if you have any new questions/concerns.
>
> Adam
>

--001a114a8baae1b522054a0b003f--