Hi,
4) I'm considering submitting a patch to make _CompoundClause.compare
tell you if the clause has the same semantics as the comparison (at
im curious how this function would work for more complex situations,
i.e. with more operators, more levels of nesting, etc. without re-
On Feb 19, 2007, at 3:39 PM, Paul Johnston wrote:
Ok, the issue was noticed due to a unit test failure
(engine.reflection.ReflectionTest.testcompositefk) where the test
checks
if the condition created by the join matches the condition it
knows. The
test was incorrectly failing because
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
