Le Fri, 02 Dec 2016 14:54:04 +0100, Matteo Beccati <p...@beccati.com> a
écrit:
On 02/12/2016 08:36, Thomas Nunninger wrote:
Hi,
So, if I only want to get the emulated prepared statement, I have to do
ob_start()/ob_get_clean(), then use a regexp to fetch it ? I want v1
back T_T
I second that. Why do you print it directly? Wouldn't it be better to
return a structured array with the information needed? If needed, you
can var_dump() the array yourself.
Could you please explain what's the use case? As far as I'm concerned
such information would only be useful during PDO driver development,
phpt files and bug reporting / fixing.
Cheers
It's pretty simple : debugging and optimizing scripts and statements. I've
lost hours, manually emulating tons of statements, or trying to guess
what's happening when I have something like 1000+ prepared values (mass
insert). And since I have to do it by hand, mistakes happen, so I lose
even more time debugging my emulations. Having a direct access to the
emulated statements, without having to dirtily parse a dump, will be a
huge plus for me, my team and the performances of my debug component.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
