In other words, considering this example: https://gist.github.com/Ocramius/3121916 (which creates table user_usergroup as relation between entities User and UserGroup)
Can I create a new entity that uses table user_usergroup in a mapping directly? The problem I am trying to solve is (using example of User and UserGroup) How can I track the admin activity and history of adding a User to a UserGroup? That is say I want to keep historical records of (admin_username, user, usergroup, date_added, date_removed), where user, usergroup are pulled from the user_usergroup relation. Dennis On Saturday, September 3, 2016 at 8:21:53 PM UTC-4, Dennis Matveyev wrote: > > Question -- can I model a Many-To-One relation going from an Entity into a > Many-To-Many relation? > > That is, from the example below, if I have entities Product and Option in > Many-To-Many relation , is it possible to connect PriceHistory entity to > relate to the ProductHasOptions relation? > > I am debating whether to do it as in the diagram below (if possible), or > if instead it is best to create ProductHasOption as an Entity with its own > id, and do "conventional" Many-To-One relations to/from relevant tables. > > > <https://lh3.googleusercontent.com/-UhFffI9uCSc/V8tn-eBCdUI/AAAAAAAASao/k9ueHXT_qSYv0lAnIDmPBGY5xS3-l1o1ACLcB/s1600/d4.PNG> > > -- 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 doctrine-user+unsubscr...@googlegroups.com. To post to this group, send email to doctrine-user@googlegroups.com. Visit this group at https://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
