openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-1944) Extra select statements executed when version column is null.
Date Tue, 22 Mar 2011 17:33:05 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009732#comment-13009732
] 

Rick Curtis commented on OPENJPA-1944:
--------------------------------------

The previous change that Mike committed causes an OLE if an Entity with a null version is
updated. The change I'm going to commit shortly here reverts the previous commit and looks
to see if a null version field has been loaded before going back to the DB. 

> Extra select statements executed when version column is null. 
> --------------------------------------------------------------
>
>                 Key: OPENJPA-1944
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1944
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.2.2, 2.1.0
>            Reporter: Michael Dick
>            Assignee: Rick Curtis
>             Fix For: 2.2.0
>
>
> This problem was originally reported on the users mailing list by Diego Cattelan. Link
to the thread :http://openjpa.208410.n2.nabble.com/N-query-problem-with-Version-td6027619.html
> The problem occurs if a null value is returned for an entity's version field. In this
case OpenJPA will issue a second select statement to re-fetch the version, potentially resulting
in a lot of repetitive SQL statements. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message