Re: [Sqlalchemy-tickets] [sqlalchemy] #1635: Patch adding support for multiple result sets in Resul
Brought to you by:
zzzeek
Menu
▾
▴
Re: [Sqlalchemy-tickets] [sqlalchemy] #1635: Patch adding support for multiple result sets in ResultProxy
|
From: sqlalchemy <mi...@zz...> - 2010-01-20 17:51:47
|
#1635: Patch adding support for multiple result sets in ResultProxy
----------------------------+-----------------------------------------------
Reporter: guest | Owner: zzzeek
Type: enhancement | Status: new
Priority: medium | Milestone: 0.6.xx
Component: engine | Severity: major - 1-3 hours
Resolution: | Keywords:
Status_field: in queue |
----------------------------+-----------------------------------------------
Comment (by zzzeek):
Replying to [comment:16 ged]:
> About the last part (RowProxy changes & related), I would like to review
any change before it gets committed, as to not have something which is
incompatible with a decent C implementation, and if possible, which is
consistent with my current C implementation.
I've committed in r6665 the basic idea of detaching the metadata from the
`ResultProxy`, and while I was going to present as a patch, halfway
through it became apparent that this is a much better way to go overall as
we lose the redundancy of `PickledResultProxy` and we also cleanly detach
`RowProxy` objects from the parent. This should make the C
implementation easier since `ResultProxyMetadata` is where the intensive
stuff occurs - you should be able to leave `ResultProxy` alone.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1635#comment:17>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python |