{"action":"created","issue":{"url":"https://api.github.com/repos/kvesteri/sqlalchemy-continuum/issues/124","repository_url":"https://api.github.com/repos/kvesteri/sqlalchemy-continuum","labels_url":"https://api.github.com/repos/kvesteri/sqlalchemy-continuum/issues/124/labels{/name}","comments_url":"https://api.github.com/repos/kvesteri/sqlalchemy-continuum/issues/124/comments","events_url":"https://api.github.com/repos/kvesteri/sqlalchemy-continuum/issues/124/events","html_url":"https://github.com/kvesteri/sqlalchemy-continuum/issues/124","id":132014828,"number":124,"title":"How can I clear the change history on a per-row basis?","user":{"login":"fake-name","id":1401239,"avatar_url":"https://avatars.githubusercontent.com/u/1401239?v=3","gravatar_id":"","url":"https://api.github.com/users/fake-name","html_url":"https://github.com/fake-name","followers_url":"https://api.github.com/users/fake-name/followers","following_url":"https://api.github.com/users/fake-name/following{/other_user}","gists_url":"https://api.github.com/users/fake-name/gists{/gist_id}","starred_url":"https://api.github.com/users/fake-name/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fake-name/subscriptions","organizations_url":"https://api.github.com/users/fake-name/orgs","repos_url":"https://api.github.com/users/fake-name/repos","events_url":"https://api.github.com/users/fake-name/events{/privacy}","received_events_url":"https://api.github.com/users/fake-name/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-02-07T21:28:08Z","updated_at":"2016-03-10T10:01:56Z","closed_at":null,"body":"I have a case where I want to track changes across a fairly large table, with a few rows that change extremely often, and a extremely large set of slowly-changing rows.\r\n\r\nI'm much more interested in the change history from the slowly changing rows then the few fast-changing rows, but the issue at the moment is that the fast-changing rows will cause my DB server to literally run out of space if they're tracked for more then a month or so.\r\n\r\nIs there anyway I can truncate or just plain delete the history *for just a few rows*? Looking at how the schema works, I can probably fudge something horribly messy up by walking the history manually, but that sort of thing seems like it should really be integrated into the library.\r\n\r\n\r\n---\r\n\r\nAs an aside, this plugin is **awesome**. I was in the process of trying to implement a horrible change-logging hack disaster, and it literally solved my entire problem with 2 lines of code."},"comment":{"url":"https://api.github.com/repos/kvesteri/sqlalchemy-continuum/issues/comments/194766342","html_url":"https://github.com/kvesteri/sqlalchemy-continuum/issues/124#issuecomment-194766342","issue_url":"https://api.github.com/repos/kvesteri/sqlalchemy-continuum/issues/124","id":194766342,"user":{"login":"kvesteri","id":398714,"avatar_url":"https://avatars.githubusercontent.com/u/398714?v=3","gravatar_id":"","url":"https://api.github.com/users/kvesteri","html_url":"https://github.com/kvesteri","followers_url":"https://api.github.com/users/kvesteri/followers","following_url":"https://api.github.com/users/kvesteri/following{/other_user}","gists_url":"https://api.github.com/users/kvesteri/gists{/gist_id}","starred_url":"https://api.github.com/users/kvesteri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kvesteri/subscriptions","organizations_url":"https://api.github.com/users/kvesteri/orgs","repos_url":"https://api.github.com/users/kvesteri/repos","events_url":"https://api.github.com/users/kvesteri/events{/privacy}","received_events_url":"https://api.github.com/users/kvesteri/received_events","type":"User","site_admin":false},"created_at":"2016-03-10T10:01:56Z","updated_at":"2016-03-10T10:01:56Z","body":"Currently yes, of course you can automate this by running periodic tasks. I don't think it is in the scope of this project to automate this process."}}