Hello Matthew, implementing embeddables in a performant, non-inversive way was very complicated already.
I don't think we will be extending the functionality of Embedabbles much in the future, because of the complexity. Inheritance is something that would be very complex to add. You could alternatively try to use "object" type or a custom one instead, serializing to and from json for example. That would be trivial to implement for yourself. greetings Benjamin On Sat, Apr 11, 2015 at 1:20 PM, matthew_be <[email protected]> wrote: > Are there any plans to further develop the possibilities of Embeddables? I > thought they're still pretty limited right now. > > For example, wouldn't it be nice to allow an Embeddable to have an > @InheritanceType("SINGLE_TABLE") ? > (If you need a use case I can give an example). > > -- > You received this message because you are subscribed to the Google Groups > "doctrine-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/doctrine-user. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
