• 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
EOModeler: Reorgs with multiple models and inheritance
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

EOModeler: Reorgs with multiple models and inheritance


  • Subject: EOModeler: Reorgs with multiple models and inheritance
  • From: Ian Joyner <email@hidden>
  • Date: Thu, 28 Jul 2005 10:21:43 +1000

Has anyone else had problems with EOModeler (5.2.4) when trying to add things to multiple models where entities are modelled with inheritance?

Specifically, I have a generic model and seven other submodels which model specific areas of the application. Entities in the submodels inherit from parent entities in the generic model.

Now what I wanted to do was change a relationship to another entity in a parent table to point at a new intermediate entity and then to the existing entity from the intermediate entity (to do a shallow hierarchy).

However, having made the changes in the generic model, opening submodels with descendent classes causes all sorts of aberrant behaviour in EOModeler, like just showing the entities as being empty with no attributes – closing the model and reopening seems to fix this.

If the above does not happen, the inherited relationship either shows the connection to the old entity, but I can't close the model without getting warnings about the inherited relationship not agreeing with the parent relationship, but I can't fix it either, nor can I delete the existing relationship and create a new correct one (or copy it from the parent).

Anyway, have others had problems of this kind? Is this a well-known problem that has been reported to Apple many times before? Is it fixed in 5.3, or is it addressed by Core Data (which I don't think is usable with WO anyway)? Should I submit a defect (bug :-)) report to Apple? Is there a correct sequence in EOModeler to achieve this sort of change in a model?

My workaround is to avoid this and make a general hierarchy so that a tree is implemented in a single table, but it would be nice not to run into this kind of problem in EOModeler if I really need to make this kind of change (and I'm sure that it is this kind of problem in EOModeler which put a lot of people off WO).

Thanks
Ian
Sportstec _______________________________________________
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


  • Prev by Date: Re: error starting up wotaskd
  • Next by Date: Re: Fetch Spec Misunderstanding
  • Previous by thread: Re: EOF and 100% Java client app
  • Next by thread: Out of error debugging
  • Index(es):
    • Date
    • Thread