You may be right. I vaguely recall now that this only works for
to-one relations. For to-many relations, I can't remember how I
handled this.
On 2/28/07, Marcin Skladaniec <marci..sh.com.au> wrote:
> Hi
> Mike, the ExpressionFactory.noMatchExp(AppleTree.APPLE_PROPERTY,
> null) does not work. I tried. I recollect I used Expression which
> aimed other way around (from many to one, example :
> ExpressionFactory.noMatchExp(Apple.APPLE_TREE_PROPERTY, null) ).
> Marcin
>
>
> On 28/02/2007, at 11:11 AM, Mike Kienenberger wrote:
>
> > ExpressionFactory.noMatchExp(AppleTree.APPLE_PROPERTY, null)
> >
> > Be aware that you cannot safely combine this expression with other
> > expressions due to outer join issues, unless you're using the outer
> > join patch. I think there was another null-related fix mixed into
> > that patch.
> >
> > On 2/27/07, Marcin Skladaniec <marci..sh.com.au> wrote:
> >> Hi
> >>
> >> I have a simple one-to-many relationship : AppleTree - Apple. I'm
> >> doing a query :
> >> new SelectQuery(AppleTree.class, expression)
> >> how should the expression look like to return the trees with apples ?
> >> expression = ExpressionFactory.noMatchExp(AppleTree.APPLES, null)
> >> does not seem to work, neither does
> >> expression = ExpressionFactory.noMatchExp("applesArray", null)
> >>
> >> Regards
> >> Marcin
> >>
>
> Marcin
>
>
>
>
This archive was generated by hypermail 2.0.0 : Wed Feb 28 2007 - 09:49:33 EST