Good morning,

On 4/25/06, Michael Radziej <[EMAIL PROTECTED]> wrote:

I don't know what you mean with "stop". I think each validator will be
executed, but they will take into account whether record_type has the
right value.

Anyway, I personally give up :-(

You can try to find out what's happening:

- create your own validator that always raises a ValidationError (see in
the sources for core.validators to see how)
- add this to your validator list
- do you get a validation message?

yes but only if I allow the field to be blank.
 
  - else, change the source of core.validators in Django; raise
Blablabla in the __call__() method. Do you get the error message?

yes, because I finally found out what the main problem was:

I specified the value to be 2 while it really is "2". As far as scripting languages go, I'm coming from Perl and didn't even think about running into conversion problems. Anyway, I think it is documented that all values in validators are still strings so my bad.

Thanks a lot

chris

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to