> (Now that I think of it, I'm somewhat surprised that Django's
> contrib.auth allows mixed case usernames. Quickly scanning through it,
> all examples seem to use all lower-case anyway.)
Surprised me too, but I'm not a real web developer (I pay the bills by
translating technical literature) so
> Using the "iexact" option would fix this case. Take a look
> at:http://www.djangobook.com/en/1.0/appendixC/
> towards the bottom, in the Field Lookups section.
Yes, this is what I meant by "filter with case-insensitive queries
whenever the username is URL param" -- I just couldn't remember
> You've understood me perfectly. I was just being picky. I would
> *like* to preserve the option of cased usernames, but if wikimedia
> doesn't fuss with it, why should I? I'll just add a clean_username
> method to the registration form that .lower() 's the name entered as
> suggested.
>
On Fri, Mar 28, 2008 at 10:02 AM, Jonathan Lukens
<[EMAIL PROTECTED]> wrote:
>
> Hi Evert,
>
>
> > > 2) Validate new usernames for case-insensitive uniqueness and filter
> > > with case-insensitive queries whenever the username is URL param.
>
>
> > def view(request, username, child=None,
You've understood me perfectly. I was just being picky. I would
*like* to preserve the option of cased usernames, but if wikimedia
doesn't fuss with it, why should I? I'll just add a clean_username
method to the registration form that .lower() 's the name entered as
suggested.
Thank you for
>>> 2) Validate new usernames for case-insensitive uniqueness and filter
>>> with case-insensitive queries whenever the username is URL param.
>
>> def view(request, username, child=None, ...):
>> username = username.lower()
>
> The problem here is that that even if 'Charlie' and 'charlie'
Hi Evert,
> > 2) Validate new usernames for case-insensitive uniqueness and filter
> > with case-insensitive queries whenever the username is URL param.
> def view(request, username, child=None, ...):
>username = username.lower()
The problem here is that that even if 'Charlie' and
> I am writing an application that involves a number of nested parent-
> child relationships, where users create objects that each in turn have
> sub-objects. So far the URL structure looks like this:
>
> example.com/username/
> example.com/username/child1/, example.com/username/child2/
>
I am writing an application that involves a number of nested parent-
child relationships, where users create objects that each in turn have
sub-objects. So far the URL structure looks like this:
example.com/username/
example.com/username/child1/, example.com/username/child2/
9 matches
Mail list logo
