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, ...): > > username = username.lower() > > The problem here is that that even if 'Charlie' and 'charlie' cannot > exist as usernames concurrently, 'Charlie' still can if he gets there > first. So if that were the case and I had '/Charlie/' and passed > username.lower() to `widgets = > Widget.objects.get(owner__username=username), it is going to look for > charlie and won't find it. At least I am pretty sure that happened to > me last evening when I was trying this, though it was pretty late...
Hey Jonathan, 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. I *think* that: Widget.objects.get(owner__username__iexact='charlie') would get Charlie, charlie, or any other case variation... That way you could also the original username value in the template, complete with capitalization. Colin --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
