On Tuesday, 11 March 2014 11:23:00 UTC+1, Parsifal wrote: > Imagine that update with foreach is in orders table but that findBy is not > by primary key but something else. Then the mapping to client causes that > notice because ManyToOne from orders to client. Since I cannot use > inheritance in this case how to avoid the notice? >
By getting your mapping right. Maybe you turned around the OneToMany and Many ToOne again? Order, the owning side, should have a $client field which is a ManyToOne mapping to a Client entity and Client, the inverse side, should (in the case of a bidirectional association) have a $orders field, which holds a collection of Order entities and is OneToMany to Order. -- 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.
