You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Dianne Richards (JIRA)" <ji...@apache.org> on 2010/01/21 19:35:54 UTC
[jira] Created: (OPENJPA-1475) Performance improvement - don't call
syncVersion() when no version is specified
Performance improvement - don't call syncVersion() when no version is specified
-------------------------------------------------------------------------------
Key: OPENJPA-1475
URL: https://issues.apache.org/jira/browse/OPENJPA-1475
Project: OpenJPA
Issue Type: Improvement
Components: kernel
Affects Versions: 2.0.0
Reporter: Dianne Richards
Fix For: 2.0.0
Currently, StateManagerImpl loadFields() always calls syncVersion() when the entity being processed does not contain a version field. This processing is expensive. So, check for the existence of a version field before making this call.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1475) Performance improvement - don't
call syncVersion() when no version is specified
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis resolved OPENJPA-1475.
----------------------------------
Resolution: Fixed
> Performance improvement - don't call syncVersion() when no version is specified
> -------------------------------------------------------------------------------
>
> Key: OPENJPA-1475
> URL: https://issues.apache.org/jira/browse/OPENJPA-1475
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.0.0
> Reporter: Dianne Richards
> Assignee: Rick Curtis
> Fix For: 2.0.0
>
> Attachments: patch.txt
>
>
> Currently, StateManagerImpl loadFields() always calls syncVersion() when the entity being processed does not contain a version field. This processing is expensive. So, check for the existence of a version field before making this call.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OPENJPA-1475) Performance improvement - don't
call syncVersion() when no version is specified
Posted by "Dianne Richards (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dianne Richards reassigned OPENJPA-1475:
----------------------------------------
Assignee: Dianne Richards
> Performance improvement - don't call syncVersion() when no version is specified
> -------------------------------------------------------------------------------
>
> Key: OPENJPA-1475
> URL: https://issues.apache.org/jira/browse/OPENJPA-1475
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.0.0
> Reporter: Dianne Richards
> Assignee: Dianne Richards
> Fix For: 2.0.0
>
>
> Currently, StateManagerImpl loadFields() always calls syncVersion() when the entity being processed does not contain a version field. This processing is expensive. So, check for the existence of a version field before making this call.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OPENJPA-1475) Performance improvement - don't
call syncVersion() when no version is specified
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis reassigned OPENJPA-1475:
------------------------------------
Assignee: Rick Curtis (was: Dianne Richards)
> Performance improvement - don't call syncVersion() when no version is specified
> -------------------------------------------------------------------------------
>
> Key: OPENJPA-1475
> URL: https://issues.apache.org/jira/browse/OPENJPA-1475
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.0.0
> Reporter: Dianne Richards
> Assignee: Rick Curtis
> Fix For: 2.0.0
>
> Attachments: patch.txt
>
>
> Currently, StateManagerImpl loadFields() always calls syncVersion() when the entity being processed does not contain a version field. This processing is expensive. So, check for the existence of a version field before making this call.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1475) Performance improvement - don't
call syncVersion() when no version is specified
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803517#action_12803517 ]
Rick Curtis commented on OPENJPA-1475:
--------------------------------------
Committed revision 901901 to trunk.
Thanks Dianne!
> Performance improvement - don't call syncVersion() when no version is specified
> -------------------------------------------------------------------------------
>
> Key: OPENJPA-1475
> URL: https://issues.apache.org/jira/browse/OPENJPA-1475
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.0.0
> Reporter: Dianne Richards
> Assignee: Rick Curtis
> Fix For: 2.0.0
>
> Attachments: patch.txt
>
>
> Currently, StateManagerImpl loadFields() always calls syncVersion() when the entity being processed does not contain a version field. This processing is expensive. So, check for the existence of a version field before making this call.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1475) Performance improvement - don't call
syncVersion() when no version is specified
Posted by "Dianne Richards (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dianne Richards updated OPENJPA-1475:
-------------------------------------
Attachment: patch.txt
Attaching patch with enhancement.
> Performance improvement - don't call syncVersion() when no version is specified
> -------------------------------------------------------------------------------
>
> Key: OPENJPA-1475
> URL: https://issues.apache.org/jira/browse/OPENJPA-1475
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.0.0
> Reporter: Dianne Richards
> Assignee: Dianne Richards
> Fix For: 2.0.0
>
> Attachments: patch.txt
>
>
> Currently, StateManagerImpl loadFields() always calls syncVersion() when the entity being processed does not contain a version field. This processing is expensive. So, check for the existence of a version field before making this call.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1475) Performance improvement - don't call
syncVersion() when no version is specified
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1475:
----------------------------------
Affects Version/s: (was: 2.0.0)
2.0.0-beta
Fix Version/s: (was: 2.0.0)
2.0.0-beta2
> Performance improvement - don't call syncVersion() when no version is specified
> -------------------------------------------------------------------------------
>
> Key: OPENJPA-1475
> URL: https://issues.apache.org/jira/browse/OPENJPA-1475
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 2.0.0-beta
> Reporter: Dianne Richards
> Assignee: Rick Curtis
> Fix For: 2.0.0-beta2
>
> Attachments: patch.txt
>
>
> Currently, StateManagerImpl loadFields() always calls syncVersion() when the entity being processed does not contain a version field. This processing is expensive. So, check for the existence of a version field before making this call.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.