Ernesto:
I like to make custom validation methods when dealing with complex
relationships between fields.
http://edwardawebb.com/programming/php-programming/cakephp/validating-optional-fields-cakephp-dreaded-scenario
On Apr 30, 4:31 am, Ernesto wrote:
> Hi guys thx for the responses
>
> @Brian
Hi guys thx for the responses
@Brian
i already have the "notEmptY" rule on each field. But the rule will
fail is the field is not set.
@starkey
overriding model::save doesn't sound cake-ish to me... imo a custom
validation rule will be more coherent
@jstein
thx for the hint
On 30 Apr, 01:54, b
I assumed the 'required'=>true was obvious, given the parameters
mentioned. I should have mentioned that, also.
On Wed, Apr 29, 2009 at 6:27 PM, jstein wrote:
>
> On Apr 29, 6:00 pm, brian wrote:
>> Just use a rule (eg. notEmpty) for each of them. You'll get errors for
>> whichever fields were
On Apr 29, 6:00 pm, brian wrote:
> Just use a rule (eg. notEmpty) for each of them. You'll get errors for
> whichever fields were not set.
No, "notEmpty" will fail validation, if the field is present but
empty. It will NOT fail, if the field is not set at all.
If the field MUST be set, use 'req
In your model you can override the save() method to check if all
fields are empty. If they are then ignore the record. If one or more
are set then call parent::save()... using the validation rule Brian
mentioned.
On Apr 29, 9:43 am, Ernesto wrote:
> Hello.
>
> I have a model with 5 fields
>
>
Just use a rule (eg. notEmpty) for each of them. You'll get errors for
whichever fields were not set.
On Wed, Apr 29, 2009 at 9:43 AM, Ernesto wrote:
>
> Hello.
>
> I have a model with 5 fields
>
> model_id
> parameter_A
> parameter_B
> parameter_C
> parameter_D
>
> if none of them are set -> th
