[
https://issues.apache.org/jira/browse/OPENJPA-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Minor updated OPENJPA-1227:
---------------------------------
Attachment: openjpa_superclass_join.patch
The attached patch forces a join to the superclass table in the specific
circumstances that I'm seeing the bug. However,
1. The join is added to the base mapping select, but I am guessing it would be
best to put it in the eager select only.
2. While it only gets applied in the specific case I'm seeing, I don't
understand the code well enough to know that it won't get applied in other
cases which my application doesn't cover.
Hopefully someone who understands this code better can use this patch to figure
out what's triggering this particular bug, and come up with a more robust
solution.
> SQL generation error when using data cache
> ------------------------------------------
>
> Key: OPENJPA-1227
> URL: https://issues.apache.org/jira/browse/OPENJPA-1227
> Project: OpenJPA
> Issue Type: Bug
> Components: datacache, jdbc, sql
> Affects Versions: 1.2.1
> Reporter: David Minor
> Attachments: openjpa_superclass_join.patch
>
>
> When the DataCacheStoreManager loads an object whose (table join strategy)
> superclass contains an eager to-many field, and this is the only field
> selected in the superclass, and when one or more fields are selected in the
> subclass, openjpa fails to create a join between the subclass and superclass.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
