You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "David Minor (JIRA)" <ji...@apache.org> on 2009/07/20 17:57:14 UTC
[jira] Created: (OPENJPA-1184) Inverse relations not set for MapKey
field when using parallel eager select
Inverse relations not set for MapKey field when using parallel eager select
---------------------------------------------------------------------------
Key: OPENJPA-1184
URL: https://issues.apache.org/jira/browse/OPENJPA-1184
Project: OpenJPA
Issue Type: Bug
Components: jdbc
Affects Versions: 1.2.1
Environment: All environments using JDBC store.
Reporter: David Minor
When selecting multiple entities A which contain a @MapKey field for entity B, the inverse relation from B to A will only be set for the first entity A, when using parallel eager select. This is because all entity B objects are created when loading the 1st entity A object, with the inverse relation to be set later in setInverseRelation(), but setInverseRelation() is looking for Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OPENJPA-1184) Inverse relations not set for
MapKey field when using parallel eager select
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods reassigned OPENJPA-1184:
-------------------------------------
Assignee: Donald Woods
> Inverse relations not set for MapKey field when using parallel eager select
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-1184
> URL: https://issues.apache.org/jira/browse/OPENJPA-1184
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.1
> Environment: All environments using JDBC store.
> Reporter: David Minor
> Assignee: Donald Woods
> Fix For: 1.2.2, 1.3.0, 2.0.0
>
> Attachments: openjpa.patch
>
>
> When selecting multiple entities A which contain a @MapKey field for entity B, the inverse relation from B to A will only be set for the first entity A, when using parallel eager select. This is because all entity B objects are created when loading the 1st entity A object, with the inverse relation to be set later in setInverseRelation(), but setInverseRelation() is looking for Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1184) Inverse relations not set for MapKey
field when using parallel eager select
Posted by "David Minor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Minor updated OPENJPA-1184:
---------------------------------
Attachment: mapkey-inverse-relation-test.patch
Test case against 1.2.1 which demonstrates the issue.
> Inverse relations not set for MapKey field when using parallel eager select
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-1184
> URL: https://issues.apache.org/jira/browse/OPENJPA-1184
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.1
> Environment: All environments using JDBC store.
> Reporter: David Minor
> Assignee: Donald Woods
> Fix For: 1.2.2, 1.3.0, 2.0.0
>
> Attachments: mapkey-inverse-relation-test.patch, openjpa.patch
>
>
> When selecting multiple entities A which contain a @MapKey field for entity B, the inverse relation from B to A will only be set for the first entity A, when using parallel eager select. This is because all entity B objects are created when loading the 1st entity A object, with the inverse relation to be set later in setInverseRelation(), but setInverseRelation() is looking for Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1184) Inverse relations not set for
MapKey field when using parallel eager select
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736748#action_12736748 ]
Donald Woods commented on OPENJPA-1184:
---------------------------------------
David, do you have a junit testcase that demonstrates this failure?
> Inverse relations not set for MapKey field when using parallel eager select
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-1184
> URL: https://issues.apache.org/jira/browse/OPENJPA-1184
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.1
> Environment: All environments using JDBC store.
> Reporter: David Minor
> Fix For: 1.2.2, 1.3.0, 2.0.0
>
> Attachments: openjpa.patch
>
>
> When selecting multiple entities A which contain a @MapKey field for entity B, the inverse relation from B to A will only be set for the first entity A, when using parallel eager select. This is because all entity B objects are created when loading the 1st entity A object, with the inverse relation to be set later in setInverseRelation(), but setInverseRelation() is looking for Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1184) Inverse relations not set for
MapKey field when using parallel eager select
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1184.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0.0)
(was: 1.2.2)
2.0.0-M3
Patch and tests committed to trunk and 13x. Thanks to David Minor for the patches.
> Inverse relations not set for MapKey field when using parallel eager select
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-1184
> URL: https://issues.apache.org/jira/browse/OPENJPA-1184
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.1
> Environment: All environments using JDBC store.
> Reporter: David Minor
> Assignee: Donald Woods
> Fix For: 1.3.0, 2.0.0-M3
>
> Attachments: mapkey-inverse-relation-test.patch, openjpa.patch
>
>
> When selecting multiple entities A which contain a @MapKey field for entity B, the inverse relation from B to A will only be set for the first entity A, when using parallel eager select. This is because all entity B objects are created when loading the 1st entity A object, with the inverse relation to be set later in setInverseRelation(), but setInverseRelation() is looking for Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1184) Inverse relations not set for
MapKey field when using parallel eager select
Posted by "David Minor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737665#action_12737665 ]
David Minor commented on OPENJPA-1184:
--------------------------------------
I don't -- I've never written a test case for openjpa, so I'll see if I can find some time this next week to figure it out.
> Inverse relations not set for MapKey field when using parallel eager select
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-1184
> URL: https://issues.apache.org/jira/browse/OPENJPA-1184
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.1
> Environment: All environments using JDBC store.
> Reporter: David Minor
> Fix For: 1.2.2, 1.3.0, 2.0.0
>
> Attachments: openjpa.patch
>
>
> When selecting multiple entities A which contain a @MapKey field for entity B, the inverse relation from B to A will only be set for the first entity A, when using parallel eager select. This is because all entity B objects are created when loading the 1st entity A object, with the inverse relation to be set later in setInverseRelation(), but setInverseRelation() is looking for Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1184) Inverse relations not set for MapKey
field when using parallel eager select
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1184:
----------------------------------
Fix Version/s: 2.0.0
1.3.0
1.2.2
> Inverse relations not set for MapKey field when using parallel eager select
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-1184
> URL: https://issues.apache.org/jira/browse/OPENJPA-1184
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.1
> Environment: All environments using JDBC store.
> Reporter: David Minor
> Fix For: 1.2.2, 1.3.0, 2.0.0
>
> Attachments: openjpa.patch
>
>
> When selecting multiple entities A which contain a @MapKey field for entity B, the inverse relation from B to A will only be set for the first entity A, when using parallel eager select. This is because all entity B objects are created when loading the 1st entity A object, with the inverse relation to be set later in setInverseRelation(), but setInverseRelation() is looking for Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1184) Inverse relations not set for MapKey
field when using parallel eager select
Posted by "David Minor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Minor updated OPENJPA-1184:
---------------------------------
Attachment: openjpa.patch
Patch against 1.2.1.
> Inverse relations not set for MapKey field when using parallel eager select
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-1184
> URL: https://issues.apache.org/jira/browse/OPENJPA-1184
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.1
> Environment: All environments using JDBC store.
> Reporter: David Minor
> Attachments: openjpa.patch
>
>
> When selecting multiple entities A which contain a @MapKey field for entity B, the inverse relation from B to A will only be set for the first entity A, when using parallel eager select. This is because all entity B objects are created when loading the 1st entity A object, with the inverse relation to be set later in setInverseRelation(), but setInverseRelation() is looking for Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.