>>The documentation is not really clear about this, so I'm just
>>posting my question here: what's the status of polymorphism
>>support in Castor ?
>>Has it been reimplemented/fixed ?
> Polymorphism (at least whow I understand it) is done via the extends attribute and
>works very well for me.
> I have created a patch which even allows OQL queries on base types to return the
>actual type of that objects. A simple example:
That's exactly what I meant: inheritance.
The idea is that we have base classes that have attributes that are common to all
products.
But every product has its own extensions in form of additional attributes and
relationships,
and the only way we see how we could implement this specialization is by using a
object-relational mapping: Castor ;-)
But inheritance capabilities in Castor would also mean that we can store inheritance
paths
into several tables or just in one (which is not normalized, but faster).
I think that Castor does support that, right ?
My point is that Castor is known not to support polymorphysm, but is that still true
(we made an evaluation of Castor some months ago and it still appears to be like
that in the documentation) ? Is the documentation outdated on that point ?
I not, what exactly is Castor's limitation in that area ?
> wile return A, B and C objects, depending on a tzype column you have to specify.
>
> This patch hasn't been included in the CVS so far, but we're working on that, and
>you can have it if you
> like to apply it for yourself.
I'm not that far right now, but I'll definately keep it in mind.
Thanks for any help about this...
--
-o) Pascal Bleser ATOS Origin/Aachen(DE) |
/\\ <[EMAIL PROTECTED]> |
_\_v <[EMAIL PROTECTED]> |
---------------------------------------------|
Jesus saves,Buddha makes incremental backups :
---------------------------------------------'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
