Prepare parametrized PG query for showing query parameters in web panel

[unavailabl3]

Since Rails 5 has parametrizied query statement like this:
SELECT * FROM 'items' WHERE 'item'.'id' = $1 [['id',123]]
So in panel we see $1 instead of 123
Params are not shown in rack-mini-profiler panel. This commit is a hack (ONLY FOR POSTGRESQL) to see params. Like this we can add for other DBs.
P.S. May be commit needs refactoring for optimization

[SamSaffron]

subbing is a bit confusing and can cause a nonsense query to be logged in some cases. For example:

$1 -> hello world's, which technically would need to be 'hello world''s' I think

[SamSaffron]

an alternative may be a preamble comment that explains the param so there is not confusion. also I think you technically want gsub here, also what if more than 10 params?

$1 -> \* $1 *\ 'hello-world''s'

[unavailabl3]

What will happen if more than 10 params?
Example from my project
SELECT tag_id FROM categories_tags WHERE category_id IN (11,3001,8794,8797,8788,8784,8783,3682,8789,3683,3680,3005,3686,3685,3684,3681,3679,8793,8787,3004,3006,8343,8791,8348,8354,3000,3003,3010,3007,3002,2999,8792,8795);

[nateberkopec]

This is still an issue on master, and there are no conflicts here, so despite the age I will leave this open.

[kbrock]

I like having the parameters separate. I want to know what is actually sent to the server. (easier to detect N+1).
But I use my own rack-mini-profiler client to fetch the sql, so I probably don't see the same issue.

Is the issue that the parameters are not showing in the UI?
Seems like a js/ui issue not a storage issue.

But comment if you feel we should modify the sql before we store it. I can look at this.

Also, historically, I was under the impression that people were concerned about the parameter values being leaked. It may be the reason the parameters were not included into the ui. Not sure if the hide parameter regex met people's concerns.