Re: Data::FormValidator and Either/Or Fields

Re-read the documentation on dependencies that should take of that part of your question. You can use constraints on any fields. So if the dependency is there it is validated and if incorrect then you get an error. If the dependency is not there the you also get an error.

I hope this is what you were asking for.

If this does not help then post the relevant code and I will try to do more for you.

-dwiz

Comment on Re: Data::FormValidator and Either/Or Fields

Replies are listed 'Best First'.
Re: Re: Data::FormValidator and Either/Or Fields by impossiblerobot (Deacon) on Jun 14, 2002 at 16:05 UTC
Dependencies (and Dependency Groups) constraint checking only kicks in when one of the dependent fields is present. It then requires that the other dependent fields are also present. My problem is just the opposite: determining that at least one of the fields is filled. In other words: `# Should be valid my %param = ( zip => '55555', postal => '',); # or my %param = ( zip => '', postal => '11111',); # Should not be valid my %param = ( zip => '', postal => '',);` [download] If I make both params required, then they're both always required, which is not what I want. If I make them optional, and add constraints to check that at least one has a value, the constraints are never checked, since the fields are empty. If I create dependencies, and add constraints to check that at least one has a value, the constraints are never checked, since none of the dependent fields exist. Thanks anyway for your help, and if you know of a way to do this that I've overlooked, please post. Impossible Robot	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Data::FormValidator and Either/Or Fields
by impossiblerobot (Deacon) on Jun 14, 2002 at 16:05 UTC

Dependencies (and Dependency Groups) constraint checking only kicks in when one of the dependent fields is present. It then requires that the other dependent fields are also present.

My problem is just the opposite: determining that at least one of the fields is filled. In other words:

# Should be valid
my %param = ( zip => '55555', postal => '',);
# or
my %param = ( zip => '', postal => '11111',);

# Should not be valid
my %param = ( zip => '', postal => '',);
[download]

If I make both params required, then they're both always required, which is not what I want.

If I make them optional, and add constraints to check that at least one has a value, the constraints are never checked, since the fields are empty.

If I create dependencies, and add constraints to check that at least one has a value, the constraints are never checked, since none of the dependent fields exist.

Thanks anyway for your help, and if you know of a way to do this that I've overlooked, please post.

Impossible Robot

[reply]
[d/l]