[DB-SIG] Result Set Inconsistencies
mal at lemburg.com
Thu Jul 17 12:50:04 EDT 2003
Marcos Sánchez Provencio wrote:
> Kevin Jacobs wrote:
>> On Wed, 16 Jul 2003, Orr, Steve wrote:
>> The API authors were very careful about _not_ specifying what kinds of
>> sequence type. The fact that you want to fill in some extra details
>> that your needs differ from those that the authors intended. This is
>> not to
>> say that the spec is perfect, but this flexibility has been
>> appreciated by
>> driver authors and has placed no undue burden on application writers.
> Maybe all we need is to narrow the spec about this point. We could say
> the resultset is list-compatible and offer suggested improvements (such
> as named columns, iterators, etc.). Plus metadata to know what level of
> improvements we have (a-la-paramstyle).
> ¿Everybody happy about that?
No need to complicate things: It's easy enough to convert any Python
sequence type into any other type you may want.
In reality, you rarely care whether the return value from .fetchall()
or .fetchmany() is a list, tuple, user defined sequence type, etc.
because you're usually processing the data using iteration and/or
Professional Python Software directly from the Source (#1, Jul 17 2003)
>>> Python/Zope Products & Consulting ... http://www.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
2003-07-01: Released mxODBC.Zope.DA for FreeBSD 1.0.6 beta 1
More information about the DB-SIG