On Feb 18, 2007, at 3:35 PM, Paul Johnston wrote:
> 4) I'm considering submitting a patch to make _CompoundClause.compare > tell you if the clause has the same semantics as the comparison (at > the > moment it tells if they're exactly the same). This would make "t1.a = > t2.a AND t1.b = t2.b" equal "t1.b = t2.b AND t1.a = t2.a" which to me > makes sense. Is this likely to be accepted? > im curious how this function would work for more complex situations, i.e. with more operators, more levels of nesting, etc. without re- implementing a full SQL expression parser. what if the CompoundClause is based around "XOR" and not "AND" ? is it going to implement the full set of commutivaty/associativity/etc ? still curious as well why this is needed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
