Re: Mapping multiple EOs to one table
Re: Mapping multiple EOs to one table
- Subject: Re: Mapping multiple EOs to one table
- From: Ricardo Strausz <email@hidden>
- Date: Mon, 18 Aug 2003 13:08:58 -0500
Just guessing...
but first, does you multiple views of the same table inherits from one
the other?
It may be that, if you want to have different views from the same
table, define different childs for it (and not simply unrelated
entities which may confuse EOM).
Hope it helps! let us know
Dino
On sabado, agos 16, 2003, at 02:13 America/Mexico_City, Ray Ackland
wrote:
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.
_______________________________________________
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.