Message 218657 - Python tracker

➜

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	glangford
Recipients	Russell.Sim, eric.araujo, ghaering, glangford, ncoghlan, petri.lehtinen, rhettinger
Date	2014-05-16.12:32:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1400243562.6.0.886330474783.issue13299@psf.upfronthosting.co.za>
In-reply-to

Content
In abstract, I like the namedtuple interface for sqlite3 as well. One caution is that the approach suggested at http://peter-hoffmann.com/2010/python-sqlite-namedtuple-factory.html can have a dramatic impact on performance. For one DB-intensive application, I experienced 20+ seconds run time with the row factory (under 3.4), versus sub second without (identified with cProfile). Many thousands of calls to namedtuple_factory were not good. :)

In abstract, I like the namedtuple interface for sqlite3 as well. One caution is that the approach suggested at

http://peter-hoffmann.com/2010/python-sqlite-namedtuple-factory.html 

can have a dramatic impact on performance. For one DB-intensive application, I experienced 20+ seconds run time with the row factory (under 3.4), versus sub second without (identified with cProfile). Many thousands of calls to namedtuple_factory were not good. :)

History
Date	User	Action	Args
2014-05-16 12:32:42	glangford	set	recipients: + glangford, rhettinger, ghaering, ncoghlan, eric.araujo, petri.lehtinen, Russell.Sim
2014-05-16 12:32:42	glangford	set	messageid: <1400243562.6.0.886330474783.issue13299@psf.upfronthosting.co.za>
2014-05-16 12:32:42	glangford	link	issue13299 messages
2014-05-16 12:32:42	glangford	create