The 0.8.11 way of doing polymorphism is rather a dangerous. It does not always work. It depends on the order of the object being loaded. Because of that, it shouldn't be put back. On the other hand, the right way to do it is done it in lower layer. Basically, having the SQLEngine to attempt to join the base and extend table. It also takes some research to see how such query can be generated. There is limitation on outer join on database... It also involves some major changes to include the new logic. It probably won't be fast and easy. Thomas -----Original Message----- >From: Thorsten Mauch [mailto:[EMAIL PROTECTED]] >Sent: Thursday, February 14, 2002 3:52 AM >To: [EMAIL PROTECTED] >Subject: [castor-dev] Anybody currently working on Polymorhic Querys /Collection > >Hi All >I Currently work to integrate Castor with Coocon and Chiba. >But due to the lack of polymorhism I can use the current castor >version. >I don't like to do this effort for Castor 0.8.11. >So for me is very important to bring back polymorhism back to castor. >Is somebody currently woorking on that ? The last info I have about that >is the post from Richard Holmes. >Anyway if somebody have haso ideas how to implement it fast in a easy way it > >would make me happy :) >For the moment performance is only on the second rank. > >THanx Thorsten > >----------------------------------------------------------- >If you wish to unsubscribe from this mailing, send mail to >[EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
