My Oracle Support Banner

REFRESH Hint On Object That Contains @JoinFetch Does Not Refresh Cache (Doc ID 1595690.1)

Last updated on MARCH 18, 2019

Applies to:

Oracle TopLink - Version 12.1.1.0 to 12.1.1.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

Disclaimer

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

 

When REFRESH hint is set to true on a query for an object that contains @JoinFetch relationship, the related objects are not updated with changes from the database. For example:

Project -- ManyToOne --> Employee

The ManyToOne is also annotated with @JoinFetch. Query the Plan object and after that re-querying the Plan object with the REFRESH hint set to true you will not see any changes in the database from out of bounds update to the Service object (e.g. out of bounds update could be from another appserver or application).

Example Environment:

Toplink 12.1.1.0
java version "1.6.0_43"
Oracle 11g 11.2.0.3 with Oracle Thin JDBC 11.2.0.3 Driver

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.