I don't know about that ... left outer join has a meaning in a
context of a relationship. Right outer join does not... JPA spec
doesn't have a right or full outer join in it. So if there is a real
use case, lets discuss it.
Andrus
On Aug 17, 2006, at 5:44 PM, Mike Kienenberger wrote:
> Andrus,
>
> If we're going to go this far, should we plan ahead and figure out
> what we're going to use as syntax for "Right Outer Join" and "Full
> Outer Join"?
>
> Implementing these should be trivial once Left Outer Join is done.
>
> If Left is "+", is right "-"? :-)
>
> And is full "+/-"? :-)
>
> Yes, I recently got a DVD burner :-)
>
> On 8/17/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
>>
>> On Aug 17, 2006, at 5:12 PM, Andrus Adamchik wrote:
>>
>> > Good point. Looks like we will need to change
>> > 'resolvePathComponents' iterator meaning to return a sequence of
>> > wrapper objects that have both relationship/attribute and the join
>> > semantics:
>> >
>> > class PathComponent {
>> > protected Object metadataObject;
>> > protected (?) joinSematics;
>> > }
>>
>> Or rather instead of "change semantics" create another iterator
>> method with a different name - don't want to break the existing apps.
>>
>> Andrus
>>
>
This archive was generated by hypermail 2.0.0 : Thu Aug 17 2006 - 17:49:24 EDT