Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97291
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <op.yru714ajhuszwh@tsukapiou.home>
References: <CADxrgCOPNDSKhptKqa-CYF9mOscJHHN+fx19pWyQiqJVdGigCQ@mail.gmail.com>
 <op.yrtb5yadhuszwh@tsukapiou.home> <758680d9-cfe2-4a93-3831-7aa03b4bc9db@nunninger.info>
 <ae327680-59a2-bf5f-bbc9-3afcfa6a6248@beccati.com> <op.yru714ajhuszwh@tsukapiou.home>
Date: Mon, 5 Dec 2016 13:30:40 -0500
Message-ID: <CADxrgCMQCovAvNRw8hrr0fK9uUTm+jW8Ai_=pGjzt8OMVn6wzQ@mail.gmail.com>
To: Benoit Schildknecht <bensor987@neuf.fr>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c05e3a82a8adc0542ed7ced
Subject: Re: [PHP-DEV] Re: [RFC] Debugging PDO Prepared Statement Emulation v2
From: adambaratz@php.net (Adam Baratz)

--94eb2c05e3a82a8adc0542ed7ced
Content-Type: text/plain; charset=UTF-8

>
> 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.
>>
>
> 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.


I understand the use case -- I submitted the "v1" RFC, after all -- but the
discussion for the last RFC seemed to stall at an "agree to disagree"
stage. My hope with "v2" is that it'll be favored more than the first one,
which basically squeezed past the required margin for acceptance.

That said, do you have thoughts on a third approach? It might be that we
should do what Matteo suggested earlier in this thread: make something more
robust for getting structured data out of statements. To be honest, the v2
RFC does exactly what I need. It'll let me write .phpt tests and do one-off
debugging.

But if your take is that simply that you prefer v1 over v2, the regular
vote should cover that.

Thanks,
Adam

--94eb2c05e3a82a8adc0542ed7ced--