Re: JDBCChannel method failed to update
Re: JDBCChannel method failed to update
- Subject: Re: JDBCChannel method failed to update
- From: Anjo Krank <email@hidden>
- Date: Thu, 27 Jul 2006 07:14:47 +0200
Am 27.07.2006 um 04:31 schrieb Corin Lawson:
I have removed locking from all but the primary key from the entity
and this has remedied the problem. But I am concerned that this is
not correct and may cause other problems. It is not possible for
the this error to be handled by the user because it occurs within a
web service operation that does not provide persistent
transactions. The problem appears when the user is making a series
of modifications to one entity and I think it is due to that each
transaction/modification is being handled by a different instance
of the application whose object store has become dirty. So in
addition to reducing the locking attributes I have ensured that the
EOEditingContext refaults before each transaction. (I suspect only
one would be necessary.)
There used to be something in Mysql where, when you had a single non-
null timestamp column, it would auto-update it on UPDATE.
And there is code in Project Wonder that handles this.
(ERXTolerantSaver, ERXEOControlUtilities and ERXEC)
Cheers, Anjo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden