django-cte

• BREAKING: on Django 5.2 and later when joining a CTE to a queryset with LEFT OUTER JOIN (_join_type=LOUTER) and the join condition implicitly joins a related table, the implicit join is now a LEFT OUTER JOIN instead of an INNER JOIN. This makes the join behavior match SQL database semantics: the left-side rows are always preserved. To restore the old behavior, either do not use _join_type=LOUTER or add extra WHERE conditions as needed. See #130 for more details.
• Fixed CTE.queryset() queries involving aggregates (#128).
• Fixed Django 5.2 ambiguous column names bug (#127).
• Fixed possible ambiguous column names in SQL (#125).
• Fixed Django 5.2 CTE.queryset() regression (#124).

• API overhaul
  • With has been renamed to CTE. With is deprecated and will be removed in a future version of django-cte.
  • with_cte was moved from a CTEQuerySet method to a stand-alone function.
  • CTEManager and CTEQuerySet are deprecated and should be removed from code that uses them, as they are no longer necessary. They will be removed in a future version of django-cte.
  • Reference the documentation for new usage patterns.
• BREAKING: On Django 5.2 and later, the name specified in .values('fk_name') must match the name of the same column referenced by cte.col.fk_name—for example, in a join condition. It may end with _id or not, but the references must be consistent. This change may require previously working CTE queries to be adjusted when migrating to Django 5.2 (example).
• Django 5.0 is EOL and no longer supported.
• Fixed broken UNION and other "combined" queries.
• Internally, the library has been updated to simplify the code and remove workarounds for old and unsupported versions of Django.
• Modernized development tooling
  • Replaced nosetests with pytest.
  • Replaced setup.py with pyproject.toml
  • Replaced flake8 with ruff.
  • Replaced venv/pip with uv.
  • Improved Github Actions automation, including automated releases.
  • Dev versions of django-cte are now published on PyPI, making them easier to test and use before an official release is cut.

Prepare for v1.3.3 release

Prepare for 1.3.2 release

Prepare for v1.3.1 release

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

Bump version to 1.2.1 for new release

Prepare for 1.2.0 release

• Django 3 compatibility. Thank you @tim-schilling and @ryanhiebert!

• Python 3 compatibility.

• Fix CTE alias bug.

• Use _default_manager instead of objects.

• Fix recursive CTE pickling. Note: this is currently broken on Django master.

• With.queryset() now uses the CTE model's manager to create a new QuerySet, which makes it easier to work with custom QuerySet classes.

• BACKWARD INCOMPATIBLE CHANGE: With.queryset() no longer accepts a model argument.
• Improve With.queryset() to select directly from the CTE rather than joining to anoter QuerySet.
• Refactor With.join() to use real JOIN clause.

• Fix related field attname masking CTE column.

• Add django_cte.raw.raw_cte_sql for constructing CTEs with raw SQL.

• Improve error on bad recursive reference.
• Add more tests.
• Add change log.
• Improve README.
• PEP-8 style fixes.

• Fix readme formatting on PyPI.

• Initial implementation.