I tried out the newforms-admin branch for my app today. The conversion went fine, except for a performance problem with the new raw_id_fields. As background, I have a model with two ForeignKey fields (among other stuff). The number of choices for those ForeignKey fields is high (over 100,000 for one of them). In the old admin, I specified raw_id_admin=True on those fields in the model, and all was well (not pretty, but usable). In the new admin, I included these fields in raw_id_fields for the associated ModelAdmin object. I know I specified it correctly because on the change form for the model these two fields are displayed "raw-ly". However, the change page for an instance of this model takes minutes to display. Tracing through the code a little I can see that for each of these fields a list of all possible values is getting generated when the model's ChangeManipulator is created. That's exactly what I was using raw_id_admin in the old version to prevent, because it takes too long. The replacement raw_id_fields isn't avoiding that -- it's just suppressing the inclusion of a humongous drop-down list on the change form.
Is there some way I've overlooked in the new admin to avoid the overhead of generating the choices list for a field listed in raw_id_fields? If not, is this a known problem that will be addressed before newforms-admin gets merged back to trunk (I did search in trac, but didn't find anything)? If not, should I open a ticket? Thanks, Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
