> In the Admin UI it could look like this: [Select State] --[Select County] ----[Select Zip]
I think situations like this are handled better on the server side anyway. A list containing ~100 items or less is appropriate in most cases, but there is a pretty good chance you would exceed this even with the filtering idea you are proposing. What you should ideally use when you are dealing with so many rows is something that filters information before it leaves the server. An example (that won't work exactly in your particular case) is the way raw_id_admin works in the admin. It paginates to 100 items by default, and can filter even more with list_display/search_fields options. It would work even better with some more javascript (e.g. to automatically fill in the field when adding a new item, change the repr() string on the fly, and allow modification of a foreign key entry), but the concept is good and you certainly can't complain about the price. My 2c: as for the exact example you have given, I don't think even selecting zip codes is appropriate in a form. Seems very tedious to select one from a list when it is only five (+4) simple numbers to type! If your goal is validation, that can be done server-side. If your goal is ease of use, stick with a text field. -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
