[eclipselink-dev] Re: bug 286961: ModifyAllQuery.invalidateCache should

["Andrei Ilitchev" <andrei.ilitchev@xxxxxxxxxx>]

The final patch checked into both trunk and 1.1. Reviewed by James.

----- Original Message -----

From: Andrei Ilitchev

To: Dev mailing list for Eclipse Persistence Services

Sent: Tuesday, August 18, 2009 7:05 PM

Subject: bug 286961: ModifyAllQuery.invalidateCache should never check ReadLocks

New Patch

The patch has been reworked following feedback from Chris and James.
Rather than adding an extra parameter to an existing method a new method
invalidateObjects was defined, which should perform better. Also ModifyAllQuery
no longer invalidates any objects in case none was modified in the db.

----- Original Message -----

From: Andrei Ilitchev

To: Dev mailing list for Eclipse Persistence Services

Sent: Tuesday, August 18, 2009 11:49 AM

Subject: Re: [eclipselink-dev] Re: Bug 280803: JPA 2.0 Pessimistic Locking Scope

Logged and suggested a patch for bug 286961: ModifyAllQuery.invalidateCache should never check ReadLocks

https://bugs.eclipse.org/bugs/show_bug.cgi?id=286961

 

Please send any feedback you may have.

Thanks,

Andrei