Very weird behavior in MySQLdb "execute"

M

M.-A. Lemburg

Since we're on the topic of shameless plugs, InformixDB has this
feature, too :)


That depends on the notion of "better". It's entirely possible that a
"WHERE CURRENT OF <cursor>" clause finds the row in question faster than
even an indexed access using a primary key could. If you're processing a
single row, I would agree that using an update cursor is overkill, but
if you're processing a large number of rows, using an update cursor
might be beneficial.

Agreed.

This approach is also very useful if you have to do extra analysis
of the rows in question *outside* the database, before selecting them
for update.

--
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source (#1, Feb 07 2008)________________________________________________________________________

:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::


eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,981
Messages
2,570,188
Members
46,733
Latest member
LonaMonzon

Latest Threads

Top