I'm going to leave this up in case anyone else has the same problem.
The answer is that you must specify the primary key, if the unique
field is not the primary key. Here is a working example:
[code=php]
new sfValidatorPropelUnique(
array(
'model' => 'Members',
'colu
I spoke too soon. Now it allows you to create multiple entries with
the same user name. I've spent about 12 hours researching this, I
read the form book, looked through all the tutorials, looked at the
api documentation and search good for hours. Can someone please for
the love of god help me f
Hello..
I had this issue.. you need to put in the primary_key the field that is
unique.
In this case: 'primary_key' => 'user_name'
Rgds,
Lic. Matías López
E-mail: lopezmat...@gmail.com
Movil: +54 9 341 155 799291
On Wed, Mar 11, 2009 at 10:49 PM, Benjamin wrote:
>
> I spoke too soon. Now i
Hey Ben,
no, your first version is right. You only need to pass model and
column.
The object that your form is updating needs to have a primary key set
though, in order to be considered an update. otherwise it will be
considered new and the update will fail.
In the most basic propel form setup n
Hi,
I had the same problem
My solution is to create custom validator inherited from
sfValidatorPropelUnique wich accepts 'criteia' object as an option
it allows to set NOT_EQUAL criteria for my instance id in validator
when editing
Best wishes,
Yuriy
On Sep 12, 7:09 pm, Richtermeister wrote:
Hi
I just ran into the same problem, and while I found the solution in
this discussion, I think it is not clear enough, so let me repeat
briefly, in case anyone comes across this in the future:
like Richtermeister says, the problem can be solved by adding a
_uniques key to the schema, and using
Hey Stefan,
The initial form knows whether it's new or an update, because you give
it a concrete object into the constructor, and most likely you have
retrieved this object by its primary key before, so it's fully
populated.
If sending the pk via hidden input rubs anybody wrong, you don't have
t
