Opened 10 years ago
Closed 10 years ago
#23509 closed Cleanup/optimization (duplicate)
Clarity: Release Notes regarding initial_data
| Reported by: | Aryeh Hillman | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.7 |
| Severity: | Normal | Keywords: | fixtures intial_data migrations runpython runsql |
| Cc: | no, one | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
When migrations are created in Django 1.7, the fixtures are ignored. This is a perfectly fine decision, but many users (such as myself) still need fixture-like functionality. That functionality is provided by RunPython or RunSQL within a migration. While the release notes correctly indicate that modifying/creating a migration can replace initial_data, they could be a little clearer, noting RunPython or RunSQL. For example:
"initial_data fixtures are no longer loaded for apps with migrations; if you want to load initial data for an app, we suggest you do it in a migration."
... could become
"initial_data fixtures are no longer loaded for apps with migrations; if you want to load initial data for an app, we suggest you create a migration for you application and define a RunPython or RunSQL command in the operations section of the migration."
That could be immensely helpful for pointing users in the right direction, especially if they are eager to quickly get django 1.7 up and running... whilst maintaining fixture-like functionality.
Duplicate submit of #23512.