#36466: Relax check E042 preventing including stored generated fields in
composite
primary keys
-------------------------------------+-------------------------------------
Reporter: David Sanders | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
Accepting on the basis that we should do something here.
Whether we should
1. Remove the check altogether for `GeneratedField`
2. Remove the check for `GeneratedField(db_persist=False)`
3. Add a feature flag `supports_stored_generated_field_pk` and base check
of it
is up for debate but given we have a whole section on _Database
limitations_ in the `GeneratedField` docs it seems like 1. is the option
that makes the most sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/36466#comment:2>
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/010701977c0a40a7-891921e2-93fe-4598-bd70-160df126aaa9-000000%40eu-central-1.amazonses.com.
