On Apr 1, 2008, at 7:29 PM, Jeff Schmitz wrote:
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?
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?
One to one relationships can only be made on primary key to primary
key joins. In relational calculus nothing else makes sense. I have
not done any modelling for a while, so I don't recall how / if Entity
Moder's wizard handles this. I'd be surprised if it did not.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
