Wouldn't it be possible to implement case-insensitive usernames without
loosing backwards compatibility, by checking the username iexact and only
if there are multiple possibilities fall back to the old case-sensitive
variant?
So something like this:
diff --git
Hello David,
Is it possible to try to use it as part of the Django fork you mention,
instead of the app ?
I couldn't find any link on your github profile, your website and google
but perhaps I've missed it.
Thanks !
Best
<3
--
You received this message because you are subscribed to the
Ooops yes this is correct, it doesn't work in the advised file, apps.py
Thank you so much for your feedback, I need to ditch this patch just
find a way to make Django default usable date, time, image, relations
form fields useable ootb by marrying a JS framework.
Best
<3
--
You received this
>
> About 1, if it's already working with a non-signal, how could it not work
> with a signal ? It is, after all, called from within formfield() in this
> implementation, so anything that's working today when formfield() is
> called, should work when formfield() emits a signal.
>
Signal handlers
Hello Tom,
Thanks for working on adding filter support to aggregate. I think adding
support for the SQL:2003 features on all aggregates by emulating it on
backends that don't support it using CASE makes a lot of sense[0].
As I've mentioned on your PR this is syntactic sugar I've been missing
hello i have create a select django form with list of images for per user.
How to take that select request in my views.py ?
i have success only to create correct that select list but i need take that
select request but i dont know how.
models.py
class MyModel(models.Model):
user =
Hi Xristos,
This mailinglist is for developing the django framework itself, not for
getting help with your code. If you need help with your code please see the
Django Users group:
https://docs.djangoproject.com/en/dev/internals/mailing-lists/
--
Jeremy Spencer
www.jeremyspencer.me
