Closer To The Ideal

I ran into this same problem, for which Symfony fails to offer a sensible error message:

It then occurred to me that the entire validator schema was being processed, not just the fields that are actually posted! This means that all the validators that are required=false will silently return a “clean” value, which is most likely the database default.

So what did this mean? Well, it meant that the validator was “cleaning” all the columns that had not been submitted with the form, including the version column, which was being set to null. When the versionable behaviour kicked in, it read this null value and incremented by 1 for the next version, which then became 1 – a version which of course already existed, causing the error.
The solution

The solution is blindingly simple, we don’t just declare the widget schema, we must also declare the validator schema. Whilst this seems like it makes sense, I feel that it is a shame that I have to essentially copy and paste the necessary validators from the base class.

This entry was posted on Thursday, May 7th, 2009 at 8:19 pm and is filed under symfony. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.