Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you are using 2.1 you may want to have a look at <a href="http://symfony.com/doc/current/book/forms.html#groups-based-on-submitted-data">"Groups based on submitted data"</a>.</p> <p><strong>Update</strong></p> <p>Example using the demo contact page <code>/demo/contact</code> in the default <code>AcmeDemoBundle</code> provided with Symfony Standard Edition :</p> <p>The form type with conditional validation groups :</p> <p> <pre><code>namespace Acme\DemoBundle\Form; use Symfony\Component\Form\AbstractType; use Symfony\Component\Form\FormBuilderInterface; use Symfony\Component\Form\FormInterface; use Symfony\Component\OptionsResolver\OptionsResolverInterface; use Symfony\Component\Validator\Constraints as Assert; class ContactType extends AbstractType { // Inject the validator so we can use it in the closure /** * @var Validator */ private $validator; /** * @param Validator $validator */ public function __construct(Validator $validator) { $this-&gt;validator = $validator; } public function buildForm(FormBuilderInterface $builder, array $options) { $builder-&gt;add('email', 'email'); $builder-&gt;add('message', 'textarea', array( // Added a constraint that will be applied if an email is provided 'constraints' =&gt; new Assert\NotBlank(array('groups' =&gt; array('EmailProvided'))), )); } public function setDefaultOptions(OptionsResolverInterface $resolver) { // This is needed as the closure doesn't have access to $this $validator = $this-&gt;validator; $resolver-&gt;setDefaults(array( 'validation_groups' =&gt; function(FormInterface $form) use ($validator) { // Get submitted data $data = $form-&gt;getData(); $email = $data['email']; // If email field is filled it will not be blank // Then we add a validation group so we can also check message field if (count($validator-&gt;validateValue($email, new Assert\NotBlank())) == 0) { return array('EmailProvided'); } }, )); } public function getName() { return 'contact'; } } </code></pre> <p>Don't forget to inject the <code>validator</code> service in the form type :</p> <pre><code>&lt;?php namespace Acme\DemoBundle\Controller; //... class DemoController extends Controller { // ... public function contactAction() { $form = $this-&gt;get('form.factory')-&gt;create(new ContactType($this-&gt;get('validator'))); // ... } } </code></pre> <p>As you can see validation of the <code>message</code> field will be triggered only if the <code>email</code> field is filled.</p> <p>Use a diff tool to catch the differences.</p>
    singulars
    1. This table or related slice is empty.
    1. POSymfony2 form validator groups without entities
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USiamdto
    1. USiamdto
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSymfony2 form validator groups without entities
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAs I clearly stated in my question, I'm not using entities, which that example uses..
      singulars
      1. PO
      1. USKristian
    2. COUsing entitie is not mandatory. See the closure example. It returns the validation group's name based on submitted data in form. It means you can do whatever checks you want in it with the content of `$form->getData();` and returns a name according to your computation.
      singulars
      1. PO
      1. USiamdto
    3. COI understand the example, but I'm not sure how to feed it with a matching set of constraints for validation..
      singulars
      1. PO
      1. USKristian
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload