Message 81110 - 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	pitrou
Recipients	erno, exarkun, ghaering, gregburd, gregory.p.smith, jcea, josiahcarlson, pitrou, rhettinger, skip.montanaro
Date	2009-02-03.22:42:20
SpamBayes Score	0.00027965775
Marked as misclassified	No
Message-id	<1233700944.37.0.469276841315.issue3783@psf.upfronthosting.co.za>
In-reply-to

Content
I think issuing 'SELECT MAX(ROWID)' to compute the length of the table is not correct if some rows get deleted in the table. I've found a thread about it here: http://osdir.com/ml/db.sqlite.general/2004-03/msg00329.html In that thread someone suggested caching the length in another table and updating it through a trigger each time the main table is modified.

I think issuing 'SELECT MAX(ROWID)' to compute the length of the table
is not correct if some rows get deleted in the table.
I've found a thread about it here:
http://osdir.com/ml/db.sqlite.general/2004-03/msg00329.html
In that thread someone suggested caching the length in another table and
updating it through a trigger each time the main table is modified.

History
Date	User	Action	Args
2009-02-03 22:42:24	pitrou	set	recipients: + pitrou, skip.montanaro, rhettinger, gregory.p.smith, jcea, ghaering, josiahcarlson, exarkun, erno, gregburd
2009-02-03 22:42:24	pitrou	set	messageid: <1233700944.37.0.469276841315.issue3783@psf.upfronthosting.co.za>
2009-02-03 22:42:21	pitrou	link	issue3783 messages
2009-02-03 22:42:20	pitrou	create