Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#26078 closed Cleanup/optimization (fixed)

Docs: DB Meta Migration Guildlines: More explicit "old" vs "new"

Reported by: Thomas Güttler Owned by: nobody
Component: Documentation Version: 1.9
Severity: Normal Keywords:
Cc: tzanke@… Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no

Description

On this page ​https://docs.djangoproject.com/en/1.9/ref/models/meta/
you easily missunderstand the examples provided below "MyModel._meta.get_fields_with_model():".

I team mate and I just read the source, and not the string above "These old APIs can be replicated by either:".

I will provide a pull request to make this more clear.

Change History (5)

comment:1 by Thomas Güttler, 10 years ago

Here is the pull request for meta.txt
​https://github.com/django/django/pull/5978

comment:2 by Tim Graham, 10 years ago

Has patch: set
Patch needs improvement: set
Triage Stage: Unreviewed → Accepted
Type: Uncategorized → Cleanup/optimization

comment:3 by Tim Graham <timograham@…>, 10 years ago

Resolution: → fixed
Status: new → closed

In 28acc0d:

Fixed #26078 -- Clarified "old vs. new" in model._meta upgrade guide.

Thanks Thomas Güttler for the suggestion.

comment:4 by Tim Graham <timograham@…>, 10 years ago

In f619b728:

[1.9.x] Fixed #26078 -- Clarified "old vs. new" in model._meta upgrade guide.

Thanks Thomas Güttler for the suggestion.

Backport of 28acc0d6df844ccfc8de6f4e7d5883eb4841e946 from master

comment:5 by TZanke, 10 years ago

Cc: tzanke@… added
Note: See TracTickets for help on using tickets.
Back to Top