• 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
Mapping multiple EOs to one table
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Mapping multiple EOs to one table


  • Subject: Mapping multiple EOs to one table
  • From: Ray Ackland <email@hidden>
  • Date: Sat, 16 Aug 2003 19:13:48 +1200

I have found that EOModeler can create "overlapping" enterprise objects mapping to one table, so information in the table can be used in several different classes.

I have found this useful to present layout variations in my D2J app (each related EO represents a layout in a switch view). This works really well.

The problem is that when I create a new master EO, WO creates a new row in the database fine, but then tries to do it again for each related EO (using the same primary key). The result is an error saying the primary key isn't unique when it tries to insert another row.

I realise that I could put the information in separate tables, but this means manually adding key paths to the views for each field I want to have in multiple views.

Does anyone know a way to get D2J to update the row that already exists, rather than creating a new one?

Thanks,

Ray.
_______________________________________________
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.

  • Follow-Ups:
    • Re: Mapping multiple EOs to one table
      • From: Ricardo Strausz <email@hidden>
  • Prev by Date: Re: Problems using primary key as attribute
  • Next by Date: Re: New WO book - "WebObjects 5 for Mac OS X
  • Previous by thread: Re: Problems using primary key as attribute
  • Next by thread: Re: Mapping multiple EOs to one table
  • Index(es):
    • Date
    • Thread