Hi, On Nov 20, 2013, at 4:38 AM, Comm unity <[email protected]> wrote:
> An empty fault could not be created because the object's class could not be > determined (e.g. the GID is temporary or it is for an abstract entity). Note that last bit. Is it possible that when you were trying to use inheritance that you flagged the ParentEntity (in EntityModeler) as being Abstract? If you did, then that is why you can’t instantiate it. Just uncheck it. HOWEVER… The EOModel is the foundation of any WO application. Choices you make in defining the Entities and their relationships will make profound differences in how every other aspect of how your application works. Get it right and it will seem like the app writes itself. Get it wrong and you’ll be constantly writing extra code to deal with the dissonance created by the model not truly representing reality. Let me ask this: Is this an existing set of databases, or ones that you are creating specifically for your application? If the databases are just for your application, I think you should reconsider how you are architecting things. If it is an existing set of databases, is there anything you can do at the DB level to simplify the structure? Some database engines have ways to hide things like cross-database inheritance. Dave ————————————————————————————— WebObjects - so easy that even Dave Avendasora can do it!™ ————————————————————————————— David Avendasora Senior Software Abuser Nekesto, Inc.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
