openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OPENJPA-2235) "READ_UNCOMMITTED" setting for the fetch plan isolation level is ignored in DB2Dictionary
Date Wed, 10 Apr 2013 16:06:15 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Albert Lee resolved OPENJPA-2235.
---------------------------------

    Resolution: Fixed
    
> "READ_UNCOMMITTED" setting for the fetch plan isolation level is ignored in DB2Dictionary
> -----------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2235
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2235
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: performance, query
>    Affects Versions: 2.1.1, 2.2.0, 2.3.0
>            Reporter: Helen Xu
>            Assignee: Helen Xu
>             Fix For: 2.1.2, 2.3.0, 2.2.2, 2.2.1.1
>
>         Attachments: OPENJPA-2235.patch
>
>
> When user set query hint as shown below for db2, no "with UR" clause append to the query.
The setting is ignored.
> query.setHint("openjpa.FetchPlan.Isolation", "READ_UNCOMMITTED");
> Uncommitted read is very risky and should be avoid if it is possible. JPA specification
requires a minimum of read-committed isolation to ensure no "dirty read" and "non-repeatible
read" can occur. Use of read-uncommitted isolation may cause data integrity problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message