Opened 7 years ago

Closed 7 years ago

Last modified 5 years ago

#12837 closed (fixed)

Clarify m2m intermediate table naming strategy

Reported by: Ramiro Morales Owned by: nobody
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Reports #12614 and #12810 hint about the fact the "By default, this table name is generated using the names of the two tables being joined." phrase at http://docs.djangoproject.com/en/dev/ref/models/fields/#id1 is creating confusion among users. We should change that to state the table is named after the model field names.

Attachments (1)

12837.diff (1.2 KB) - added by Ramiro Morales 7 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 7 years ago by Alex Gaynor

Triage Stage: UnreviewedAccepted

Changed 7 years ago by Ramiro Morales

Attachment: 12837.diff added

comment:2 Changed 7 years ago by Ramiro Morales

Has patch: set

comment:3 Changed 7 years ago by Tim Graham

Triage Stage: AcceptedReady for checkin

comment:4 Changed 7 years ago by Russell Keith-Magee

Resolution: fixed
Status: newclosed

(In [12516]) Fixed #12837 -- Clarified the naming strategy for m2m intermediate tables. Thanks to Ramiro Morales for the report and patch.

comment:5 Changed 7 years ago by Russell Keith-Magee

(In [12521]) [1.1.X] Fixed #12837 -- Clarified the naming strategy for m2m intermediate tables. Thanks to Ramiro Morales for the report and patch.

Backport of r12516 from trunk.

comment:6 Changed 5 years ago by Jacob

milestone: 1.2

Milestone 1.2 deleted

Note: See TracTickets for help on using tickets.
Back to Top