#2638: default ForeignKey field results in terrible scaling perfomance
---------------------------+------------------------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  adrian
     Type:  defect         |       Status:  new   
 Priority:  normal         |    Milestone:        
Component:  Validators     |      Version:  0.95  
 Severity:  critical       |   Resolution:        
 Keywords:                 |  
---------------------------+------------------------------------------------
Comment (by Karen Tracey <[EMAIL PROTECTED]>):

 Yes, I think I've run into this also.  I actually thought it was this
 problem (list_display containing !ForeignKey create a dead loop):
 
 http://groups.google.com/group/django-
 
users/browse_thread/thread/1d73cec767f42c38/84538ca609dceee2?lnk=gst&q=infinite+loop&rnum=1
 
 but in my case I didn't have a loop in my !ForeignKey relations, just over
 100,000 potential values for the !ForeignKey field.  Trying to turn on
 edit_inline in the admin for a model that pointed to one of these things
 via !ForeignKey resulted in what appeared to be an infinite loop.  I only
 realized later that the problem was some code in admin was trying to
 populate a list of choices for these things, which isn't feasible for my
 DB.  Malcolm alerted me that he thought I would also hit the problem
 outside of admin if I just tried to create a manipulator for form
 processing, but since I haven't gotten to needing to do that yet and I
 don't need the edit_inline functionality, I hadn't gotten around to
 worrying about/investigating that yet.  I'm glad to hear there is already
 a way to turn this behavior off; for my DB it would be better if "off" was
 the default.
 
 Just figured I'd mention that I did run afoul of this, in case it
 influences what you decide to do with it.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2638>
Django <http://code.djangoproject.org/>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to