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://
>
> I have a requirement to use querysets as choices in various elements
> of a form, and as the data grows this is clearly going to have a big
> hit on the database every time this form is loaded. Can anyone think
> of a way around this? Is there a way to cache the query set and only
>
No one have any ideas?
Thanks,
Dave
On 3 Sep 2007, at 12:51 pm, David Reynolds wrote:
>
> Hi,
>
> I have a requirement to use querysets as choices in various elements
> of a form, and as the data grows this is clearly going to have a big
> hit on the database every time this form is loaded.
Hi,
I have a requirement to use querysets as choices in various elements
of a form, and as the data grows this is clearly going to have a big
hit on the database every time this form is loaded. Can anyone think
of a way around this? Is there a way to cache the query set and only
update
4 matches
Mail list logo