StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13439504
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-11-18T10:59:07.083
FavoriteCount
0
LastActivityDate
2012-11-18T10:59:07.083
LastEditDate
LastEditorUserId
0
OwnerUserId
220180
ParentId
13435292
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I did exactly the same. My <code>InternalMessage</code> entity is your <code>Notification</code>. In the form, <code>users</code> field is not mapped (<code>property_path</code> is <code>false</code>) and it's validated using a subscriber: <pre class="lang-php prettyprint-override"><code>public function buildForm(FormBuilder $builder, array $options) { $builder ->add('title', 'text', array( 'label' => 'Titolo *' )) ->add('content', 'textarea', array( 'label' => 'Contenuto *' )) ->add('priority', new PriorityType(), array( 'label' => 'Priorità *' )) ->add('users', 'entity', array( 'label' => 'Destinatari *', 'class' => 'Acme\HelloBundle\Entity\User', 'property' => 'select_label', 'multiple' => true, 'expanded' => true, 'property_path' => false, )); ; $builder->addEventSubscriber(new AddUsersValidationSubscriber()); } </code></pre> While in my controller, the only thing i have to do (assuming that form is valid) is to create one <code>InternalMessageFeedback</code> entity (the same as your <code>UserNotification</code>) fore each user in form model: <pre class="lang-php prettyprint-override"><code>$message = new InternalMessage(); $form = $this->createForm(new InternalMessageType(), $message); // ... // The sender $message->setUser($this->getSecurityContext()->getToken()->getUser()); // Persist the inverse side $em = $this->getEntityManager(); $em->persist($message); // One feedback for each user /** @var $user \Acme\HelloBundle\Entity\User */ foreach($form->get('users')->getData() as $user) { $feedback = new InternalMessageFeedback(); // Se the message and user for current feedback $feedback->setInternalMessage($message); $feedback->setUser($user); // Persist the owning side $em->persist($feedback); // Sync the inverse side $message->addInternalMessageFeedback($feedback); } $em->flush(); </code></pre> Hope this helps :)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORender a many-to-many relation with extra fields into a form
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USgremo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORender a many-to-many relation with extra fields into a form
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks for your answer Gremo ;) I wasn't aware about the `property_path` property. And it's working like a charm.
 singulars
 PostPostId
 PO
 UserUserId
 USSimon Taisne

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.