I think the other situation is that the old cron job is not done yet
and the new cron job gets started up.
Having a flag in the DB would be able to fix that as well.
On Jul 21, 9:33 pm, Andrew Fong wrote:
> >> I was worried by potential caching issues with the database
There is a hacky way, which is not good practice and can probably mess
with your 3rd party photologue stuff:
from myproject1.photologue.models import PhotoSize
PhotoSize._meta.abstract = True
BR
Chee Ming
On Feb 22, 12:35 am, TiNo wrote:
> On Sat, Feb 21, 2009 at 16:04,
If I am not mistaken, you're talking about passing states between the
request that is returning the redirect after a POST and the new
request that is rendering the GET.
If you really need to do that you can use sessions to store the data
that you need and then just set the initial data for the
3 matches
Mail list logo