#30435: __iexact NOT WORKING. URGENT!!!!!!!!!!!!!!!!!!!!!!! -------------------------------------+------------------------------------- Reporter: Diego Arturo | Owner: nobody Hernandez Fuentes | Type: Bug | Status: new Component: Uncategorized | Version: 2.1 Severity: Normal | Resolution: Keywords: | Triage Stage: | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Ryan Govostes): You are raising your ValidationError inside a `try ... catch` block which catches the exception and then does nothing with it. This will prevent the ValidationError from escaping your validator. Does this work? {{{ def validate_name(self, value): if not value: raise serializers.ValidationError('Proporciona un valor, por favor.') exist_name = FundingSource.objects.filter(name__iexact=value) if len(exist_name) > 0: raise serializers.ValidationError('Este nombre ya fue usado, por favor proporciona otro valor.') }}} Please keep bug report titles simple. -- Ticket URL: <https://code.djangoproject.com/ticket/30435#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/069.f59728be271dd7d86a03f70ec74a907c%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.