Re: Vertical inheritance

2010-06-01 Thread Andrus Adamchik
Yes, multiple levels will be supported in the suggested design. All I was saying is that the JPA-style vertical inheritance approach seems to imply a strict single-join-table-per-subclass mapping. While with flattened attributes, you can (theoretically) mix and match where subclass attribut

Re: Vertical inheritance

2010-06-01 Thread Mike Kienenberger
What I probably should do is create a simple project using single-table inheritance, point it at a relevant subset of my current project's schema structure, and see exactly what it looks like in the modeler and in the generated code. On Tue, Jun 1, 2010 at 12:32 PM, Mike Kienenberger wrote: > I'm

Re: Vertical inheritance

2010-06-01 Thread Mike Kienenberger
I'm not complete certain I understand the design -- I don't have any experience with single-table inheritance. It sounds ok for as much as I do understand. The only concern I have is that the wording below seems to indicate that only two tables are involved (the root table and the subclass tabl

Re: Vertical inheritance

2010-06-01 Thread Andrus Adamchik
On May 31, 2010, at 9:11 AM, Andrus Adamchik wrote: BTW, semantically "vertical inheritance with discriminator" is essentially single-table inheritance with flattened attributes in subclasses. Which Cayenne supports already, but without any special optimizations for wide|deep hierarchies.