Joris Dobbelsteen <[EMAIL PROTECTED]> writes: > The MAJOR benefit of Microsoft's approach is that it works on existing > application, and, most importantly makes NO assumptions on the > "volatile" server state. A few cases where the Microsoft solution works, > while yours will fail is:
> * Server restart and assorted like failover (you need to redo a > global prepare). Hmm? He's proposing storing the info in a system catalog. That hardly seems "volatile"; it'll certainly survive a server restart. > * Cleanup and instantiation of a prepared statement. Again, it's not clear what you've got in mind. I agree with the point that this isn't completely transparent to applications, but if an app is already using named prepared statements it would surely be a pretty small matter to make it use this feature. The app code would likely get simpler instead of more complex, since you'd stop worrying about whether a given statement had been prepared yet in the current session. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers