-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Merlin Moncure wrote: > I have to jump through hoops to keep track of what statements are > already prepared to keep from bouncing the current transaction. Christopher Kings-Lynne wrote: > * PREPARE OR REPLACE... > > This would be an incredibly useful command since there's no > way of _checking_ in advance that a name is already used as a > prepared statement... A check would be nice (and I've asked about it before) but it's really not a lot of jumping through hoops since each connection has it's own "namespace" of prepared statements. Since they last until an explicit deallocate, the simple use of unique names makes it fairly easy on the application side. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200406232330 -----BEGIN PGP SIGNATURE----- iD8DBQFA2krxvJuQZxSWSsgRAhLSAJ9othitQerDlB9+J65rVl3EbRT9+QCeJfzH vFdWCDLvxU/zkFMLEDjpydU= =OzCx -----END PGP SIGNATURE-----
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
