Message: 12
Date: Wed, 15 Sep 2004 20:12:29 -0700
From: Chuck Hill <email@hidden>
Subject: Re: Dev Environment Gone Haywire: Java Client Optimistic
locking failure on every save
To: Jaime Magiera <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
That exception should be the result of a DB operation. Enable SQL
logging and find which UPDATE statement is failing. Then try to
isolate which column(s) are not matching the DB.
Have you updated anything recently (OS, Java version, JDBC driver,
plugin, WO version, valueType in EOModel)?
Chuck
------------------------------
Message: 13
Date: Wed, 15 Sep 2004 22:28:02 -0600
From: Dana Wood <email@hidden>
Subject: Re: Dev Environment Gone Haywire: Java Client Optimistic
locking failure on every save
To: Jaime Magiera <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
I've seen something similar, and if memory serves, unchecking some of
the columns used for matching and locking records in the eomodeler that
aren't really that relevant can help alleviate this problem.
Dana
