-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> We could imagine that once we add tracking of plan dependencies,
> detection of a change that invalidates a prepared statement's plan
> would just cause the prepared statement to be marked as "needs
> recompilation". The next attempt to use it would have to re-plan
> from source, and could get an error if there is no longer any valid
> interpretation of the original source string.
I am very uneasy about this. Statements should stay invalidated, else
the prepared statement may no longer even do what was originally
intended when it was first created.
> I'm not sure whether this is a reasonable argument for discarding *all*
> prepared statements made within a failed transaction, though.
That gets my vote, and seems to make the most sense. If the user does
not want it to get rolled back, let them commit it before going on
to the rest of the actions.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200405011816
-----BEGIN PGP SIGNATURE-----
iD8DBQFAlCIivJuQZxSWSsgRAun5AKCUWH3mb59c+iuaDMlf2U+pZG9UXACghalD
5E34MgozbiPkIYMn2tvdGFk=
=oenf
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
