Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130555
Precedence: list
MIME-Version: 1.0
References: <CALkpNnS0_9T421vjBoYxuqYKZoSWUMuOp7vGKCtQbZpSp17ivw@mail.gmail.com>
 <4d8d56c4522430326d796e240b24cdd2@glaive.pro>
In-Reply-To: <4d8d56c4522430326d796e240b24cdd2@glaive.pro>
Date: Fri, 3 Apr 2026 14:12:56 -0400
Message-ID: <CALkpNnStPLfoW8xwjjA79yXj3wUSgUH8YiS1dQhYPTxzAxP5Rw@mail.gmail.com>
Subject: Re: [PHP-DEV] PDO SQLite: statement attributes for SQL text retrieval
To: Juris Evertovskis <juris@glaive.pro>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000eb2e30064e924441"
From: ilia@ilia.ws (Ilia)

--000000000000eb2e30064e924441
Content-Type: text/plain; charset="UTF-8"

> But two things here are unclear to me:
> - What's insufficient with `->queryString` and other existing features?
> Does one of these overlap with `->queryString` or not?
>
The output of ATTR_SQL and queryString are essentially the same;
ATTR_EXPANDED_SQL is the novelty that gives you access to the resolved
prepared statement.  So the ATTR_SQL is there mostly for completion, if
ever something changes in terms of how PHP does pre-prepare handling this
could have utility.

- What's so special about SQLite? Wouldn't the same need be just as present
> for any other driver?
>
>
Nothing special, just that it provides library functionality to get this
data programmatically.

-- 
Ilia Alshanetsky
Technologist, CTO, Entrepreneur
E: ilia@ilia.ws
T: @iliaa
B: http://ilia.ws

--000000000000eb2e30064e924441
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=
=3D"font-size:10pt;font-family:Verdana,Geneva,sans-serif"><p>But two things=
 here are unclear to me:<br>- What&#39;s insufficient with `-&gt;queryStrin=
g` and other existing features? Does one of these overlap with `-&gt;queryS=
tring` or not?<br></p></div></blockquote><div>The output of=C2=A0ATTR_SQL a=
nd=C2=A0queryString are essentially the same; ATTR_EXPANDED_SQL is the nove=
lty that gives you access to the resolved prepared statement.=C2=A0 So the =
ATTR_SQL is there mostly for completion, if ever something changes in terms=
 of how PHP does pre-prepare handling this could have utility.</div><div><b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"fon=
t-size:10pt;font-family:Verdana,Geneva,sans-serif"><p>-=C2=A0What&#39;s so =
special about SQLite? Wouldn&#39;t the same need be just as present for any=
 other driver?</p>
<p></p></div></blockquote></div><div><br clear=3D"all"></div><div><font fac=
e=3D"Verdana, Geneva, sans-serif">Nothing special, just that it provides li=
brary functionality to get this data programmatically.=C2=A0=C2=A0</font></=
div><div><br></div><span class=3D"gmail_signature_prefix">-- </span><br><di=
v dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Ilia Alshanetsky<d=
iv>Technologist, CTO, Entrepreneur</div><div>E: <a href=3D"mailto:ilia@ilia=
.ws" target=3D"_blank">ilia@ilia.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>
</div>

--000000000000eb2e30064e924441--