Re: [Sqlalchemy-tickets] [sqlalchemy] #2150: backport distinct(*expr) to 0.6
Brought to you by:
zzzeek
From: sqlalchemy <mi...@zz...> - 2011-04-27 14:10:09
|
#2150: backport distinct(*expr) to 0.6 -------------------------+-------------------------------------------------- Reporter: guest | Owner: zzzeek Type: enhancement | Status: new Priority: medium | Milestone: 0.6.xx Component: sql | Severity: minor - half an hour Keywords: distinct | Status_field: needs review -------------------------+-------------------------------------------------- Changes (by zzzeek): * keywords: => distinct * component: postgres => sql * severity: no triage selected yet => minor - half an hour * status_field: awaiting triage => needs review Comment: this is the actual patch: ra7f581395db1 its in 0.7 because it deprecates several features, and greatly reorganizes how "distinct" is handled at all levels. the patch above includes: * documentation * deprecation for MySQL's old style * deprecation for passing a basestring to select(distinct='xyz') * fixes to the logic used in compiler.py * fixes to PG's logic * tests for the feature, PGs behavior, MySQLs behavior im not yet convinced 0.6 really needs a new feature backport of this size - 0.7.0 is due very soon. -- Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2150#comment:1> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |