• 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
Re: Saving entities problem [SOLVED]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Saving entities problem [SOLVED]


  • Subject: Re: Saving entities problem [SOLVED]
  • From: Art Isbell <email@hidden>
  • Date: Thu, 31 Jul 2003 11:47:53 -1000

On Thursday, July 31, 2003, at 04:54  AM, Jevon Hills wrote:

The Join table exists in the DataBase, so EOModeler is not creating the Join.

Are you saying that you're stuck with the "join" entity as it's configured in the DB? I put "join" in quotes because with its own primary key and conventional foreign keys to the entities being joined, it's not a conventional join entity.


If you're stuck with this schema, then you may need to create a new join entity object, insert it into your EC, set both sides of its three to-one relationship values, and save. I.e, you wouldn't use the flattened relationships in User and no primary key values would be propagated. The EC should analyze the changes, insert the new User first so that it has a primary key value, then insert the "join" object with its foreign keys properly set.

Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Saving entities problem [SOLVED] (From: Jevon Hills <email@hidden>)

  • Prev by Date: Re: Saving entities problem [SOLVED]
  • Next by Date: Re: Duplicating an EO and all its relationships
  • Previous by thread: Re: Saving entities problem [SOLVED]
  • Next by thread: Re: Saving entities problem [SOLVED]
  • Index(es):
    • Date
    • Thread