Databases
StackOverflow2013
Postsdbo
POForm validation ignores empty value
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POForm validation ignores empty value
    primarykey
    data
    text
    <p>FormType:</p> <pre><code>class BranchFormType extends AbstractType { public function buildForm(FormBuilderInterface $builder, array $options) { $builder-&gt;add('name'); } public function getName() { return 'branch'; } public function setDefaultOptions(OptionsResolverInterface $resolver) { $resolver-&gt;setDefaults(array( 'data_class' =&gt; 'My\MainBundle\Entity\Branch', )); } } </code></pre> <p>In entity definition:</p> <pre><code>&lt;field name="name" column="name" type="string" length="255"/&gt; </code></pre> <p>there is no nullable=true and the field has required attribute when rendered.</p> <p>Validation.yml:</p> <pre><code>My\MainBundle\Entity\Branch: properties: name: - NotBlank: ~ </code></pre> <p>Does symfony find this file automatically or do I have to included somewhere? The doc just states that the form uses validation service automatically.</p> <p>Controller:</p> <pre><code> $branch = new Branch(); $form = $this-&gt;createForm(new BranchFormType(), $branch); if ($request-&gt;isMethod('POST')) { $form-&gt;bindRequest($request); if ($form-&gt;isValid()) { $em-&gt;persist($branch); $em-&gt;flush(); return $this-&gt;redirect($this-&gt;generateUrl('view_branch')); } } return $this-&gt;render('MyMainBundle:Branch:create.html.twig', array( 'form' =&gt; $form-&gt;createView() )); </code></pre> <p>On submit I get following error:</p> <blockquote> <p>SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'name' cannot be null</p> </blockquote> <p>So isValid returns true despite the fact that name is empty and continues to persist the entity with empty values. How can isValid return true when the name is empty? ORM definition says nullable=false?`Any ideas? I have no extra validator defined. I use sf2.1</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMohammed Zayan
    1. USLost in OWL
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POForm validation ignores empty value
      1. USLost in OWL
      1. VTFavorite
    2. VO
      singulars
      1. POForm validation ignores empty value
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POForm validation ignores empty value
      1. USLost in OWL
      1. VTBountyStart
    1. CO`nullable=false` is a Doctrine constraint, `isValid` does not perform checks on the Doctrine side (Doctrine does not know how to validate en entity), it check only for assertions (NotBlank...) from the Validator component.
      singulars
      1. POForm validation ignores empty value
      1. USDamien
    2. COI guess there could be a problem with a cascade persist. Let say that your Branch entity has relation to another entity (with cascade persist) which have a "name" field as well. In your case if you set value for the "name" field in your Branch entity but don't set "name" field in related entity you'll got the same error as you described. So could you ensure that your relations don't cause this error? I maybe could say more if you post you Branch entity definition
      singulars
      1. POForm validation ignores empty value
      1. USCyprian
    3. COYou may be right, In sf toolbar there is an entity error, like "children refers to the owning side field Kloppe\SmsBundle\Entity\User#user which does not exist." here is the entity definition http://dpaste.com/879513/
      singulars
      1. POForm validation ignores empty value
      1. USLost in OWL
 

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