Re: Knowing when cache expires or DurationField is done

Just to clarify the first point: celery is "updating" the cache with new info once the cache expires; hence the need for the cache to expire. I thought about using a DB table, but also thought about how wasteful it would be to keep a DurationField (which I still don't know how to use) to log when celery should execute a task.

On Saturday, August 24, 2019 at 5:12:12 PM UTC-4, Yoo wrote:

1. Using celery to make a replacement cache when that specific expires, but not sure how to do it.

2. Along the same lines, I need to also know when a DurationField is at "zero." Not sure how a DurationField works though. Again, need celery to be able to execute something when a specific record has its attribute hit the "zero" on its "timer."

If there are other ways, lemme know!

Thanks!

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9a902c69-72db-404c-b76e-a42fbbdbbb1e%40googlegroups.com.