That is an interesting approach. However, I see the problem that the
functions would have to be removed when no longer needed. If that fails
(broken connection etc.), they would be orphaned.
Prepared statements are bound to the connection, so when the connection
is closed they are gone.
On Thu,
On Tue, Jan 28, 2014 at 7:53 AM, Andreas Lubensky luben...@cognitec.com wrote:
That is an interesting approach. However, I see the problem that the
functions would have to be removed when no longer needed. If that fails
(broken connection etc.), they would be orphaned.
Prepared statements are
Hello,
When implementing a database backend with libpq I realized that it seems
to be impossible to declare a cursor on a prepared statement. Is this
correct? What is the reason for this limitation?
--
with best regards,
Andreas Lubensky
--
Sent via pgsql-general mailing list
pgpool-II may do what you want.
On Thu, Jan 23, 2014 at 6:31 AM, Andreas Lubensky luben...@cognitec.comwrote:
Hello,
When implementing a database backend with libpq I realized that it seems
to be impossible to declare a cursor on a prepared statement. Is this
correct? What is the reason for
Sorry, answered wrong posting.
On Thu, Jan 23, 2014 at 6:31 AM, Andreas Lubensky luben...@cognitec.comwrote:
Hello,
When implementing a database backend with libpq I realized that it seems
to be impossible to declare a cursor on a prepared statement. Is this
correct? What is the reason for
On Thu, Jan 23, 2014 at 8:31 AM, Andreas Lubensky luben...@cognitec.com wrote:
Hello,
When implementing a database backend with libpq I realized that it seems
to be impossible to declare a cursor on a prepared statement. Is this
correct? What is the reason for this limitation?
I can't think
