[DB-SIG] RE: mxODBC performance question
Tue, 30 May 2000 10:23:58 +0200
David Bolen wrote:
> M.-A. Lemburg [email@example.com] writes:
> > SQLExecDirect() is currently not used, but would be a good candidate
> > for the case where you don't have any parameters and keeping the
> > prepared command around is not important. I'll add that to my TODO
> > list.
> Thanks - FYI, I experimented with adding a method for that command to mxODBC
> and the Python script's runtime immediately dropped down to virtually the
> same as that of the original Perl script. So at least in WAN cases,
> permitting access to the SQLExecDirect() if parameters aren't used can be a
> big time saver.
Sounds like there is a real need for SQLExecDirect()...
> > You should definitely consider using bound parameters, since
> > these fit your problem quite nicely (fixed SQL statement +
> > variable query values).
> Precisely, and I expected to do that as the next step - the problem was that
> the easiest method of verification of the new script was a comparison of the
> commands being executed, so I sort of need to stick with the full strings
> initially until we have some parallel runtime under our belts.
I'd be interested in whether you get the same (or better)
performance with bound variables.
Python Pages: http://www.lemburg.com/python/