I would like to try again:
I believe having a general setting for autofields could cause all
sorts of issues. As illustrated, I immediately thought that some
people might want to use that for migrating to UUID fields for that (I
read about using them somewhere about when I started using Django 5
ye
Hello everyone.
So far, I've managed to implement joins via Subquery and OuterRef with some
caveats.
To begin with, the API looks like this
Product.objects.create(name='Pizza', country='USA', type='FOOD')
Tax.objects.create(name='USA Food Tax', amount=10, product_country='USA',
product_type='FO
Hrm. Thanks for the link... probably not going to end up being a Django
issue. I will report back if it is.
On Sunday, April 12, 2020 at 10:25:07 AM UTC-4, Tim Graham wrote:
>
> The relevant commit might be
> https://github.com/django/django/commit/10b44e45256ddda4258ae032b8d4725a3e3284e6.
>
Hi all,
I would like to continue the discussion started in this very old thread:
https://groups.google.com/d/msg/django-developers/H2QFcQYsbo8/RmRb-8FVypwJ
I’m sorry if I should've continued the discussion in that thread but it
felt a bit wrong to bring a 5 year old thread back to life :-)
Any
The relevant commit might be
https://github.com/django/django/commit/10b44e45256ddda4258ae032b8d4725a3e3284e6.
That change was made in Django 2.1. You didn't say what version of Django
you're using.
You'll have to give more details about your case and what's behaving
differently.
On Sunday,
Why was the error log removed from handle_uncaught_exception? I didn't
find mention about it but I've recently encountered a middleware causing a
500 error and not getting a traceback log was unexpected.
https://github.com/django/django/blob/stable/2.0.x/django/core/handlers/exception.py#L115
