Django-tree-queries

Latest version: v0.18.0

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

Scan your dependencies

Page 1 of 3

0.18

~~~~~~~~~~~~~~~~~

- Fixed broken SQL which was generated when using a tree query with
``EXISTS()`` subqueries.

0.17

~~~~~~~~~~~~~~~~~

- Preserved the tree ordering even when using ``.values()`` or
``.values_list()``. Thanks Glenn Matthews!
- Added support for descending sibling ordering, multi-field sibling ordering,
and related field sibling ordering. Thanks rhomboss!

0.16

~~~~~~~~~~~~~~~~~

- Added Python 3.12, Django 5.0.
- Fixed a problem where ``.values()`` would return an incorrect mapping. Thanks
Glenn Matthews!
- Started running tests periodically to catch bugs earlier.

0.15

~~~~~~~~~~~~~~~~~

- Switched to ruff and hatchling.
- Dropped Django 4.0.
- Added Python 3.11.
- Added a ``.without_tree_fields()`` method which calls
``.with_tree_fields(False)`` in a way which doesn't trigger the flake8
boolean trap linter.

0.14

~~~~~~~~~~~~~~~~~~~~

.. _0.14: https://github.com/matthiask/django-tree-queries/compare/0.13...0.14

- Changed the behavior around sibling ordering to warn if using
``Meta.ordering`` where ordering contains more than one field.
- Added Django 4.2a1 to the CI.
- Django 5.0 will require Python 3.10 or better, pruned the CI jobs list.
- Added quoting to the field name for the ordering between siblings so that
fields named ``order`` can be used. Thanks Tao Bojlén!
- Narrowed exception catching when determining whether the ordering field is an
integer field or not. Thanks Tao Bojlén.

0.13

~~~~~~~~~~~~~~~~~~~~

.. _0.13: https://github.com/matthiask/django-tree-queries/compare/0.12...0.13

- Made it possible to use tree queries with multiple table inheritance. Thanks
Olivier Dalang for the testcases and the initial implementation!

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.