Hello everybody,
I'd like to start a discussion on a new RFC about fixing the default PDO
SQL parser and having (optional) driver-specific parsers.
https://wiki.php.net/rfc/pdo_driver_specific_parsers
Thanks GPB and Tom de Wit for their help with initial proof-reading.
Cheers
--
Matteo
Hi all!
Voting ended and Derick's script counted the votes [1].
Our "rookie" PHP 8.4 release managers are:
- Calvin Buckley
- Saki Takamachi
Our "veteran" is the PHP 8.3 release manager Eric Mann.
Further steps are described in the New release manager checklist [2],
I believe you can discuss
Hi Matteo,
> 2024/04/17 21:24、Matteo Beccati のメール:
>
> Hello everybody,
>
> I'd like to start a discussion on a new RFC about fixing the default PDO SQL
> parser and having (optional) driver-specific parsers.
>
> https://wiki.php.net/rfc/pdo_driver_specific_parsers
>
> Thanks GPB and Tom de
Hey Larry,
Il 17/04/2024 16:51, Larry Garfield ha scritto:
This all seems logical, but having separate parsers would mean that the SQL
strings are no longer portable, yes? Eg, many frameworks and CMSes try to
(claim to) support multiple DBs transparently. (MySQL and Postgres and SQLite,
Hi Saki,
Il 17/04/2024 16:03, Saki Takamachi ha scritto:
This is a very interesting topic for me. A few days ago I saw an issue that was
largely related to this.
https://github.com/php/php-src/issues/13958
It seems possible to get around this problem using some hacks, but essentially
I agree
On Apr 17, 2024, at 9:24 AM, Matteo Beccati wrote:
>
> Hello everybody,
>
> I'd like to start a discussion on a new RFC about fixing the default PDO SQL
> parser and having (optional) driver-specific parsers.
>
> https://wiki.php.net/rfc/pdo_driver_specific_parsers
>
> Thanks GPB and Tom de
Il 17/04/2024 15:38, Sergey Panteleev ha scritto:
Hi all!
Voting ended and Derick's script counted the votes [1].
Our "rookie" PHP 8.4 release managers are:
- Calvin Buckley
- Saki Takamachi
Our "veteran" is the PHP 8.3 release manager Eric Mann.
Congrats to the RMs!
Cheers
--
Matteo
Hi Matteo,
> Thanks for the feedback. I will reference this issue as duplicate too in the
> RFC.
Thanks for the reference to the issue.
> I'm certain if we dig deep enough we'll find a few more.
Agree. Maybe we can find something other than PostgreSQL.
I have read through your RFC. If we
On Wed, Apr 17, 2024, at 2:45 PM, Matteo Beccati wrote:
> Hi Saki,
>
> Il 17/04/2024 16:30, Saki Takamachi ha scritto:
>> Hi Matteo,
>>
>>> Thanks for the feedback. I will reference this issue as duplicate too in
>>> the RFC.
>>
>> Thanks for the reference to the issue.
>>
>>
>>> I'm certain
Hi Saki,
Il 17/04/2024 16:30, Saki Takamachi ha scritto:
Hi Matteo,
Thanks for the feedback. I will reference this issue as duplicate too in the
RFC.
Thanks for the reference to the issue.
I'm certain if we dig deep enough we'll find a few more.
Agree. Maybe we can find something
I think the question here was more about what the syntax will be after the
parameters are substituted. But if I recall correctly, the quoting is done
by PDO:: quote so the syntax will remain the same. Only the buggy behavior
would be fixed when it comes to recognizing parameters.
On Wed, Apr 17, 2024, at 4:19 PM, Matteo Beccati wrote:
> Hey Larry,
>
> Il 17/04/2024 16:51, Larry Garfield ha scritto:
>> This all seems logical, but having separate parsers would mean that the SQL
>> strings are no longer portable, yes? Eg, many frameworks and CMSes try to
>> (claim to)
Hi,
On Wed, 17 Apr 2024, at 19:25, Kamil Tekiela wrote:
> I think the question here was more about what the syntax will be after the
> parameters are substituted. But if I recall correctly, the quoting is done by
> PDO:: quote so the syntax will remain the same. Only the buggy behavior would
>
13 matches
Mail list logo
