Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130542
Precedence: list
MIME-Version: 1.0
Date: Fri, 3 Apr 2026 08:29:34 -0400
Message-ID: <CALkpNnS0_9T421vjBoYxuqYKZoSWUMuOp7vGKCtQbZpSp17ivw@mail.gmail.com>
Subject: [PHP-DEV] PDO SQLite: statement attributes for SQL text retrieval
To: PHP Developers Mailing List <internals@lists.php.net>
Cc: saki@php.net
Content-Type: multipart/alternative; boundary="000000000000eb86e0064e8d787c"
From: ilia@ilia.ws (Ilia)

--000000000000eb86e0064e8d787c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi internals,

I'm looking for feedback on a small pdo_sqlite addition.

PR: https://github.com/php/php-src/pull/21456
Implements: https://github.com/php/php-src/issues/21322

Two new read-only statement attributes on Pdo\Sqlite:
- Pdo\Sqlite::ATTR_SQL =E2=80=94 original SQL text of a prepared statement =
(via
sqlite3_sql())
- Pdo\Sqlite::ATTR_EXPANDED_SQL =E2=80=94 SQL with bound parameters inlined=
 (via
sqlite3_expanded_sql())

$stmt =3D $db->prepare('SELECT :name AS greeting');
$stmt->bindValue(':name', 'hello');
$stmt->execute();

$stmt->getAttribute(Pdo\Sqlite::ATTR_SQL);          // "SELECT :name AS
greeting"
$stmt->getAttribute(Pdo\Sqlite::ATTR_EXPANDED_SQL); // "SELECT 'hello' AS
greeting"

This mirrors SQLite3Stmt::getSQL() from the non-PDO API, but uses PDO's
getAttribute() mechanism rather than adding a driver-specific method. The
attribute system is how PDO drivers expose driver-specific functionality,
so it's a natural fit.

ATTR_EXPANDED_SQL is gated behind a configure check for
sqlite3_expanded_sql availability.

I don't think this needs a full RFC given the scope (two read-only
attributes, single driver, no BC impact), but I wanted input from the list.

Thoughts?

--=20
Ilia Alshanetsky
Technologist, CTO, Entrepreneur
E: ilia@ilia.ws
T: @iliaa
B: http://ilia.ws

--000000000000eb86e0064e8d787c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi internals,<br><br>I&#39;m looking for feedback on =
a small pdo_sqlite addition.<br><br>PR: <a href=3D"https://github.com/php/p=
hp-src/pull/21456">https://github.com/php/php-src/pull/21456</a><br>Impleme=
nts: <a href=3D"https://github.com/php/php-src/issues/21322">https://github=
.com/php/php-src/issues/21322</a><br><br>Two new read-only statement attrib=
utes on Pdo\Sqlite:<br>- Pdo\Sqlite::ATTR_SQL =E2=80=94 original SQL text o=
f a prepared statement (via sqlite3_sql())<br>- Pdo\Sqlite::ATTR_EXPANDED_S=
QL =E2=80=94 SQL with bound parameters inlined (via sqlite3_expanded_sql())=
<br><br>$stmt =3D $db-&gt;prepare(&#39;SELECT :name AS greeting&#39;);<br>$=
stmt-&gt;bindValue(&#39;:name&#39;, &#39;hello&#39;);<br>$stmt-&gt;execute(=
);<br><br>$stmt-&gt;getAttribute(Pdo\Sqlite::ATTR_SQL); =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0// &quot;SELECT :name AS greeting&quot;<br>$stmt-&gt;getAt=
tribute(Pdo\Sqlite::ATTR_EXPANDED_SQL); // &quot;SELECT &#39;hello&#39; AS =
greeting&quot;<br><br>This mirrors SQLite3Stmt::getSQL() from the non-PDO A=
PI, but uses PDO&#39;s getAttribute() mechanism rather than adding a driver=
-specific method. The attribute system is how PDO drivers expose driver-spe=
cific functionality, so it&#39;s a natural fit.<br><br>ATTR_EXPANDED_SQL is=
 gated behind a configure check for sqlite3_expanded_sql availability.<br><=
br>I don&#39;t think this needs a full RFC given the scope (two read-only a=
ttributes, single driver, no BC impact), but I wanted input from the list.<=
br><br>Thoughts?<br><br></div><span class=3D"gmail_signature_prefix">-- </s=
pan><br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_=
signature"><div dir=3D"ltr">Ilia Alshanetsky<div>Technologist, CTO, Entrepr=
eneur</div><div>E: <a href=3D"mailto:ilia@ilia.ws" target=3D"_blank">ilia@i=
lia.ws</a></div><div>T: @iliaa=C2=A0</div><div>B: <a href=3D"http://ilia.ws=
" target=3D"_blank">http://ilia.ws</a></div></div></div></div>

--000000000000eb86e0064e8d787c--