Re: Update & Delete of an Enterprise Object causes EOEditingContext.saveChanges() to Exception
Re: Update & Delete of an Enterprise Object causes EOEditingContext.saveChanges() to Exception
- Subject: Re: Update & Delete of an Enterprise Object causes EOEditingContext.saveChanges() to Exception
- From: Chuck Hill <email@hidden>
- Date: Fri, 7 Nov 2008 17:47:04 -0800
On Nov 7, 2008, at 2:44 AM, Tim Kitchener wrote:
Since changing the database engine to InnoDB, I no longer get the
locking error. Just a
com.webobjects.eoaccess.EOGeneralAdaptorException:
updateStatementForRow: qualifier may not be null exception whenever
I call saveChanges() on my editing context.
We really need the entire, complete stack trace. Something odd is
going on.
Chuck
My primary key is set up as follows:
<Picture 1.png>
Hi TimMay be you could try with:DbTest dbObj = (DbTest)
EOUtilities.objectMatchingKeyAndValue (ec, "Test", "priKey", new
Integer(0));>> DbTest dbObj = (DbTest)
EOUtilities.objectMatchingKeyAndValue (ec,
"Test", "priKey", 0);
Cheers
Cheong Hee
_______________________________________________
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
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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