Blake Mitchell wrote: > Is there appreciable overhead in just preparing each statement as it's > built and only using it once?
I guess we pretty much have to assume the penalty might be a potential DOS. > This would still allow binding of the > parameters, to avoid the quoting quagmire. Obviously there are > performance gains in re-using prepared statements. But it seems to me > that a good first step is to just change the method by which each query > is executed, then worry about how to cache statement handles. I'm all for it. Sounds like it's worth the potential performance penalty. The search/sort code will be tricky, but if we leave that while tackling the more often used queries I'm sure we'll work out an approach to help us ease the transition of that code and the rewritten fetch code as well. I've never used prepared statements before, so I'm curious where this will lead... -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
