#35246: Make Field.unique a plain attribute
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Adam
Type: | Johnson
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 Natalia Bidart):
* stage: Unreviewed => Accepted
Comment:
I agree with Simon on both items, that this optimization can be helpful
and that we could use some metrics to do some follow up in the medium/long
term.
I just checked the branch and wonder if converting the property into a
cached one, instead of deleting it in favor of an attribute, might be a
better idea. I'm thinking of potential usages out there in the wild
overriding the property for <reasons> and the proposed change would break
those scenarios.
--
Ticket URL: <https://code.djangoproject.com/ticket/35246#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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018dd749e6f8-1d5be360-8787-44ce-a7cb-b280b5a748e4-000000%40eu-central-1.amazonses.com.
