#32234: Add warning when multiple-column primary keys are found when using
inspectdb
-------------------------------------+-------------------------------------
Reporter: Damien | Owner: Damien
Type: New feature | Status: assigned
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => assigned
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* easy: 1 => 0
* owner: nobody => Damien
* has_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
`inspectdb` is meant as a shortcut, not as definitive model generation. I
would rather add a comment to the field's `notes` like we do in other
cases. Raising a warning can be really annoying when you try to inspect a
legacy database.
--
Ticket URL: <https://code.djangoproject.com/ticket/32234#comment:1>
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/065.aa99ab789efd67c0a2397042ef14080a%40djangoproject.com.
