Le 08/01/2014 11:14, Jasper N. Brouwer a écrit :
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.
To be more explicit about why it does not make sense, think about what
you get in PHP in the first case: you only have a list of Group
instances in the User. there is no place to store the values of the
extra columns. When trying to build the PHP representation of your data,
the second option will appear immediately as you will see that your
application itself needs the Membership object.
--
Christophe | Stof
--
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.
