#373: Add support for multiple-column primary keys
-------------------------------------+-------------------------------------
Reporter: Jacob | Owner: Clouds
Type: New feature | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: database | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Clouds):
Hello, the main work of CompoisteField has been done and I'm now working
on `primary_together`/`PrimaryKeyConstraint`.
While I've got several questions:
1. How to write test for migration? (or witch existing test as example)
a. test if the model generating correct models.State
b. test if from OldModel to NewModel would success migrated
2. Shall we have PrimaryKeyConstraint and CompositeField in one PR?
a. primary (without multicolumn) first, then composite
b. composite (cannot set as PK) first, then primary
The main blocker split it into 2 PR might be hard to add meaningful tests
in first PR.
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:157>
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/0107018364d84469-b3955cf4-9498-4583-a141-bfd8801c21c0-000000%40eu-central-1.amazonses.com.
