[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] Update JPQL does not invalidate Entity caches, bug?
|
Hi Igor,
When execute update JPQL query and then update entity, that also
updated in
JQPL in one transaction
Looks like a found a bug in EclipseLink:
It's works as specified. Unfortunatly I can't find the specification
which defines this behaviour, but I am 100% sure I've read it somewhere
that NO bulk operation invalidates the cache.
You can eiter invalidate the caches by yourself or use a system like
Oracle DCN (database-triggered cache-invalidation).
But isn't your problem the entity update after the JPQL udate?
When i tested on other JPA implementations - Hibernate, OpenJPA,
DataNucleos
- all works as expected.
Sure that you even used a 2nd level cache? It's by default activated in
EclipseLink but not in Hibernate. Don't know about the other. By my
opinion 2nd level cache usually causes more trouble than it's doing
good.
Best regards
... Michael
--
http://michael.hoennig.de
