Hi Jeff,
I've decided to fully EOize my app to replace my current use of
flat files, mainly to better deal with concurrency issues. In
creating my analogous tables, I found that there's no way to
specify a "1 to 1" relationship between tables using the Entity
Modeler tool. Is there a specific reason for this? Or is it just
figured that you might as well make it one to many anyway even if
it is just one to one?
You can specify «1 to 1» relationship with Entity Modeler.
If the destination cannot be null, use the same id in the two tables.
-In Properties > Basic select : the cardinality «To One», your
destination, and add your primary keys.
-In Properties > Advanced select : for the source object, check
Propagates primary key and Owns Destination (if the destination
object cannot exist without an owner).
Good luck!
Jacky
If you're wondering why I want to do this, it's to hopefully reduce
conflicts of multiple people updating the same record in a table.
Is that generally a good reason to split 1 to 1 data into two tables?
Thanks,
Jeff
_______________________________________________
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/jgagnon%
40druide.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
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 [EMAIL PROTECTED]
