Re: Re: [RFC] Debugging PDO Prepared Statement Emulation v2
| From: | Benoit Schildknecht | Date: | Fri, 02 Dec 2016 22:43:06 +0000 |
| Subject: | Re: Re: [RFC] Debugging PDO Prepared Statement Emulation v2 | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-97270@lists.php.net to get a copy of this message | ||
Le Fri, 02 Dec 2016 14:54:04 +0100, Matteo Beccati <php@beccati.com> a écrit:
On 02/12/2016 08:36, Thomas Nunninger wrote: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.Hi,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. CheersSo, 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_TI 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.