Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Henno Vermeulen <henno@huizemolenaar.nl>
To: "'users@openjpa.apache.org'" <users@openjpa.apache.org>
Date: Wed, 15 May 2013 16:06:10 +0200
Subject: found a bug in criteria API left join and a solution
Thread-Topic: found a bug in criteria API left join and a solution
Thread-Index: Ac5RdAIdYfuaCyYESqeT2mmgOG8Q+Q==
Message-ID: <1C448C478A6B4743AF19DBC3C3DCE13203EAE1DA584F@HMS.hm.local>
Accept-Language: nl-NL
Content-Language: nl-NL
acceptlanguage: nl-NL
Content-Type: multipart/alternative;
	boundary="_000_1C448C478A6B4743AF19DBC3C3DCE13203EAE1DA584FHMShmlocal_"
MIME-Version: 1.0

--_000_1C448C478A6B4743AF19DBC3C3DCE13203EAE1DA584FHMShmlocal_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

There is a bug in the Criteria API where a LEFT JOIN that follows another j=
oin (tested for INNER JOIN) gets actual SQL that uses an INNER JOIN.
This was already reported by someone else as OPENJPA-2318 and OPENJPA-2317

I investigated the issue myself and created a small OpenJPA unit test. I al=
so think that I found the exact cause of the problem and the solution to it=
.
It's a simple matter of replacing two literal values of "false" that should=
 probably have been "allowNull" which is true in case of a left join.

Can someone confirm that this means the bug will be fixed in an upcoming re=
lease? I believe it's a simple matter of perform this change and verifying =
that no existing tests are broken.

See my comments in https://issues.apache.org/jira/browse/OPENJPA-2318

Thank you,
Henno

--_000_1C448C478A6B4743AF19DBC3C3DCE13203EAE1DA584FHMShmlocal_--