Re: Re: [RFC] Extended String Types For PDO
| From: | Matteo Beccati | Date: | Thu, 09 Mar 2017 10:03:13 +0000 |
| Subject: | Re: Re: [RFC] Extended String Types For PDO | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-98453@lists.php.net to get a copy of this message | ||
Hi Adam,
On 03/03/2017 16:47, Adam Baratz 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.
I'm sorry for being late to the party. I too have some doubts, but
having clarified the fact that national character types are a SQL-92
standard clears some of them.
However, I see no reference about the expected input/output encoding
(Unicode data is a bit vague). Is it expected to be UFT-8? Or maybe
match the internal encoding of the driver (e.g. UTF-16?)? What happens
if I try to quote a latin1 string?
Cheers
--
Matteo Beccati
Development & Consulting - http://www.beccati.com/