Home/ Questions/Q 7630985
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T06:14:14+00:00

from django.contrib.auth.models import User a = User.objects.create_user(1,2,3) b = User.objects.create_user(1,2,3) no errors yet… a.validate_unique()

  • 0
from django.contrib.auth.models import User

a = User.objects.create_user("1","2","3")
b = User.objects.create_user("1","2","3")

no errors yet…

a.validate_unique()
ValidationError: {'username': [u'User with this Username already exists.']}

I would expect to receive the validation error when b was being saved as part of create_user.

Looking at the Django Model Instance Reference, the ‘what happens when you save’ section does not describe saving at any point.

Is this an intentional design decision or a side-effect due to using django-nonrel? I would have expected a relational database to return an IntegrityError or something similar.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You might be using SQLite, which does not support unique key constraints.

    create_user assumes you’ve done all the needed checking, usually in a form’s validation functions. It gives you quite enough rope to hang yourself with.

    • 0