[OSM-dev] Auto closing of changesets in API 0.6
frederik at remote.org
Fri Oct 3 18:17:19 BST 2008
Shaun McDonald wrote:
> There is a slight issue here, because in the database table for
> changesets only stores the time it was created_at (timestamp), and
> whether it is open, as a boolea. It doesn't store the expiry time, nor
> the time it was closed.
I thought the one that I designed did have an expiry timestamp, and I
also thought I'd done the rails code that would extend the lifetime on
updates. Maybe forgot to check it in? Will check on my notebook.
> Should we have a daemon to clear empty expired changesets?
I'd think about that once empty expired changesets become a problem.
Frederik Ramm ## eMail frederik at remote.org ## N49°00'09" E008°23'33"
More information about the dev