[
https://issues.apache.org/jira/browse/OPENJPA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798299#comment-13798299
]
ASF subversion and git services commented on OPENJPA-2343:
----------------------------------------------------------
Commit 1533218 from [~jpaheath] in branch 'openjpa/branches/2.1.x'
[ https://svn.apache.org/r1533218 ]
OPENJPA-2343: Version field returns null when explicity projected from a JOIN
in SELECT clause - based fix off of patch provided by Howard Kelsey.
> Version field returns null when explicity projected from a JOIN in SELECT
> clause
> --------------------------------------------------------------------------------
>
> Key: OPENJPA-2343
> URL: https://issues.apache.org/jira/browse/OPENJPA-2343
> Project: OpenJPA
> Issue Type: Bug
> Components: query
> Affects Versions: 2.3.0, 2.2.1
> Reporter: howard kelsey
> Assignee: Rick Curtis
> Fix For: 2.3.0
>
> Attachments: OPENJPA-2343-2.2.1.x.patch
>
>
> With these entities:
> @Entity
> public class Foo {
> private int id;
> private int version;
> @Id
> public int getId() {
> return id;
> }
> public void setId(int id) {
> this.id = id;
> }
> public void setVersion(int version) {
> this.version = version;
> }
> @Version
> public int getVersion() {
> return this.version;
> }
> }
> @Entity
> public class Bar{
> private int id;
> private Foo foo;
> @Id
> public int getId() {
> return id;
> }
> public void setId(int id) {
> this.id = id;
> }
> public void setFoo(Foo foo) {
> this.foo = foo;
> }
> @ManyToOne
> public Foo getFoo() {
> return foo;
> }
> }
> Insert a record for each associating foo with bar.
> Foo foo = new Foo();
> em.getTransaction().begin();
> em.persist(foo);
> Bar bar = new Bar();
> bar.setFoo(foo);
> em.persist(bar);
> em.getTransaction().commit();
> em.close();
> queries
> select bar.id as id, foo as foo from Bar bar join bar.foo foo
> The version field is available via foo.getVersion()
> select bar.id as id, foo.version as version from Bar bar join bar.foo foo
> version is always null.
> By enabling the jdbc debug I can see that the actual SQL being run is correct
> but the value is just not hydrated.
--
This message was sent by Atlassian JIRA
(v6.1#6144)