Hi everyone,
I'm struggling to understand something here and am wondering if it's a
*feature* of WO/EOF.
I have an entity called "Category" with a not-nullable "name" String
field. When I create a new one and forget to set a "name"
I get a ValidationException that says "Please provide a Name" and I
spit the user back to the same page (good).
If I have an existing Category with a valid name, and I try to set the
name to null, the setter on the entity is never called (I have logging
in there) there is no validation and no SQL is generated.
The object just remains with it's old name the user moves off to
something else. It is as if they never tried to change it to null.
I would much rather a ValidationException be raised so I can hold up
there user and say "Please provide a Name" to make it clear that what
they were trying to do did not work.
Is it a "feature" of WO/EOF that it won't let you set a not-nullable
to null? Is there any way I can override this behavior?
WO 5.4.3 on 10.5.6
Wonder and WoLips from about 2 weeks ago.
Thanks very much,
-Dan Grec
_______________________________________________
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]
