Re: [GENERAL] Using the dollar sign as a prefix for named parameter of prepared statement.

2017-08-27 18:32 GMT+03:00 Dmitry Igrishin : > > > 2017-08-27 18:13 GMT+03:00 Tom Lane : > >> Dmitry Igrishin writes: >> > I'm working on finishing beta release of my C++ API for PostgreSQL. The >> > library >> > have simple SQL pars

Re: [GENERAL] Using the dollar sign as a prefix for named parameter of prepared statement.

2017-08-27 18:13 GMT+03:00 Tom Lane : > Dmitry Igrishin writes: > > I'm working on finishing beta release of my C++ API for PostgreSQL. The > > library > > have simple SQL parser (preprocessor) to support the queries like that: > > > SELECT :"column&

[GENERAL] Using the dollar sign as a prefix for named parameter of prepared statement.

Hi all, I'm working on finishing beta release of my C++ API for PostgreSQL. The library have simple SQL parser (preprocessor) to support the queries like that: SELECT :"column", $tag$constant string$tag$ FROM :tables WHERE name LIKE :'name' AND sex = $1 AND age > $ag

Re: [GENERAL] C++ port of Postgres

Hi Joy, 2016-08-15 0:05 GMT+03:00 Joy Arulraj : > Hi folks -- > > We have ported Postgres over to the C++ language (C++11 standard). > > https://github.com/jarulraj/postgresql-cpp > > Our goal is to use certain features of the C++ language and its standard > library to simplify coding, improve cod

Re: [GENERAL] RowDescription via the SQL?

2016-06-03 1:55 GMT+03:00 Merlin Moncure : > On Thu, Jun 2, 2016 at 1:14 AM, Dmitry Igrishin wrote: >> Hi, >> >> It's possible to query pg_prepared_statements view to obtain the >> information about >> parameters used in the statement that was prepare

[GENERAL] RowDescription via the SQL?

Hi, It's possible to query pg_prepared_statements view to obtain the information about parameters used in the statement that was prepared. But I don't found how to get the information about the rows that will be returned when the statement is eventually executed. (It's possible to get this informa

Re: [GENERAL] Session Identifiers

2015-12-20 21:00 GMT+03:00 Pavel Stehule : > > > 2015-12-20 18:56 GMT+01:00 Dmitry Igrishin : > >> >> >> 2015-12-20 19:44 GMT+03:00 Pavel Stehule : >> >>> >>> >>> 2015-12-20 17:30 GMT+01:00 Dmitry Igrishin : >>> >>>

Re: [GENERAL] Session Identifiers

2015-12-20 19:44 GMT+03:00 Pavel Stehule : > > > 2015-12-20 17:30 GMT+01:00 Dmitry Igrishin : > >> Can be totally different if you use some connection pooler like pgpool or >>> pgbouncer - these applications can reuse Postgres server sessions for more >>> us

Re: [GENERAL] Session Identifiers

> > Can be totally different if you use some connection pooler like pgpool or > pgbouncer - these applications can reuse Postgres server sessions for more > user sessions. > BTW, AFAIK, it's not possible to change the session authentication information by using SET SESSION AUTHORIZATION [1] if the

Re: [GENERAL] libpq: why only one PQsendQuery per connection at a time?

2015-01-04 19:02 GMT+03:00 : > Hello! > Question generally to (libpq) developers. > > According to http://www.postgresql.org/docs/9.4/static/libpq-async.html: > "PQsendQuery cannot be called again (on the same connection) until > PQgetResult > has returned a null pointer, indicating that the comma