Well, quoting my first post:
> And the following query returns exactly the same error
> above (note the only change to the previous query was the IN
> operator:
> select u
> from User u
> where exists (
> select u2
> from User u2 inner join u2.roles r
> where u2
IDE Environment: Eclipse-3.4
DB Environment: Apache-Derby-10.5.1.1
JDK Environment: Sun JDK-1.6.0_07
Jar Environment: from
http://openjpa.apache.org/builds/latest/downloads/apache-openjpa-2.0.0-SNAPSHOT-binary.zip
Eclipse PlugIn Environment:Apache-Derby, JUnit4
I want to test the @ManyToMany(the
Hi,
Looks like a potential issue.
Please
1. create a JIRA issue
2. two patches : one for a test case and one with your suggested fix
3. submit the patch with the JIRA issue (do not forget to grant access --
last radio button on "Attach Patch" page in JIRA)
I will review and apply t
Hi,
Interesting that this works on Hibernate. The first potential issue I found
in the test is that it uses a hardcoded id and your entities are annotated
with @GeneratedValue. Depending on how the value is generated, the values
could be different between test runs and providers. Storing away t
Hi,
Thanks for your response.
I hardcoded is just for test @ManyToMany and see the effect. @GeneratedValue
is not the point of this issue.
I also do not think this is the bug of OpenJPA, and I had been modified the
code like your advice before, and It didn't passed test either. because the
test co
