| Hi Geoff, I removed the padlock from the only "suspicious" item and still have the same error.
One thing to mention: on the exact same account, restarting the application resolve the issue, I mean the direct action works immediately after the restart...
maybe this make you think about something;) I'm clueless:(
Xavier
Keep an eye out for data columns like floats, timestamps, blobs - if you have the 'padlock' set on these, you can sometimes get weirdness. Try unchecking the padlock in eomodeler on anything that looks like it may have a precision problem, see if that helps.
HTH
Geoff
On 10/01/06, Ken Anderson <[EMAIL PROTECTED]> wrote: Why is it doing a save if it's just checking?
Since you are saving, you have a staleness problem - so it makes
sense that it only occurs some of the time. Are you running multiple
instances? Is your database being updated by anything outside of
your application?
If you answered yes to either question, you need to consider how
you're going to keep data up to date. Chuck Hill (and others) have
made many useful posts on this subject if you look in the archives.
The brute force way is to refresh your object(s) before you update
them, but there's still the possibility of running into trouble with
a stubborn contender.
Ken
PS - I bcc'd the omnigroup list instead of replying all.
On Jan 10, 2006, at 11:07 AM, Dev WO wrote:
> Hi,
> I'm having trouble debugging an issue:
> I've got a direct action that would validate a member account.
> So the method is simply checking the database to see if the email/
> account exists and if it is not already activated.
>
> But I end up with:
> ====
> com.webobjects.eoaccess.EOGeneralAdaptorException:
> updateValuesInRowDescribedByQualifier --
> com.webobjects.jdbcadaptor.JDBCChannel method failed to update row
> in database
> at
> com.webobjects.eoaccess.EODatabaseContext._exceptionWithDatabaseContex
> tInformationAdded(EODatabaseContext.java :4685)
> at com.webobjects.eoaccess.EODatabaseContext.performChanges
> (EODatabaseContext.java:6393)
> at
> com.webobjects.eocontrol.EOObjectStoreCoordinator.saveChangesInEditing
> Context( EOObjectStoreCoordinator.java:415)
> at com.webobjects.eocontrol.EOEditingContext.saveChanges
> (EOEditingContext.java:3226)
> at DirectAction.validateEmailAction(DirectAction.java:96)
> ====
>
> I have set EOAdaptorDebugEnabled=YES to check the SQL, and the SQL
> is correct...
> This doesn't happen every time, but time to time, so it's hard to
> track it down.
>
> Any clue on how to find where it comes from would be greatly
> appreciated:)
>
> Thanks
>
> Xavier
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list ( [email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/lists%
> 40anderhome.com
>
> This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/geoff.hopson%40gmail.com
This email sent to [EMAIL PROTECTED]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Help/Unsubscribe/Update your Subscription:
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
