I don’t think this should be the case. Synchronization across contexts should
only happen once objects have been committed to the DB. Running the following
code generates the same output, regardless of whether OC synchronization is on
or off:
public static void main( String[] args ) {
Well, as long as you leave global synchronization enabled, it doesn't really
matter in which context you commit something, because every change gets
propagated everywhere. IMHO it doesn't make sense to use parent/child contexts
with that setting at all.
Maik
> Am 23.02.2017 um 09:38 schrieb M
Hi,
I'm looking for a more detailed explaination of the caching mechanism, as
we are running a quite important and big web application with cayenne, I
want to fine tune, because we run in some performance issues.
I only found this
https://cayenne.apache.org/docs/3.0/individual-object-caching.html
Hi Maik,
thx for your detailed and quick answer! Ok the thing with the ChildContext
was my fault, although I should know better, shame on me :-/
But anyway the result of my test is the same.
What I can verifiy is that when you commit sthg to a context, the child
contexts gets synched immediatetl
Hi Markus,
> I'm having some troubles understanding commitChanges() and
> commitChangesToParent() :-/
>
> I've created a test case with two ObjectContexts
> ObjectContext context1 = runtime.newContext();
> ObjectContext context2 = runtime.newContext();
Those two don't have a parent/child relatio
