From 3e96fb1d9ae62179371931e7aca8cd517adf8a95 Mon Sep 17 00:00:00 2001 From: Par Winzell Date: Tue, 21 Aug 2007 19:06:55 +0000 Subject: [PATCH] Turn off field overrides when evaluating a join condition. This is all getting hairy -- sometimes you want FooRecord.BAR_C to point to the field 'under' the override, sometimes you want the actual overide expression. Hrm. Michael feels we probably shouldn't do any field expansion magic past the FROM clause. I am hoping we can preserve some of it in some intuitive way. This is a stop gap measure. --- src/java/com/samskivert/jdbc/depot/BuildVisitor.java | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/java/com/samskivert/jdbc/depot/BuildVisitor.java b/src/java/com/samskivert/jdbc/depot/BuildVisitor.java index 5bab31b..d3ea095 100644 --- a/src/java/com/samskivert/jdbc/depot/BuildVisitor.java +++ b/src/java/com/samskivert/jdbc/depot/BuildVisitor.java @@ -280,7 +280,9 @@ public abstract class BuildVisitor implements ExpressionVisitor _builder.append(" as "); appendTableAbbreviation(join.getJoinClass()); _builder.append(" on "); + _ignoreOverrides = true; join.getJoinCondition().accept(this); + _ignoreOverrides = false; } public void visit (Limit limit)