I'm using 1.0.3 version and default (per broker) cache
yes persistence broker wich fetch folder is different from that one wich
materialize children.
So to prevent this I need touch all objects in single persistence broker
(long-lived caches dont feet me because I'm using web application with
Martin Kalén wrote:
So you should never combine autoReconnect for MySQL JDBC URL and
testOnBorrow
for a Commons Pool-based Connection pool (like OJB's default- and
DBCP-based
pools). If you do, you will just create additional overhead by
checking the
same things twice.
The advantage of
If I cauld say OJB prefetch parent and children
reference in all folders wich I materizalize by this call it
would be more productive
I am slightly confused by this statement. Are you saying you want all
the children to be materialized when the parent is created, thus
populating all of
Clute, Andrew wrote:
If I cauld say OJB prefetch parent and children
reference in all folders wich I materizalize by this call it
would be more productive
I am slightly confused by this statement. Are you saying you want all
the children to be materialized when the parent is created, thus
If I cauld say OJB prefetch parent and children
reference in all folders wich I materizalize by this call
it would be
more productive
I am slightly confused by this statement. Are you saying you
want all
the children to be materialized when the parent is created, thus
Does the default Cache Impl in OJB 1.0.2 work with Optimistic locking?
We are having a problem when using the Os Cache implementation, but it
works fine with the default implementation. Before I try to figure out
what's wrong, I was wondering if it would be ok to just use the Default
Thanks Andrew!
That's what I need ;)
If I cauld say OJB prefetch parent and children
reference in all folders wich I materizalize by this call
it would be
more productive
I am slightly confused by this statement. Are you saying you
want all
the children to
Stijn de Witt wrote:
The advantage of mastering the Commons Pool options is that this will
work with all database servers that OJB supports, not just MySQL.
Do you know if the autoReconnect=true option alone will fix it? I have
seen mention of autoReconnectForPools option? We are not planning