 |
2018-10-11_10-23-21.png (65,196 bytes) |
|
|
Well I just realized my problem. It seems that bind variables are represented by $ followed by a number in postgresql. And that works just fine (thank you BTW - love this feature). If I can I'd love to change this to a feature request: could we have a dropdown to automatically convert between bind variable syntax. This will allow users to use a query with bind variables on a different DB and also if the dropdown defaults to the syntax for the current DB it would help the user know what the right syntax is. This will also help users (like me) when they have a SQL statement dumped from code that is parameterized with "?" and let them easily convert it to the appropriate bind variable syntax. Before I had to go ? by ? and replace it with an appropriate value to test a query that was giving me trouble in our application. |
 |
Hello Carlos, Unnamed '?' parameters were supposed to work, too, they are prepared the same way, I'll figure out why they are not applied. |
|
|
Looks like libpq library doesn't support '?' parameters https://www.postgresql.org/docs/current/static/libpq-exec.html What client do you use? Maybe it implements '?' parameters on its own. Anyway, conversion within the application would be helpful. |
|
|
Now unnamed parameters are supported for all databases, including PostgreSQL |
 |
Let me add -- Valentina Studio 9.6 on the fly replace ? to syntax which PostgreSQL understands. |
- Anonymous
