Django-ordered-model

Latest version: v3.7.4

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

Scan your dependencies

Page 1 of 6

3.7.4

----------
- Relax Check for `OrderedModelManager` to a `Warning`, if the manager returns the correct queryset (290)

3.7.3

----------
- Restrict signal handler 'senders' to subclasses of `OrderedModelBase` to avoid query count regression due to `Collector.can_fast_delete` logic in `models/deletion.py` (288)
- Fix `reorder_model` management command re-ordering with multiple `order_with_respect_to` values

3.7.2

----------
- Fix a performance regression (unnecessary queries) in the WRT change detection (286)
- Add a Check that `order_with_respect_to` specifies only ForeignKey fields
- Add a Check that our subclasses of ModelManager and QuerySet are used (286)

3.7.1

----------

- Fix for `model.save()` falsely detecting WRT change from admin create since 3.7
- Cascaded deletes of `OrderedModel` instances now handled using signals (182)

3.7

----------

- Use bulk update method in `reorder_model` management command for performance (273)
- Add tox builder for python 3.10, use upstream DRF with upstream django
- Emit a system Check failure if a subclass of `OrderedModelBase` fails to specify `Meta.ordering`
- Updating the value of fields within `order_with_respect_to` now adjusts ordering accordingly (198)

3.6

----------

- Add `serializers.OrderedModelSerializer` to allow Django Rest Framework to re-order models (251 264)
- Add tox builder for Django 4.0, drop building against 2.0 and 2.1 due to DRF compatibility.

Page 1 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.