Django-cte

Latest version: v1.3.3

Safety actively analyzes 675388 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

1.3.3

- Handle empty result sets in CTEs ([92](https://github.com/dimagi/django-cte/pull/92)).
- Fix `.explain()` in Django >= 4.0 ([91](https://github.com/dimagi/django-cte/pull/91)).
- Fixed bug in deferred loading ([90](https://github.com/dimagi/django-cte/pull/90)).

1.3.2

- Work around changes in Django 4.2 that broke CTE queries due to internally
generated column aliases in the query compiler. The workaround is not always
effective. Some queries will produce mal-formed SQL. For example, CTE queries
with window functions.

1.3.1

- Fix: `.update()` did not work when using CTE manager or when accessing nested
tables.

1.3.0

- Add support for Materialized CTEs.
- Fix: add EXPLAIN clause in correct position when using `.explain()` method.

1.2.1

- Fix compatibility with non-CTE models.

1.2.0

- Add support for Django 3.1, 3.2 and 4.0.
- Quote the CTE table name if needed.
- Resolve `OuterRef` in CTE `Subquery`.
- Fix default `CTEManager` so it can use `from_queryset` corectly.
- Fix for Django 3.0.5+.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.