multiple levels of inheritance shouldn't really matter with respect to batch
faulting for single table inheritance (which i assume he's using based on the
restricting qualifier references) ... what DOES matter is if you refer to
abstract entities, which requires tripping faults to know what type
Understood Ken. Good point and I know you're right about performance
trade-offs. I've not given up just yet but I'll take your words to heart.
On 3/22/11 9:29 PM, Ken Anderson wrote:
Jon,
My point was that SQL optimizations are much easier to implement (I use Oracle
too) without an inherita
Jon,
My point was that SQL optimizations are much easier to implement (I use Oracle
too) without an inheritance hierarchy, since EOF is less involved in building
queries to handle the structure. I actually have a situation today where I
regret using 2 levels of inheritance because I cannot tun
Hi Ken,
The inheritance is absolutely necessary and works a treat. My example EO tree
is just that, an example for the sake of simplicity. The real model supports
social network content types and is fairly esoteric (the example is easy to
understand and is a valid representation). While qui
Not to put a crimp in your model, but is inheritance really necessary here?
What actual behavior is different?
One level inheritance is hard to optimize - two levels, doubly so (at least!).
If you could share more about what kind of behavior you're looking for from
these objects it might be h
Hi Chuck.
Yes, I'm using 2-3 week old Wonder and there's no IN qualifier in play. I
don't think the Oracle optimizer likes that either although I'll definitely
give it a trial.
I'm still trying to get /*+ rule */ to work. I think that's my best bet.
Jon
On 3/22/11 5:47 PM, Chuck Hill wrote
Are you using Wonder? I thought that Wonder would collapse these into an IN.
Oracle might be more inclined to optimize that. It might be that the Wonder
qualifier support is not used for inheritance. You might try running the SQL
for that and see if the Oracle optimizer will play nice.
You
I have a fairly involved EO inheritance tree that works beautifully in every
way but one. Here's a quick example illustrating the structure I'm using:
Human
North American
American
Canadian
Mexican
European
German
Italian
Spaniard
Asia
