You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (Created) (JIRA)" <ji...@apache.org> on 2012/01/18 00:37:39 UTC
[jira] [Created] (OPENJPA-2111) Optimize column based ResultSet
lookup whereever feasible
Optimize column based ResultSet lookup whereever feasible
---------------------------------------------------------
Key: OPENJPA-2111
URL: https://issues.apache.org/jira/browse/OPENJPA-2111
Project: OpenJPA
Issue Type: New Feature
Components: jdbc
Affects Versions: 2.2.0
Reporter: Pinaki Poddar
Assignee: Pinaki Poddar
Fix For: 2.2.0
The column values of a result are accessed to populate each persistent instance. This frequent operation requires a lookup. This lookup process can be optimized for special cases where each projected column is distinct by name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENJPA-2111) Optimize column based ResultSet
lookup whereever feasible
Posted by "Albert Lee (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee updated OPENJPA-2111:
--------------------------------
Fix Version/s: (was: 2.2.0)
2.3.0
Move fix version to 2.3.0 in preparation for 2.2.0 release.
> Optimize column based ResultSet lookup whereever feasible
> ---------------------------------------------------------
>
> Key: OPENJPA-2111
> URL: https://issues.apache.org/jira/browse/OPENJPA-2111
> Project: OpenJPA
> Issue Type: New Feature
> Components: jdbc
> Affects Versions: 2.2.0
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.3.0
>
>
> The column values of a result are accessed to populate each persistent instance. This frequent operation requires a lookup. This lookup process can be optimized for special cases where each projected column is distinct by name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENJPA-2111) Optimize column based ResultSet
lookup whereever feasible
Posted by "Albert Lee (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee resolved OPENJPA-2111.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.3.0)
2.2.0
Pinaki confirmed this issue has been resolved in parallel with work in OPENJPA-2099.
> Optimize column based ResultSet lookup whereever feasible
> ---------------------------------------------------------
>
> Key: OPENJPA-2111
> URL: https://issues.apache.org/jira/browse/OPENJPA-2111
> Project: OpenJPA
> Issue Type: New Feature
> Components: jdbc
> Affects Versions: 2.2.0
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.2.0
>
>
> The column values of a result are accessed to populate each persistent instance. This frequent operation requires a lookup. This lookup process can be optimized for special cases where each projected column is distinct by name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENJPA-2111) Optimize column based ResultSet
lookup whereever feasible
Posted by "Albert Lee (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-2111.
-------------------------------
> Optimize column based ResultSet lookup whereever feasible
> ---------------------------------------------------------
>
> Key: OPENJPA-2111
> URL: https://issues.apache.org/jira/browse/OPENJPA-2111
> Project: OpenJPA
> Issue Type: New Feature
> Components: jdbc
> Affects Versions: 2.2.0
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.2.0
>
>
> The column values of a result are accessed to populate each persistent instance. This frequent operation requires a lookup. This lookup process can be optimized for special cases where each projected column is distinct by name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENJPA-2111) Optimize column based ResultSet
lookup whereever feasible
Posted by "Kevin Sutter (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter updated OPENJPA-2111:
----------------------------------
Fix Version/s: (was: 2.2.0)
> Optimize column based ResultSet lookup whereever feasible
> ---------------------------------------------------------
>
> Key: OPENJPA-2111
> URL: https://issues.apache.org/jira/browse/OPENJPA-2111
> Project: OpenJPA
> Issue Type: New Feature
> Components: jdbc
> Affects Versions: 2.2.0
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
>
> The column values of a result are accessed to populate each persistent instance. This frequent operation requires a lookup. This lookup process can be optimized for special cases where each projected column is distinct by name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (OPENJPA-2111) Optimize column based ResultSet
lookup whereever feasible
Posted by "Kevin Sutter (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter reopened OPENJPA-2111:
-----------------------------------
> Optimize column based ResultSet lookup whereever feasible
> ---------------------------------------------------------
>
> Key: OPENJPA-2111
> URL: https://issues.apache.org/jira/browse/OPENJPA-2111
> Project: OpenJPA
> Issue Type: New Feature
> Components: jdbc
> Affects Versions: 2.2.0
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
>
> The column values of a result are accessed to populate each persistent instance. This frequent operation requires a lookup. This lookup process can be optimized for special cases where each projected column is distinct by name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira