• 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: EOModeller Question - probably inheritance
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOModeller Question - probably inheritance


  • Subject: Re: EOModeller Question - probably inheritance
  • From: Ray Ackland <email@hidden>
  • Date: Sun, 11 Jan 2004 13:35:56 +1300

Jonathan,

To me, it sounds like you are wanting to make things clearer in your intermediate table for when you view it using SQL outside of the WO environment as you won't normally be using the intermediate table in your WO design. My answer relates to that, as if this is not the case you are likely to get bombarded with people telling you what a bad design concept it was.

In fact, even when looking up the table using sql, you could relate and include the columns from the other tables. But instead of telling you how I would design things, let's concentrate on solving your problem.

One way you could try it (if you wanted WO to keep things updated) - and note, this is just an idea, I have never tested it to see what happens - you could go into EOModeler and flatten the attribute you are wanting. Then go to that flattened attribute and give it a column name. This seems to remove the bolding (signalling the flattened part) so may just make this a normal attribute - or perhaps WO will keep that attribute updated!! I doubt it though.

Perhaps the only way of doing it is to put two extra columns in your database, and every so often run an query which updates the table from the related records. To be honest, I don't see this being of any advantage over just dynamically relating the tables.

But, those are my 2c worth. Good luck with whatever you go for.

ray.

On 11/01/2004, at 6:14, Jonathan Fleming wrote:

I Have a join entity (as in a many-to-many) and as you all may well know all it does is track which row of one entity joins with certain rows of another entity by their PK id's given that I have a job table/entity >>> and a <<< category table/entity, however, what I would like to do for a little more clarity as to what PK is what JobName or categoryName is to copy the value of the jobName attribute from the Job entity into an attribute in the Join table as well as copy the value of categoryName from the Category entity into an attribute of the Join entity.

Can anyone tell me the best way to go about doing that please.
_______________________________________________
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: 
 >EOModeller Question - probably inheritance (From: "Jonathan Fleming" <email@hidden>)

  • Prev by Date: Re: EOModeling
  • Next by Date: Getting application instance in Direct Action
  • Previous by thread: EOModeller Question - probably inheritance
  • Next by thread: Re: EOModeller Question - probably inheritance
  • Index(es):
    • Date
    • Thread