Specifically, the boolean values describe certain types of
data the
user wishes to mask when looking through the database. The
values are
specific to each user, so there is no reason to DB them. I
am storing
them in the session variable. The problem is that the
variables are
not updated instantly, and I was wondering why this could
be.
On Jun 27, 2:06 pm, "Jeremy Dunck" <jdu... gmail.com> wrote:
> On 6/27/07, Val <VASav... gmail.com> wrote:
> ...
>
> >change a boolean
> > value
>
> A boolean value where, in what context, for what
purpose?
>
> > it
> > takes multiple refreshes for the value to update
itself.
>
> There are multiple processes in general-- runserver is
one process,
> but shouldn't be used outside of development.
>
> If you're setting a value you wish to be shared amongst
multiple
> requests, you need to put it out of process somehow.
Cache or DB are
> the general answers.
--~--~---------~--~----~------------~-------~--~----~
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
django-users-unsubscribe googlegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
|