You would not need to insert logic at entity level but you'd still need to have the manipulated fields to be defined as entity fields (even if they should not be used). For now, I could use the traits provided by DoctrineExtensions to separate nested-set internals from entity definitions but I'll still search a way to have database design agnostic entities.
Le jeudi 8 octobre 2015 11:37:35 UTC+2, Marco Pivetta a écrit : > > On 7 October 2015 at 01:45, dunaeth <[email protected] <javascript:>> > wrote: > >> 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 ? >> > > Two metadata structures > > >> That sounds great but I cannot see how to implement those splitted >> metadata structure.Even wrapping entities would require to manipulate the >> internal fields. >> > > You don't need to operate at entity level with this sort of mapping: you > can add SQL to your queries or manipulate existing DQL/ORM logic via custom > walkers. > See how DoctrineExtensions does it > https://github.com/Atlantic18/DoctrineExtensions/tree/33778a4dd886734077c491056862653f81b2dbdd/lib/Gedmo > > > > Marco Pivetta > > http://twitter.com/Ocramius > > http://ocramius.github.com/ > > -- 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.
