Am 04.01.2019 um 19:10 schrieb Justin Pryzby:
> But instead should pygres use NAMED prepared statements for its
> internal queries, to avoid its unnamed queries conflicting with
> users' unnamed prepared> statements ?
I fear that would open a whole new can of worms for us. We would need
our own namespace for the names, and keep track of the lifetime of these
statements, particularly when they need to be created (remember they
live only one session long). Since we don't have control over what the
user is in the meantime, we would probably need to test every time if
the statement is still there. A lot of overhead...
> Currently it calls PQexecParams which (I think you agree) is creating
> unnamed prepared statements behind the scenes.
Yes, I think this is the case. And I got the impression that even simple
PQexecs annihilate existing unnamed statements. Did you also see that?
-- Christoph
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo/pygresql
