Re: libpq PQexecParams & value placeholders

2018-12-20 Thread Merlin Moncure
On Fri, Dec 14, 2018 at 6:09 AM Oleg wrote: > > On Fri, Dec 14, 2018 at 02:47:12PM +0300, Dmitry Igrishin wrote: > > пт, 14 дек. 2018 г. в 14:33, Oleg : > > > > > > Hi, all. > > > > > > Do we really need a numeric value placeholders like $1 in command string? > > It's a syntax defined at the

Re: libpq PQexecParams & value placeholders

2018-12-14 Thread Oleg
On Fri, Dec 14, 2018 at 02:47:12PM +0300, Dmitry Igrishin wrote: > пт, 14 дек. 2018 г. в 14:33, Oleg : > > > > Hi, all. > > > > Do we really need a numeric value placeholders like $1 in command string? > It's a syntax defined at the backend side. >

Re: libpq PQexecParams & value placeholders

2018-12-14 Thread Dmitry Igrishin
пт, 14 дек. 2018 г. в 14:33, Oleg : > > Hi, all. > > Do we really need a numeric value placeholders like $1 in command string? It's a syntax defined at the backend side. (https://www.postgresql.org/docs/current/sql-prepare.html) > Construction of such string for complex non-static queries is very

libpq PQexecParams & value placeholders

2018-12-14 Thread Oleg
Hi, all. Do we really need a numeric value placeholders like $1 in command string? Construction of such string for complex non-static queries is very annoying. Why do we can't simply use $$ placeholder, which take the next value from an array of values? -- Олег Неманов (Oleg Nemanov)