First, thanks for your answers since I know my questions are not related to a common usage of Doctrine ORM ;)
So you mean I should be able to have two metadata structures for the same SQL schema, one for the entity mapping and the other for the database dependant behavior ? That sounds great but I cannot see how to implement those splitted metadata structure.Even wrapping entities would require to manipulate the internal fields. Or were you talking about splitting the schema ? Le mardi 6 octobre 2015 17:44:26 UTC+2, Marco Pivetta a écrit : > > Metadata cannot be manipulated at runtime, only during metadata loading. > > You can usually have a separate metadata structure to store those fields, > and then use them inside your specific logic. > > Marco Pivetta > > http://twitter.com/Ocramius > > http://ocramius.github.com/ > > On 6 October 2015 at 12:26, dunaeth <[email protected] <javascript:>> > wrote: > >> Actually, I already saw many nested-set behavioral plugins that added >> those so-called "internal" fields to entities - to compute left/right >> values at entity move for example - however I think that kind of data >> should only be known of ORM. So you confirm there's no way to avoid >> defining at entity level an ORM mapped field or to add those fields to the >> mapping when needed ? >> >> Le mardi 6 octobre 2015 17:17:51 UTC+2, Marco Pivetta a écrit : >>> >>> DQL would still be unaware of those fields as well >>> >>> Marco Pivetta >>> >>> http://twitter.com/Ocramius >>> >>> http://ocramius.github.com/ >>> >>> On 6 October 2015 at 12:14, dunaeth <[email protected]> wrote: >>> >>>> Seems like a good idea, won't it make it more difficult to manipulate >>>> those fields through DQL though ? >>>> >>>> Le mardi 6 octobre 2015 17:07:16 UTC+2, Marco Pivetta a écrit : >>>>> >>>>> Yes: simply do not map them. >>>>> >>>>> Marco Pivetta >>>>> >>>>> http://twitter.com/Ocramius >>>>> >>>>> http://ocramius.github.com/ >>>>> >>>>> On 6 October 2015 at 11:48, dunaeth <[email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> To achieve Model/Persistence separation, I'd like to restrict some >>>>>> database specific fields (like left/right values from nested-set >>>>>> implementations for RDBMS) to the ORM layer and that the entity layer >>>>>> stay >>>>>> unaware of those fields. Is it somehow possible to have this kind of >>>>>> behavior ? >>>>>> >>>>>> -- >>>>>> 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. >>>> >>> >>> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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.
