Rick Debay wrote:

>
> When an SQL statement is executed, the plan is not saved, although the
> statement may be cached on the client side (e.g. Jaybird's statement
> pooling).

The optimized version of a prepared statement is saved for reuse by the
connection that prepared it until that connection specifically releases
it. Vulcan has provisions for saving compiled and optimized requests
independent of the connection, though it does not do so yet. Note that
the cost of optimization is relatively low in Firebird and becomes a
factor only when an unprepared statement is executed in a long loop -
e.g. massive inserts.

Regards,


Ann