Re: Vertical inheritance with a non-abstract superclass

2008-03-10 Thread David Elliott
On Mar 10, 2008, at 4:51 PM, David Avendasora wrote: On Mar 10, 2008, at 3:43 PM, David Elliott wrote: Woah. Hold up there. If you fetch one of the subclasses you will see one query. It will join the subclass table with the base table. That's it. It's only when you fetch the base

Re: Vertical inheritance with a non-abstract superclass

2008-03-10 Thread David Avendasora
On Mar 10, 2008, at 3:43 PM, David Elliott wrote: On Mar 10, 2008, at 11:35 AM, David Avendasora wrote: Nathan, I think you will find that Vertical Inheritance is much more resource intensive than you'd think. David Elliotts email points this out in that if query an object of the superc

Re: Vertical inheritance with a non-abstract superclass

2008-03-10 Thread David Elliott
On Mar 10, 2008, at 11:35 AM, David Avendasora wrote: Nathan, I think you will find that Vertical Inheritance is much more resource intensive than you'd think. David Elliotts email points this out in that if query an object of the superclass or any one subclass is requested, it does a qu

Re: Vertical inheritance with a non-abstract superclass

2008-03-10 Thread Chuck Hill
On Mar 10, 2008, at 7:34 AM, Nathan Gabrish wrote: Thank you for the help. I was able to pass the consistency check by adding restrictive qualifiers to both the super and subclasses (I could have sworn I had tried that already) however, this does not seem to work across models. What is a l

Re: Vertical inheritance with a non-abstract superclass

2008-03-10 Thread David Avendasora
Nathan, I think you will find that Vertical Inheritance is much more resource intensive than you'd think. David Elliotts email points this out in that if query an object of the superclass or any one subclass is requested, it does a query for each possible subclass as well. So if you have

Re: Vertical inheritance with a non-abstract superclass

2008-03-10 Thread Nathan Gabrish
Thank you for the help. I was able to pass the consistency check by adding restrictive qualifiers to both the super and subclasses (I could have sworn I had tried that already) however, this does not seem to work across models. What is a little confusing to me is the need to put a qualifier on the

Re: Vertical inheritance with a non-abstract superclass

2008-03-10 Thread David Avendasora
Non-abstract superclasses must have restricting qualifiers as well as their subclasses. What were the restricting qualifiers you used? They must be unique. Do you have any choice in the use of Vertical Inheritance? I used to use it as it made my "DB Normalization" voice stop screaming at me

Re: Vertical inheritance with a non-abstract superclass

2008-03-08 Thread David Elliott
Hi Nathan, Your problem is that your superclass is non-abstract. If you really do want instances of your superclass then you MUST write a qualifier to distinguish records in your base table that need to instantiate an object of your base class vs. records that have data in some other tab