#32234: inspectdb should inform about composite keys.
-------------------------------------+-------------------------------------
Reporter: Damien | Owner: Anvesh
Type: | Mishra
Cleanup/optimization | Status: closed
Component: Core (Management | Version: 3.1
commands) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by nessita <124304+nessita@…>):
In [changeset:"4c75858135589f3a00e32eb4d476074536371a32" 4c758581]:
{{{#!CommitTicketReference repository=""
revision="4c75858135589f3a00e32eb4d476074536371a32"
Refs #36052, #32234 -- Removed
create_test_table_with_composite_primary_key flag in favor of using
CompositePrimaryKey.
Now that Django properly supports creating models with composite primary
keys, the tests should use a `CompositePrimaryKey` field instead of a
feature flag to inline backend specific SQL for creating a composite PK.
Specifcially, the inspectdb's test_composite_primary_key was adjusted to
use schema editor instead of per-backend raw SQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32234#comment:13>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019686f7e203-1d6f1d1f-0fbd-426f-b069-c39a4109ec6e-000000%40eu-central-1.amazonses.com.
