On Mon, Mar 18, 2013 at 5:49 AM, fire_water wrote:
> Hello,
>
> I am fairly new to Django but have started developing my first app. The
> app will require the general public to create an account before being
> allowed to post comments on the website.
>
> After reading through The Django
> Book
Why is anyone shocked that the print version of the book would have an
error?
--~--~-~--~~~---~--~~
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
T
a project?
Mat
-Original Message-
From: django-users@googlegroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of James Bennett
Sent: 01 April 2008 21:47
To: django-users@googlegroups.com
Subject: Re: Auth System
On Tue, Apr 1, 2008 at 3:38 PM, Mat <[EMAIL PROTECTED]> wrote:
> I
On Tue, Apr 1, 2008 at 3:38 PM, Mat <[EMAIL PROTECTED]> wrote:
> I'm looking at django for a new project, and have a quick question, I'm
> going to need a mixture of the Query-set branch and generic-auth branch, I
> really need object based permissions, but it seems like generic-auth was
> las
On Aug 6, 4:55 pm, LaundroMat <[EMAIL PROTECTED]> 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 wit
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 Mohorov
i'm checking username and email because i want to avoid situations
where some user registers with same email using different username.
Aljosa
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
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 th
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 <[EMAIL PROTECTED]>
wrote:
> i'm currently looking at django.contrib.auth a
9 matches
Mail list logo