Re: Prepared statements considered harmful

On Aug 31, 2006, at 8:52 , Csaba Nagy wrote:

>
> This of course would need a lot more preparation time than just
> prepare
> one plan, but that's why you want to do it upfront and then cache the
> results. A central plan repository mentioned in other posts would fit
> nicely here... and you could use prepared plans for non-parameterized
> queries too by simply considering the constants as parameters, to
> increase the chances for a prepared plan reuse - this of course for
> complex enough queries.

If prepared statements become more expensive to create, then it would
make more sense for them to persist across sessions. All of an
application's prepared statements could be cached.

-M