#10243: to_field option problems in admin site
---------------------------------------------------+------------------------
          Reporter:  tsawyer                       |         Owner:  mtredinnick
            Status:  assigned                      |     Milestone:  1.1        
         Component:  Database layer (models, ORM)  |       Version:  SVN        
        Resolution:                                |      Keywords:  to_field   
             Stage:  Accepted                      |     Has_patch:  0          
        Needs_docs:  0                             |   Needs_tests:  0          
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Changes (by mtredinnick):

  * owner:  nobody => mtredinnick
  * status:  new => assigned
  * component:  django.contrib.admin => Database layer (models, ORM)

Comment:

 This is reporting two different bugs in one. Reducing the example to
 something a lot simpler (no `db_columns`, etc) shows things a bit more
 easily. The extra row in the inline forms is #8903.

 The other problem turns out to be a bug that's been in the related fields
 code for, literally, years. I'm working on it.

 (Also, this bug has nothing to do with #9994 -- that ticket was much
 easier and not about the same thing, as it turned out.)

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10243#comment:5>
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