Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123149
Content-Type: text/plain;
	charset=utf-8
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: [PHP-DEV] [RFC][Discussion] PDO driver specific parsers
In-Reply-To: <ff5785b8-ba73-4302-9e1a-afaba34650bb@beccati.com>
Date: Wed, 17 Apr 2024 12:01:08 -0300
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <821F0B74-B24B-4309-B2BF-FFC7D5E009CE@cmpct.info>
References: <ff5785b8-ba73-4302-9e1a-afaba34650bb@beccati.com>
To: Matteo Beccati <php@beccati.com>
From: calvin@cmpct.info (Calvin Buckley)

On Apr 17, 2024, at 9:24=E2=80=AFAM, Matteo Beccati <php@beccati.com> =
wrote:
>=20
> Hello everybody,
>=20
> I'd like to start a discussion on a new RFC about fixing the default =
PDO SQL parser and having (optional) driver-specific parsers.
>=20
> https://wiki.php.net/rfc/pdo_driver_specific_parsers
>=20
> Thanks GPB and Tom de Wit for their help with initial proof-reading.
>=20
>=20
> Cheers
> --=20
> Matteo Beccati
>=20
> Development & Consulting - http://www.beccati.com/

FWIW, ODBC would annoyingly complicate things by not exposing a single
dialect, but it handles placeholders directly, so it hasn't needed to
parse queries. Using standard SQL quoting would probably work for most
drivers though if it comes to it.=