Debian Patches

Status for django-ldapdb/1.5.1-3

Patch Description Author Forwarded Bugs Origin Last update
0001-Use-_base_manager-instead-of-objects-when-modifying-.patch Use _base_manager instead of objects when modifying model
Guard against issues with a non-empty default QuerySet returned by
a Model's Manager instance by calling the Model's _base_manager when
doing lookups by dn. LDAP lookups by dn must be done by setting the dn
as the base of the LDAP query.

The current method for determining if a dn lookup is being requested
relies on inspecting the generated django.db.models.sql.query.Query and
looking for a 'dn' target column in the first where clause statement. If
a Model uses a custom Manager to append a where clause statement to all
QuerySets, this logic is broken. Using _base_manager instead of objects
as the Manager for constructing explicit dn lookups avoids this problem.
This behavior also matches the Django documentation and internals for
related object access, so it is likely to continue to work for the
foreseeable future.

Fixes #196
Bryan Davis <> not-needed 2019-07-17
0002-router-disallow-migrations-on-ldap-connection-and-mo.patch router: disallow migrations on ldap connection and models dzen <> not-needed 2020-10-13
0003-Use-get_attname-instead-of-attname-attribute.patch Use get_attname instead of attname attribute dzen <> not-needed 2021-04-13
0004-tests-add-missing-contribute_to_class-to-fully-insta.patch tests: add missing contribute_to_class to fully instantiate the field dzen <> not-needed 2021-04-13
0005-Update-regex-to-be-compatible-with-django-2-to-Djang.patch Update regex to be compatible with django 2 to Django 3.2 dzen <> not-needed 2021-04-13

All known versions for source package 'django-ldapdb'