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] <javascript:>> 
> 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] <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.

Reply via email to