2013/6/28 Albe Laurenz
> Dmitriy Igrishin wrote:
> >> Since there can be only one unnamed prepared statement per
> >> session, there should be only one such object per connection.
> >> It should not get deallocated; maybe it could be private to the
> >> connection, which only offers a "parseUnnam
2013/6/26 Albe Laurenz
> Dmitriy Igrishin wrote:
> >> I understand the problem now.
> >> I pondered a bit over your design, and I came up with a different
> >> idea how to represent prepared statements in a C++ library.
>
> >> First, a prepared statement is identified by its name.
> >> To make th
2013/6/25 Albe Laurenz
> Dmitriy Igrishin wrote:
> While developing a C++ client library for Postgres I felt lack of
> extra
> information in command tags in the CommandComplete (B) message [...]
>
> >>> It seems like bad design to me to keep a list of prepared statements
> >>> on the c
2013/6/24 Albe Laurenz
> I'm moving this discussion to -general.
>
Okay, lets continue here.
>
> Dmitriy Igrishin wrote:
> >>> While developing a C++ client library for Postgres I felt lack of extra
> >>> information in command tags in the CommandComplete (B) message [...]
> >>> for the followin
