I tried this in the user's list, but it didn't get any interest. Use of the django default forms routines form_for_model, form_for_instance on a model that has a foreign key that references a table with a large number (many thousands) of rows results in two problems. One, you get an appreciable (5 seconds on a local network using postgres and apache) delay while the list is populated and rendered. Two, the list is not very easy to use. This has been discussed in this list before, but no one really seems to believe it is a problem. One reply was that the list should be categorized to cut it down - not a very scalable solution. Such foreign keys must be very common, surely every large company address book must contain thousands of entries. These default routines are so useful that it seems a shame to not provide some way of suppressing/delaying the population of what can be a very large drop down list. I know this is done in admin using raw_id, but admin is not always appropriate.
Paul Hide --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
