On Jun 29, 10:20 pm, Ben Bangert <[EMAIL PROTECTED]> wrote:
> Nope, that's a bit tricky and depends greatly on deployment
> environment. In a cluster, which machine runs the delete, how often,
> if it just happens by default there's odd lock conditions, etc. It's
> safer to let the person deploying it use the appropriate strategy.
Interesting points.
> If you're using db session, it does store last accessed time for each
> session. There's no reason you can't have a very simple SQL command
> that runs every day to clear the ones with the accessed timestamp > 2
> days or whatever.
So no shortcoming!
FWIW, in the past I've done this under modperl:
- delete in db based on last-accessed timestamp ( as we know now
pylons has )
- delete on fs based on inode timestamps
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
