Thanks Brian, One more question, there is another way to write a custom validator without override the field type?
Nuno On May 9, 5:30 pm, Brian Rosner <[EMAIL PROTECTED]> wrote: > On May 9, 4:31 am, Nuno Mariz <[EMAIL PROTECTED]> wrote: > > > I'm using newforms-admin and I've got a "duplicate key violates unique > > constraint" when I'm added new record(with the same value on field > > that already exists in the db) in admin interface. > > I've an "unique=True" in the field, shouldn't admin interface shows a > > error message in the form and not raise a IntegrityError exception? > > Not yet. Similar to a ModelForm it does not do any model level > validation. This functionality is on its way. This has become aparent > because the newforms-admin branch now uses newforms to deal with forms > which brings any problems newforms has. This can be avoided by writing > your own custom validation in your own ModelForm and use it in the > ModelAdmin, but nothing will be default until model aware validation > lands. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
