Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Talk:EclipseLinkCachingAndLocking

Revision as of 21:05, 21 July 2008 by Unnamed Poltroon (Talk) (Discussion)

Discussion

For @Cache, the existence option should still be allowed when not using a shared cache. Also its default in JPA is check-database.

The default cache size is 100.

James.sutherland.oracle.com 14:19, 21 July 2008 (EDT)

Will move existence checking out of the check box-enabled panel

The default for existence checking says CHECK_CACHE in the ExistenceChecking annotation. In org.eclipse.persistence.queries.DoesExistQuery the existencePolicy is set to CHECK_CACHE in the constructor, so that also looks to be the default if no ExistenceChecking annotation is used.

Yes, the @Cache annotation has the default size set to 100. The problem with this is how do you reconcile that with the persistence unit properties eclipselink.cache.size.default being 1000? I had asked about this internally, but never entered a bug, should I?

Karen.moore.oracle.com 21:05, 21 July 2008 (EDT)

Back to the top