I agree with Mariusz.
Moreover, the app directories loader class is really small. You can create
a project-specific version in 3 lines, if you need:
class Loader(FilesystemLoader):
def get_dirs(self):
return get_app_template_dirs("email-templates")
On Tue, May 10, 2022 at 6:27 AM Mar
Hi all.
Time to begin release process for the next major release, Django 4.1!
It's been an incredible cycle with (again) a staggering number of
contributions. Thank you everyone!
The 4.1 feature freeze is scheduled (according to
https://code.djangoproject.com/wiki/Version4.1Roadmap) for Tues
Hello everyone,
I'm often using django-cte and I'd be thrilled to have CTE in the core.
If I'm not mistaken, the only DB currently supported by Django and not
having CTE support is MySQL 5.7 (with an end of life in October 2023). I
don't know if Django 4.2 will support it, but it should be drop
I will always suggest that we use the Subquery API to make CTEs. To make them
recursive, just add a keyword argument (recursive=True) and/or use a union.
It’s been a while since I looked at CTEs, so I might be missing something.
I would hate to see us create an entirely separate API for CTEs.
As far as I know, CTE and subquery are equivalent when used only in a
single place in the query.
CTE should be better when a single query is used several times.
If we want to reuse the Subquery API, we should find a way to be able to
reuse a subquery (hash its content and use that as a key to d
Hi.
Why we don't have __eq__ for QuerySets, here is an example:
```
qs1 = Model.objects.all()
qs2 = qs1.all()
qs1 == qs2
```
output: False
as we know these two are the same by value!
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions t
I am not Agree.
qs1.all() it is copy from qs1, the new object.
I already try to write QuerySet compare on the Django 1.4 and i remember,
that str(qs1.query) can be different as str(qs2.query), I am not Shure.
Mit freundlichen Grüßen,
DI Mag. Maxim Danilov
+43(681)207 447 76