auth system - check if user already exists

[Aljosa Mohorovic]

i'm currently looking at django.contrib.auth and wondering what is the
correct way to check if user already exists?
before i call User.objects.create_user() i want to know that user with
submitted username and email doesn't exist.
my current situation is that i call
User.objects.get(username__exact=user) and
User.objects.get(email__exact=email) and if i get exception
"DoesNotExist: User matching query does not exist." and i assume that
it's ok to create new user.

i'm sure there is a better way to check if user with submitted
username or email already exists, please share your ways...

Aljosa

[Poromenos]

That's what I do (well, I just check the username, since I can't think
why you'd want to check the email). I don't think there's a better
way, it's pretty straightforward...

Poromenos

On Aug 6, 12:42 am, Aljosa Mohorovic <aljosa.mohoro...@gmail.com>
wrote:

[LaundroMat]

Of the top of my head, but would the following be helpful?
user, new = User.objects.get_or_create(username = user, email =
email)

The function returns either:
- a new user object and True if the user didn't exist yet (and had to
be created);
- an object with existing user data and False.

Mind that you still have to call user.save() in case of a new user.

On Aug 5, 11:42 pm, Aljosa Mohorovic <aljosa.mohoro...@gmail.com>
wrote:

[Aljosa Mohorovic]

i'm checking username and email because i want to avoid situations
where some user registers with same email using different username.

Aljosa

[LaundroMat]

Are you sure you want to avoid that? I remember somebody here linking
to an article where this wasn't advised, because it's (apparently)
quite common for members of the same household to register with the
same e-mail address (but with another username ofcourse).

On Aug 6, 12:02 pm, Aljosa Mohorovic <aljosa.mohoro...@gmail.com>
wrote:

[Aljosa Mohorovic]

On Aug 6, 4:55 pm, LaundroMat <Laun...@gmail.com> wrote:
> Are you sure you want to avoid that? I remember somebody here linking
> to an article where this wasn't advised, because it's (apparently)
> quite common for members of the same household to register with the
> same e-mail address (but with another username ofcourse).

good point but in my situation users will mostly be companies so i
want to ensure that nobody with same email registers twice.

Aljosa