#15412: Custom SQL fixtures appear to be loaded in the wrong order.
--------------------------------------------------------+-------------------
               Reporter:  al_the_x                      |         Owner:  
nobody     
                 Status:  closed                        |     Milestone:        
     
              Component:  Database layer (models, ORM)  |       Version:  1.2   
     
             Resolution:  wontfix                       |      Keywords:  sql 
fixture
           Triage Stage:  Unreviewed                    |     Has patch:  0     
     
    Needs documentation:  0                             |   Needs tests:  0     
     
Patch needs improvement:  0                             |  
--------------------------------------------------------+-------------------
Changes (by russellm):

  * status:  new => closed
  * needs_docs:  => 0
  * resolution:  => wontfix
  * needs_tests:  => 0
  * needs_better_patch:  => 0


Comment:

 The order is undesirable *for you*. The other order is just as desirable
 under different circumstances. For example, if you have some unusual table
 requirements, you may need to do some db-specific ALTER TABLE statements
 before you do some generic data loading. That's a fairly simple example
 that demonstrates that the current order is "correct".

 In addition, loading of data via SQL is something that we're trying to
 discourage; the preferred approach is to use fixtures.

 Given that Django (a) has a preferred solution that avoids the problem you
 describe, and (b) can't fix the problem you describe in a generic way
 without allowing for multiple custom SQL entry points (i.e., a pre-generic
 and post-generic SQL hook, which itself would need pre-specific and post-
 specific hooks, and so on...), I'm going to close this wontfix. If you
 feel there is a broader issue that needs to be addressed, feel free to
 start a discussion on Django-dev.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/15412#comment:1>
Django <http://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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to