This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dlenski
Recipients BreamoreBoy, Russell.Sim, dlenski, eric.araujo, ghaering, ncoghlan, petri.lehtinen, rhettinger, serhiy.storchaka
Date 2014-08-04.09:28:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
52 usec/loop doesn't seem like much overhead. This is not 52 usec per row fetched, but just 52 usec per cursor.execute(). An example where >1 row is fetched for each cursor would show this more clearly.

The advantage of namedtuple is that it's a very well-known interface to most Python programmers. Other db-api modules have taken a similar approach; psycopg2 has a dict-like cursor similar to Row, but has added NameTupleCursor in recent versions. (
Date User Action Args
2014-08-04 09:28:05dlenskisetrecipients: + dlenski, rhettinger, ghaering, ncoghlan, eric.araujo, BreamoreBoy, petri.lehtinen, serhiy.storchaka, Russell.Sim
2014-08-04 09:28:05dlenskisetmessageid: <>
2014-08-04 09:28:05dlenskilinkissue13299 messages
2014-08-04 09:28:04dlenskicreate