[SQL-CVS] r1776 - SQLObject/branches/0.7-bugfix/docs

[<sub...@co...>]

Author: phd
Date: 2006-05-18 10:54:44 -0600 (Thu, 18 May 2006)
New Revision: 1776

Modified:
   SQLObject/branches/0.7-bugfix/docs/FAQ.txt
Log:
Copied the question "Why there is no __len__?" and the answer from the trunk.


Modified: SQLObject/branches/0.7-bugfix/docs/FAQ.txt
===================================================================
--- SQLObject/branches/0.7-bugfix/docs/FAQ.txt	2006-05-18 16:53:07 UTC (rev 1775)
+++ SQLObject/branches/0.7-bugfix/docs/FAQ.txt	2006-05-18 16:54:44 UTC (rev 1776)
@@ -4,6 +4,25 @@
 
 .. contents::
 
+Why there is no __len__?
+------------------------
+
+There are reasons why there is no __len__ method, though many people think
+having those make them feel more integrated into Python.
+
+One is that len(foo) is expected to be fast, but issuing a COUNT query can
+be slow.  Worse, often this causes the database to do essentially redundant
+work when the actual query is performed (generally taking the len of a
+sequence is followed by accessing items from that sequence).
+
+Another is that list(foo) implicitly tries to do a len first, as an
+optimization (because len is expected to be cheap -- see previous point).
+Worse, it swallows *all* exceptions that occur during that call to __len__,
+so if it fails (e.g. there's a typo somewhere in the query), the original
+cause is silently discarded, and instead you're left with mysterious errors
+like "current transaction is aborted, commands ignored until end of
+transaction block" for no apparent reason.
+
 How can I do a LEFT JOIN?
 -------------------------