#23513: Fixtures/initial_data Clarification in Release Notes for django 1.7
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  nobody
  abhillman              |     Status:  new
         Type:           |    Version:  1.7
  Uncategorized          |   Keywords:  runpython runsql documentation
    Component:           |  migrations initial_data
  Documentation          |  Has patch:  0
     Severity:  Normal   |      UI/UX:  0
 Triage Stage:           |
  Unreviewed             |
Easy pickings:  1        |
-------------------------+-------------------------------------------------
 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.

--
Ticket URL: <https://code.djangoproject.com/ticket/23513>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.fa40e9d4e09ba4384975238b1a5e1e86%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to