Thanx Siddharth and Pradeep, I will try both suggestion and let you know
On Thu, Apr 25, 2013 at 2:07 PM, Pradeep Kumar <[email protected]> wrote: > Hi Sachin, > > If you have added the unique=True later and migrated the existing table, I > would also suggest you to first clean up the NULL and duplicate entries > using a script or even from shell. > > After doing that you can use > * try: * > # your code here > * except IntegrityError: * > #create variables here to send user error message > > One more pointer - try checking for the user input( X.object.filter > method) in the unique fields in database before performing .save > > > On Thu, Apr 25, 2013 at 1:34 PM, Siddharth Ghumre < > [email protected]> wrote: > >> hi Sachin, >> >> Please use django's form clean method in order to validate your phone_num >> field. >> You can also override the django's clean method by using your own >> clean_phone_field method. >> Please refer the link:- >> >> https://docs.djangoproject.com/en/dev/ref/forms/validation/ >> >> I am sure that a small googling on overriding the clean method in django >> form class will defiantly help you. >> >> -Siddharth >> >> >> On Wed, Apr 24, 2013 at 8:57 PM, sachin <[email protected]> wrote: >> >>> Hello, >>> >>> I m extending my auth user model to add addition entries like phone >>> numbers and emp_id. In the model I m marking both the fields as unique=True. >>> Form generation is using UserCreationForm. But whenever I try to save >>> same phone number or emp_id it throws >>> >>> *IntegrityError: (1062, "Duplicate entry '447' for key 'phone_num'")* >>> >>> How to handle this error and show it to user during form input? >>> >>> Also how do the same UserCreationForm validates duplicate entry for >>> username etc ?? >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/django-users?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/django-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-users/EaYF9DEptLo/unsubscribe?hl=en > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Sachin -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
