> Part of the problem is that PREPARE has no provision to overwrite an
> existing plan (CREATE OR REPLACE). I run into this all the time because
> I make heavy use of prepared statements to emulate an ISAM file system.
> I have to jump through hoops to keep track of what statements are
> already prepared to keep from bouncing the current transaction.
Bruce - TODO?:
* 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...
Chris