| Robert, Woops! That did it (the diamond right). I guess that generates classes for each attribute?
Thanks, -dustin On Aug 18, 2006, at 3:40 PM, Robert Walker wrote: Dustin,
You aren't using inheritance by chance are you?
From:
Allows Null By default, attributes you add to entities allow null values, except in the case of primary keys. This means that Enterprise Objects allows attributes containing no values to be saved to the data source. In some cases, such as when using inheritance, allowing null values may be necessary. On Aug 18, 2006, at 4:32 PM, Dustin Withers wrote: Hello All,
So I have a foreign key that does not allow nulls and the relationship to the primary is Mandatory. When I run the direct to web app and create a new record D2W comes back telling me that the foreign key does not allow nulls and will not save the record. If I allow nulls on the foreign key Entity Modeler complains and says "DBTest/Entity:People/Relationship:building is mandatory but DBTest/Entity:People/Attributes:buildingID allows null." but the D2W app works fine at this point. I don't mind allowing null but I don't understand why things are functioning this way.
The database is MySQL 4
Any ideas?
-dustin
_______________________________________________ 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 (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
