On Jun 19, 8:49 pm, Jason Davies <[EMAIL PROTECTED]> wrote: > 2. Utilise simple thread synchronisation mechanisms to control access > to the queryset in question. This would only need to be done when > cache_choices is True, so in the usual case when it is False there > would be no performance impact.
I found a way to cache the choices without having to use any locks [1]. Cheers, Jason [1]: http://code.djangoproject.com/attachment/ticket/7475/models.3.py.diff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
