#2210: [patch] order_by on related table with db_column different to name fails
------------------------------------------------+---------------------------
   Reporter:  Russell Cloran <[EMAIL PROTECTED]>  |                Owner:  
adrian          
     Status:  new                               |            Component:  
Database wrapper
    Version:  SVN                               |           Resolution:         
         
   Keywords:  order_by related                  |                Stage:  
Unreviewed      
  Has_patch:  0                                 |           Needs_docs:  0      
         
Needs_tests:  0                                 |   Needs_better_patch:  0      
         
------------------------------------------------+---------------------------
Comment (by ramiro <rm0 _at_ gmx.net>):

 So, it seems the patch for #2076 also solves this ticket :-/
 
 Attached you will find a {{{models1.py}}}, it has some doctest
 ![1]testcases that reproduce the problem described by the original
 reporter. It should be installed as the {{{models.py}}} file of a
 {{{ticket2210}}} application.
 
 Also attached is a {{{models2.py}}}, it has the same ![1]testcases but
 using the {{{order_by}}} notation introduced by the patch for #2076 (so
 that patch should be applied first) and they complete without errors. It
 should be installed as the app {{{models.py}}} file.
 
 Apologies for the noise.
 
 1. Run them executing
 {{{
 $ ./manage.py test ticket2210
 }}}

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2210#comment:21>
Django Code <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