#2225: 'manage.py sql ...' gets confused when using tables from separate apps
---------------------------------------------------+------------------------
          Reporter:  Lucas Hazel                   |         Owner:  nobody
            Status:  new                           |     Milestone:        
         Component:  Database layer (models, ORM)  |       Version:  SVN   
        Resolution:                                |      Keywords:        
             Stage:  Accepted                      |     Has_patch:  1     
        Needs_docs:  1                             |   Needs_tests:  1     
Needs_better_patch:  1                             |  
---------------------------------------------------+------------------------
Changes (by glassresistor):

  * owner:  glassresistor => nobody
  * needs_better_patch:  0 => 1
  * has_patch:  0 => 1
  * needs_tests:  0 => 1
  * needs_docs:  0 => 1

Comment:

 To fix this problem I had to create a new BaseCommand extension so that
 unlike AppCommand CrossAppCommand looks at all of the models in the
 project so the table references across multiple apps will have sane
 outputs which can be piped into an sql database.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2225#comment:7>
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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.


Reply via email to