> I don't see this as all that helpful for a client interface that does the
> preparation itself. Possibly it could be used for libpq, but you
> mentioned DBI which should already know what it has or has not prepared.
> The idea of adding a network round trip to detect a prepared statement
> seems like a performance loss, not a gain. If this is just to avoid
> repreparing the same statement then perhaps something like PREPARE OR
> REPLACE would be more useful.
Yes, PREPARE OR REPLACE was the other thing I thought would be useful.
However, in my example that still means preparing everytime, wasting the
benefits.
You could have:
PREPARE IF NOT EXISTS
:P
Chris
