You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Helen Xu (JIRA)" <ji...@apache.org> on 2012/07/20 01:55:33 UTC
[jira] [Updated] (OPENJPA-2235) "READ_UNCOMMITTED" setting for the
fetch plan isolation level is ignored in DB2Dictionary
[ https://issues.apache.org/jira/browse/OPENJPA-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Helen Xu updated OPENJPA-2235:
------------------------------
Attachment: OPENJPA-1955.patch
Fix and unit test attached.
> "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
> Attachments: OPENJPA-1955.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira