Re: Null value in column on insert when marked as mandatory in EO Model?
Re: Null value in column on insert when marked as mandatory in EO Model?
- Subject: Re: Null value in column on insert when marked as mandatory in EO Model?
- From: Simon McLean <email@hidden>
- Date: Fri, 05 Dec 2008 15:59:11 +0000
Hi -
We've seen this too, but running on MySQL. It's really bizarre. The
EO's are built, the relationship set but then sometime between
saveChanges() and the raw SQL being sent to the DB it seems to forget
the foreign key in the relationship.
I've asked myself the same question too: how the hell did it get
passed model validation ?!!
Unfortunately we've never got to the bottom of it either...
Simon
On 5 Dec 2008, at 15:22, Alan Zebchuk wrote:
I seem to get the following exception in one of my applications
lately:
com.webobjects.eoaccess.EOGeneralAdaptorException:
EvaluateExpression failed:
<com.webobjects.jdbcadaptor.PostgresqlExpression: "INSERT INTO "......
Next exception:SQL State:23502 -- error code: 0 -- msg: ERROR: null
value in column "oid_person_type" violates not-null constraint
Any ideas how this could happen? The relationship and attribute are
marked as mandatory in the EO Model, so I'm not sure how this would
even pass through the validation?
It might be possible that this is related to load on the
application. I have 2 instance of this application, one which has a
much heavier load. This error is only occurring on this instance.
Any help is greatly appreciated,
Thanks,
Alan
_______________________________________________
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
_______________________________________________
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