> >
> > aHome.findBySomeProprety(7) ->
> >
> > select a.id, a.property
> > from a
> > where a.property > 7
> >
> > and then:
> >
> > select b.id, b.someotherfield, b.aref
> > from a, b
> > where a.id=b.aref
> > and a.property > 7
> >
> > (This would be the equivalent of a join. Alternatively, I
> > wouldn't much mind if the container requested a single SQL
> with the join)
>
> Well, it seems to me this example is way too specific to be
> handled through
> CMP. You would need to go with BMP for that. Note that you
> could actually
> use both, and leverage underlying CMR relationships to
> perform some of those
> queries for you. But for the final result, you would
> definitely need to
> write some code by hand.
I don't think this example is specific. For example, a users/groups
relationship is very similar - you want to display a table with the user
name and group name. Using finders-call-ejbload (or an equivalent), you get
the users in one shot. But then N selects are required for the groups (lets
assume a great number so caching is ineffective). The example also applies
to order line item/product name, or anywhere else a join would be used.
Possibly every nontrival table display requires a join.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
