On Mon, Dec 10, 2018 at 6:29 AM John Lehmann <john.lehm...@gmail.com> wrote:
> So my takeaway from what you are saying is that no one is running a > production site with a Django select field to render a country or currency > option (e.g., django-countries or django-money), because either of these > would have well over a hundred entries (and my form happens to have both). > Instead they would be loading these options via AJAX or using a different > widget all together like an auto-complete. (I get it that a long list is > not the best UX but that's a bit of a different discussion). > Have you profiled a country select on its own? Your original post suggested you had multiple large (hundreds of options) selects in a single form that you were rendering. Whether any specific individual select in the form is the sole culprit, or whether it's the combination of them, is something you still haven't pinned down, and it's a bit combative to jump to "nobody must have a country select" from that. In general, a select with a large set of options is going to be slower to render. It may turn out that this has nothing whatsoever to do with your problem, but we don't have enough information to precisely diagnose your problem; all we can do here is give you general advice like "avoid rendering a template hundreds of times if you can, or use a faster-rendering template option if you can't". -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAL13Cg9YnOwGYATe%3DBpHBGEoULeNJ8VngJsPp3LQfGR1AJvxHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
