#36665: Rewrite reference to model manager usage to avoid saying "tricky"
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Segni
Type: | Mekonnen
Cleanup/optimization | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Segni Mekonnen):
* has_patch: 0 => 1
* owner: (none) => Segni Mekonnen
* status: new => assigned
Comment:
Working on this ticket. Will submit PR shortly.
This ticket asks to replace vague "tricky" language with specific examples
of when managers are not used. Planning to provide concrete examples like
instance access (raises AttributeError) and related field access that may
bypass custom manager methods.
--
Ticket URL: <https://code.djangoproject.com/ticket/36665#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199e4bfd1b0-583737c3-ce34-4d76-bff9-70627bc29505-000000%40eu-central-1.amazonses.com.
