I have an EO with a not null constraint on a date columnn. I have a function
that I call from a click that sets a boolean (isDeleted) to true and saves the
EO.
try {
contactEO.saveChanges();
} catch (ValidationException e) {
NSLog.out.appendln("ValidationException e = " + e.getMessage());
} catch (EOGeneralAdaptorException e) {
NSLog.out.appendln("EOGeneralAdaptorException e = " + e.getMessage());
}
}
It is throwing an exception and claiming that the date field is null and
violates the not null constraint. I don't have anyplace in the interface that
is wired to the date column in question (it is the insertion date).
I guess I could just set the EO to accept nulls but I thought I would try to
understand why the saveChanges() is trying to update the row with a null.
Thanks,
Ted
_______________________________________________
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]
