READ_ONLY query hint causes uncommitted data to be loaded into shared cache
(Doc ID 1513181.1)
Last updated on MARCH 01, 2019
Applies to:
Oracle TopLink - Version 11.1.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
Setting the READ_ONLY query hint and executing a query against an EntityManager that has flushed new objects those entities will be loaded into the shared cache and continue to exist even if the transaction is rolled back
Refer EclipseLink bug 382410
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |