A list of open points in the documentation

Hello,

the psycopg documentation is almost finished. It can be previewed on
http://piro.develer.com/psycopg2-doc/

While working at it, a lot of points came up: i recorded them in the
todo list and now it's time for a few answers. Please help me to
clarify these points.

1. the DBAPI says about cursor.execute():
"""
A reference to the operation will be retained by the cursor. If the
same operation object is passed in again, then the cursor can optimize
its behavior.
"""
does psycopg do this?

2. does cursor.arraysize influence cursor.fetchall?

3. DBAPI says that scroll() should raise IndexError. Psycopg raises
ProgrammingError instead. I'd say this is a bug, but maybe it's too
late to be fixed. Shall we keep it this way? Shall I point out the
discrepancy between dbapi and psycopg in the docs or keep it quiet?

4. in order to use the tuple adapter to the IN syntax,
psycopg2.extensions has to be imported. Is this a bug (it has already
bitten me once) to be fixed or a "feature" to document?

5. Does psycopg user ever have to directly use the ISQLQuote object?
in my knowledge it is just a symbol used internally for adpters
dispatch. Has he ever to instantiate it? Are the methods defined on it
any useful?

6. The binary adapter is not imported in the psycopg2.extensions
module while all the other adapters seem there. Shall i add it too?

7. What does the second parameter of register_type do? It seems what i
described here:
http://piro.develer.com/psycopg2-doc/extensions.html#psycopg2.extensions.register_type
Is this confirmed?

8. Is binary_types in psycopg2.extensions and on the connection class
used? Or only string_types is?

9. Is any connection status constant useful, apart from READY and
BEGIN? These states don't seem matching any informative function of
the libpq. http://piro.develer.com/psycopg2-doc/extensions.html#connection-status-constants

Well, I'd say not stuff for newbies...

Thank you very much.


-- Daniele