On 6 Sep 2007, at 9:21 pm, RajeshD wrote:
> You can always turn the queryset into a list and cache it with > Django's caching framework. However, that doesn't solve the usability > issue of a huge drop-down list. A few options: > > 1. Do what the Django raw_id_admin interface does (http:// > www.djangoproject.com/documentation/model-api/#many-to-one- > relationships). > It uses a popup-window in which the user sees the set of available > options (they could be paginated if it's a big list); clicking a row > results in its pk being fed back to the parent field being selected. > > 2. ExtJS (and possible other Javascript) libraries provide fancy AJAX > based interfaces that let you load a custom drop down list on demand > as the user scrolls down. I never actually mentioned it being a drop down, it's actually going to be checkboxes and also the actual dataset won't be that big. It'll be a distinct query on a huge set of data and I don't want that huge hit every time someone loads the form. I think I'll go for the caching idea, as you suggested. Thanks, David -- David Reynolds [EMAIL PROTECTED] -- David Reynolds [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
