Brian McCallister wrote:
What database are you using?
I have hit (and not yet fixed =/) precision difference problems when dealing with postgres.
Thought we have fixed this issue by explicit call of #setNanos(0) in ClassDescriptor?
long newCv = (new Date()).getTime(); Timestamp ts = new Timestamp(newCv); ts.setNanos(0); f.set(obj, ts);
Does it only fix an issue with oracle?
regards, Armin
-Brian
On Aug 11, 2004, at 10:23 AM, Alessandro Colantoni wrote:
Hi again.
I saw that my problem is not in the OSCACHE, but in the locking.
I set isolation level = optimistic in the jdbc connection descriptor, and I put in my table a field with locking=true
Every time I do an update on an element of this table I got the OptmisticLockException. It looks like the element is never released. Have I to set any LockManager in the ojb.properies? I have to put in my code something to release the element? I tried to remove the cache with OjbCache cache broker.serviceObjectCache(); cASOcacheVO = (CASOVO)cache.lookup(oid) cache.remove(oid). But it still doesn't work I tried cahe.clear and still nothing. What I have to do?
Please help me Thanks
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
