Recent versions of adodbapi do in fact return a result set ("Rows") object.
Since ADO requires a separate operating system call to fetch each row, and
since we can assume that the ADO result set is setting around in memory
somewhere, I did not want the space overhead of making an additional copy
of
Vernon D. Cole wrote:
>
> Since both "Rows" objects, and "Row" objects, obey the sequence API, this
> design satisfies the PEP requirements that we return a sequence of sequences.
> It will also do much more. If the PEP had been written to require a list of
> tuples, none of these other o
On 03.02.2015 21:30, Michael Bayer wrote:
>> [By the way, both Rows and Row objects are made immutable, so that an unwary
>> programmer does not receive an unwelcome surprise by attempting to alter
>> data without using an SQL statement.]
>
> I would actually favor the result list to be an immut
M.-A. Lemburg wrote:
>
> The DB-API does provide guidance, but doesn't mandate specific
> implementations.
>
> What we can do is add a note to recommend that implementations
> return results sets as list of tuples, unless special result set and
> row objects are more appropriate or needed.
>
