- attached clauselist_columnproperty.patch
ClauseList as a column_property
Issue #798
resolved
As described in the clauselist as a column_property group mail, the current version doesn't allow ClauseLists as a column property.
Comments (6)
-
Account Deleted -
repo owner - changed milestone to 0.4.xx
the orig_set() thing is probably not needed here.
but im thinking that it may be more appropriate here to just have and_(), or_(), etc. return a
_CalculatedClause
instead ofClauseList
. since i think that object is already designed to handle the "list of items which can act like a column" use-case (i.e. it has a "type_" parameter, etc.)of top importance here is that we have some small test cases. such as:
x = and_(a, b, c) assert x.type is types.Boolean assert str(x) == 'a AND b AND c' assert str(select([x.label('foo')](x.label('foo')))) == 'SELECT (a AND b AND c) AS foo'
etc.
-
repo owner - changed milestone to 0.4.3
-
repo owner - changed milestone to 0.5.xx
-
repo owner - changed status to resolved
since I suddenly had the need for this myself, its fixed in e158234478f3bb17ec90e5dc5a125d0207d2d5fe.
-
repo owner - removed milestone
Removing milestone: 0.5.xx (automated comment)
- Log in to comment
Not sure if orig_sit property is actually needed, and of its doc string is correct.