• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Why no 1to1 relationships?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Why no 1to1 relationships?


  • Subject: Why no 1to1 relationships?
  • From: Jeff Schmitz <email@hidden>
  • Date: Tue, 1 Apr 2008 21:29:17 -0500

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?

Thanks,
Jeff
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Why no 1to1 relationships?
      • From: Jacky Gagnon <email@hidden>
    • Re: Why no 1to1 relationships?
      • From: Andrew Lindesay <email@hidden>
    • Re: Why no 1to1 relationships?
      • From: Chuck Hill <email@hidden>
  • Prev by Date: [OT] Postgresql capital accentuated characters problem
  • Next by Date: Accessing Session
  • Previous by thread: Re: [OT] Postgresql capital accentuated characters problem
  • Next by thread: Re: Why no 1to1 relationships?
  • Index(es):
    • Date
    • Thread