[
https://issues.apache.org/jira/browse/OPENJPA-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423920#comment-13423920
]
Kevin Sutter commented on OPENJPA-2235:
---------------------------------------
The code patch looks clean. I would suggest a few more comments in the header
block for this method... Since we're kind of extending the use of the
getForUpdateClause() method to only do the "WITH UR" clause if isForUpdate
parameter is false, it would be good to explain that. Either that, or we
should consider breaking off these two aspects into separate methods. Not sure
of the ripple effect though with this type of change. Thanks.
> "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-2235.patch, 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
