This also makes the duplicate count incorrect I think as its comparing queries with placeholders and not queries with values actually used

See #26135, #28852

Set to "closed" on behalf of @chmst by The JTracker Application at issues.joomla.org/joomla-cms/29951

#28852 is completely unrelated.

This still seems to be present in Joomla 4.0.3 and as the original poster stated makes it almost impossible to debug withou changing the code with lots of echo statements
Whilst the params button does show the parameters used it is s fair bit of work cutting and pasting if you want to replicate the statement for testing in phpMyAdmin

It is intended. This is why prepared statements increase the security of the system.

I understand that. But if I have debug on I can see the SQL statement with
placeholders. I can also see the parameters so with a bit of "cut and
paste" it is possible to recreate the statement and test it in phpMyAdmin.
This is often useful when debugging.

So my question really I guess is can we have the option to see the SQL
statement with the values filled in - I do not see how this will compromise
the system.

On Tue, 5 Oct 2021 at 18:04, Christiane Maier-Stadtherr <
@.***> wrote:

It is intended. This is why prepared statements increase the security of
the system.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#29951 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUEV557JEOEKN6WESLUX5LUFKPPPANCNFSM4OQLC5EA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.