StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17873821
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-07-26T05:46:53.440
FavoriteCount
0
LastActivityDate
2013-07-26T05:46:53.440
LastEditDate
LastEditorUserId
0
OwnerUserId
2044355
ParentId
13751279
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Not exactly sure that it will work with the collection, but it certainly works with a single form. Please try this idea. First make a form for your basic entity <code>ComplaintBase</code> <pre><code>class ComplaintForm extends AbstractType { public function buildForm(FormBuilderInterface $builder, array $options) { $subscriber = new ComplaintSubscriber($builder); $builder->addEventSubscriber($subscriber); /* your fields */ } public function setDefaultOptions(OptionsResolverInterface $resolver) { $resolver->setDefaults(array( 'data_class' => 'Acme\ConsultBundle\Entity\ComplaintBase', )); } } </code></pre> Then in subscriber you can define additional fields based on submitted entity type. <pre><code>class ComplaintSubscriber implements EventSubscriberInterface { private $factory; private $builder; public function __construct(FormBuilderInterface $builder) { $this->factory = $builder->getFormFactory(); $this->builder = $builder; } public static function getSubscribedEvents() { return array( FormEvents::PRE_SET_DATA => 'preSetData', ); } public function preSetData(FormEvent $event) { $data = $event->getData(); $form = $event->getForm(); if (null === $data) { return; } $class = get_class($data); if( $class === 'Acme\ConsultBundle\Entity\ComplaintDefault' ) { $this->processDefault($data, $form); } elseif( $class === 'Acme\ConsultBundle\Entity\ComplaintRosacea' ) { $this->processRosacea($data, $form); } elseif( $class === 'Acme\ConsultBundle\Entity\ComplaintBotox' ) { $this->processBotox($data, $form); } else { #NOP } } protected function processDefault(Entity\ComplaintDefault $node, FormInterface &$form) { #NOP } protected function processRosacea(Entity\ComplaintRosacea $node, FormInterface &$form) { $form->add($this->factory->createNamed('some_field', 'text')); } protected function processBotox(Entity\ComplaintBotox $node, FormInterface &$form) { $form->add($this->factory->createNamed('other_field', 'text')); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSymfony2: Adding a collection based on a table-inheritance structure to a FormView
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAlexey B.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThis feels like a very restrictive approach, every time you want to add a new table to the group you would need to add a new if statement and a new function. An approach using the collection type like this: http://forum.symfony-project.org/viewtopic.php?f=23&t=37873 is a much more configurable solution. I would steer away from hardcoding class names in code that you might want to be reusable. You could not, for instance, use your subscriber for another instance of cti and would have to create another almost identical one
 singulars
 PostPostId
 PO
 UserUserId
 USLuke
2. COThis is just an idea, not a complete solution. Of course you can go through all the fields of a class and add to the form. But if the fields that do not need to add? Make your annotations, settings and so on ...
 singulars
 PostPostId
 PO
 UserUserId
 USAlexey B.

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.