> You can take my example and make yaml based the second option, please I'm not going to do this for you. If you run into any errors, ask about them. If you get different behavior than you would expect, describe what's going on. In other words: ask for help on specific problems you encounter (and describe these problems in detail).
> Ideally the first option, now only a question what is the reason that the > first is not possible to have extra columns? Doctrine simply doesn't support it, because it doesn't make any sense. -- Jasper N. Brouwer (@jaspernbrouwer) On 7 Jan 2014, at 20:01, Sandro Cândido <[email protected]> wrote: > HI > You can take my example and make yaml based the second option, please > > Ideally the first option, now only a question what is the reason that > the first is not possible to have extra columns? > > > Em terça-feira, 7 de janeiro de 2014 16h15min54s UTC-2, Jàπ (Jasper N. > Brouwer) escreveu: >> You have 2 options: >> >> 1) User <- ManyToMany -> Group, where the join-table does _not_ have extra >> columns. >> >> 2) User <- OneToMany -> Membership <- ManyToOne -> Group, where Membership >> can have as many extra properties (and even other associations) as you like. >> >> You'll have to choose! -- 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/groups/opt_out.
