You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Albert Lee (Closed) (JIRA)" <ji...@apache.org> on 2012/02/07 16:46:59 UTC

[jira] [Closed] (OPENJPA-2111) Optimize column based ResultSet lookup whereever feasible

     [ 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