Hi Armin,
Hi Jair jr,
Jair da Silva Ferreira Júnior wrote:
Hi Armin,
Thank you for your fast reply.
hmm, this should not happend. Do you use checkpoint() or flush()
in your code?
This only could happens when the object was already in DB. Only the
PersistenceBrokerImpl and
Hi,
Is this fix going to be available in the final 1.0 version coming
out in
1 or 2 days?
yes, a fix or workaround
regards,
Armin
Jair da Silva Ferreira Júnior wrote:
Hi Armin,
Hi Jair jr,
Jair da Silva Ferreira Júnior wrote:
Hi Armin,
Thank you for your fast reply.
hmm, this
Hi Jair jr,
Jair da Silva Ferreira Júnior wrote:
Hi Armin,
Thank you for your fast reply.
hmm, this should not happend. Do you use checkpoint() or flush()
in your code?
This only could happens when the object was already in DB. Only the
PersistenceBrokerImpl and RsIterator class push
Hi Armin,
Thank you for your fast reply.
hmm, this should not happend. Do you use checkpoint() or flush()
in your code?
This only could happens when the object was already in DB. Only the
PersistenceBrokerImpl and RsIterator class push objects to cache.
If you abort the tx, the PB
Hi,
I am using ojb1.0_rc5, ODMG api with OJB queries, mysql4 (innodb tables) in Linux
Red Hat 7.3 (kernel 2.4.20-20.7).
I moved from rc4 to rc5 recently and I noticed that sometimes the objects
persisted inside an aborted transaction are still in cache when another transaction is