You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Heath Thomann (JIRA)" <ji...@apache.org> on 2010/10/26 01:24:20 UTC
[jira] Created: (OPENJPA-1854) A 'find' or 'query' may return
multiple instances of Entities which contain Embeddables, where the
Embeddables use String identities, if the id value has trailing spaces.
A 'find' or 'query' may return multiple instances of Entities which contain Embeddables, where the Embeddables use String identities, if the id value has trailing spaces.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: OPENJPA-1854
URL: https://issues.apache.org/jira/browse/OPENJPA-1854
Project: OpenJPA
Issue Type: Bug
Components: kernel
Affects Versions: 2.0.0, 1.2.2, 1.3.0
Reporter: Heath Thomann
Assignee: Heath Thomann
This issue is very similar to that of OPENJPA-1501, with one twist.......I've found that when you have an Embeddable, which has Strings as the keys/ids, openJPA code puts the Embeddable into an ObjectID by design, rather than a StringID....recall, the fix to OJ1501 was to strip white space from the end of a user's String key when that String was placed into a StringID. So, the strings in an Embeddable would also need to be stripped, just as was done in OJ-1501, but unfortunately it would seem to be harder to do so for Embeddables since openJPA code doesn't necessarily know what types are contained in the Embed.
I've created a JUnit test case which has three test methods. The test is attached here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (OPENJPA-1854) A 'find' or 'query' may return
multiple instances of Entities which contain Embeddables, where the
Embeddables use String identities, if the id value has trailing spaces.
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick updated OPENJPA-1854:
----------------------------------
Fix Version/s: (was: 2.0.1)
2.0.2
> A 'find' or 'query' may return multiple instances of Entities which contain Embeddables, where the Embeddables use String identities, if the id value has trailing spaces.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1854
> URL: https://issues.apache.org/jira/browse/OPENJPA-1854
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.2, 1.3.0, 2.0.0
> Reporter: Heath Thomann
> Assignee: Heath Thomann
> Fix For: 1.2.3, 2.0.2, 2.1.1
>
> Attachments: OPENJPA-1854-1.2.x.test
>
>
> This issue is very similar to that of OPENJPA-1501, with one twist.......I've found that when you have an Embeddable, which has Strings as the keys/ids, openJPA code puts the Embeddable into an ObjectID by design, rather than a StringID....recall, the fix to OJ1501 was to strip white space from the end of a user's String key when that String was placed into a StringID. So, the strings in an Embeddable would also need to be stripped, just as was done in OJ-1501, but unfortunately it would seem to be harder to do so for Embeddables since openJPA code doesn't necessarily know what types are contained in the Embed.
> I've created a JUnit test case which has three test methods. The test is attached here.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENJPA-1854) A 'find' or 'query' may return
multiple instances of Entities which contain Embeddables, where the
Embeddables use String identities, if the id value has trailing spaces.
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick updated OPENJPA-1854:
----------------------------------
Fix Version/s: 2.0.1
2.1.1
1.2.3
Targeting for 1.2, 2.0 and 2.1
> A 'find' or 'query' may return multiple instances of Entities which contain Embeddables, where the Embeddables use String identities, if the id value has trailing spaces.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1854
> URL: https://issues.apache.org/jira/browse/OPENJPA-1854
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.2, 1.3.0, 2.0.0
> Reporter: Heath Thomann
> Assignee: Heath Thomann
> Fix For: 1.2.3, 2.0.1, 2.1.1
>
> Attachments: OPENJPA-1854-1.2.x.test
>
>
> This issue is very similar to that of OPENJPA-1501, with one twist.......I've found that when you have an Embeddable, which has Strings as the keys/ids, openJPA code puts the Embeddable into an ObjectID by design, rather than a StringID....recall, the fix to OJ1501 was to strip white space from the end of a user's String key when that String was placed into a StringID. So, the strings in an Embeddable would also need to be stripped, just as was done in OJ-1501, but unfortunately it would seem to be harder to do so for Embeddables since openJPA code doesn't necessarily know what types are contained in the Embed.
> I've created a JUnit test case which has three test methods. The test is attached here.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OPENJPA-1854) A 'find' or 'query' may return
multiple instances of Entities which contain Embeddables, where the
Embeddables use String identities, if the id value has trailing spaces.
Posted by "Heath Thomann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Heath Thomann updated OPENJPA-1854:
-----------------------------------
Attachment: OPENJPA-1854-1.2.x.test
> A 'find' or 'query' may return multiple instances of Entities which contain Embeddables, where the Embeddables use String identities, if the id value has trailing spaces.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1854
> URL: https://issues.apache.org/jira/browse/OPENJPA-1854
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.2, 1.3.0, 2.0.0
> Reporter: Heath Thomann
> Assignee: Heath Thomann
> Attachments: OPENJPA-1854-1.2.x.test
>
>
> This issue is very similar to that of OPENJPA-1501, with one twist.......I've found that when you have an Embeddable, which has Strings as the keys/ids, openJPA code puts the Embeddable into an ObjectID by design, rather than a StringID....recall, the fix to OJ1501 was to strip white space from the end of a user's String key when that String was placed into a StringID. So, the strings in an Embeddable would also need to be stripped, just as was done in OJ-1501, but unfortunately it would seem to be harder to do so for Embeddables since openJPA code doesn't necessarily know what types are contained in the Embed.
> I've created a JUnit test case which has three test methods. The test is attached here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (OPENJPA-1854) A 'find' or 'query' may return
multiple instances of Entities which contain Embeddables, where the
Embeddables use String identities, if the id value has trailing spaces.
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick updated OPENJPA-1854:
----------------------------------
Fix Version/s: (was: 2.1.1)
2.1.2
> A 'find' or 'query' may return multiple instances of Entities which contain Embeddables, where the Embeddables use String identities, if the id value has trailing spaces.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1854
> URL: https://issues.apache.org/jira/browse/OPENJPA-1854
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.2, 1.3.0, 2.0.0
> Reporter: Heath Thomann
> Assignee: Heath Thomann
> Fix For: 1.2.3, 2.0.2, 2.1.2
>
> Attachments: OPENJPA-1854-1.2.x.test
>
>
> This issue is very similar to that of OPENJPA-1501, with one twist.......I've found that when you have an Embeddable, which has Strings as the keys/ids, openJPA code puts the Embeddable into an ObjectID by design, rather than a StringID....recall, the fix to OJ1501 was to strip white space from the end of a user's String key when that String was placed into a StringID. So, the strings in an Embeddable would also need to be stripped, just as was done in OJ-1501, but unfortunately it would seem to be harder to do so for Embeddables since openJPA code doesn't necessarily know what types are contained in the Embed.
> I've created a JUnit test case which has three test methods. The test is attached here.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira