Skip Headers

# Configuring Existence Checking at the Project Level

Previous

Next

When TopLink writes an object to the database, it runs an existence check to determine whether to perform an insert or an update operation.

By default, TopLink checks against the cache. Oracle recommends that you use this default existence check option for most applications. Checking the database for existence can cause a performance bottleneck in your application.

Table: Project Support for Existence Checking summarizes which projects support existence checking configuration.

Project Support for Existence Checking

Descriptor | Using TopLink Workbench | Using Java
--- | --- | ---
Relational Projects |  |
EIS Projects |  |
XML Projects |  |

By default, this configuration applies to all descriptors in a project. You can also configure existence checking at the descriptor level to override this project-level configuration on a descriptor-by-descriptor basis. For more information, see "Configuring Cache Existence Checking at the Descriptor Level".

For more information see the following:

- "Cache Type and Object Identity"

- "Queries and the Cache"

- "Using Registration and Existence Checking"