| 5/5/2006 12:39:53 AM |
Hi,
I've seen the WIKI FAQ detailing the limitation that subentities must store their properties in the same table as the base class and I've seen a number of posts asking about this feature and workarounds to it (which I'm sure are what prompted the FAQ entry).
Can you give an indication as to whether this is something you will never support, something you might support in the future or something that is high on your list of changes to make and might be released shortly?
Thanks,
Phil |
| 5/5/2006 12:46:56 AM |
Hi Phil:
Its something I might support in the future, and its gradually rising higher on my list as I knock of other things. But its so far not something I view as necessary either -- even the creators of Hibernate warn people that using the other type of "database inheritance" with their mapper can be very inefficient in many cases. Instead, in most cases where you need a more complicated database model, you also need to go to greater pains to model it efficiently and optimize it -- a process that tends to not be very generic, i.e. not one-size-fits-all.
Thanks, Paul Wilson
|