#1151: VisitManagers should delete expired entries in tg_visit
-------------------------------------+--------------------------------------
Reporter: grover | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 1.5
Component: Identity | Version: 1.0b1
Severity: normal | Resolution:
Keywords: visit data housekeeping |
-------------------------------------+--------------------------------------
Comment (by chrisz):
Right, the `VisitManager` seems to be the appropriate place for deleting
expired visits.
In one project I'm also dealing with many users created on the fly from a
remote LDAP repository. In this case, in addition to the `visit` table,
expired entries can also accumulate in the `visit_identity` and `tg_user`
tables. Maybe we should also provide a solution for that.
As a temporary solution, I have added an example in
http://docs.turbogears.org/1.0/Scheduler that shows how you clean up the
entries using the scheduler.
--
Ticket URL: <http://trac.turbogears.org/ticket/1151#comment:7>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
