{"action":"opened","issue":{"url":"https://api.github.com/repos/sequelpro/sequelpro/issues/2548","repository_url":"https://api.github.com/repos/sequelpro/sequelpro","labels_url":"https://api.github.com/repos/sequelpro/sequelpro/issues/2548/labels{/name}","comments_url":"https://api.github.com/repos/sequelpro/sequelpro/issues/2548/comments","events_url":"https://api.github.com/repos/sequelpro/sequelpro/issues/2548/events","html_url":"https://github.com/sequelpro/sequelpro/issues/2548","id":172661793,"number":2548,"title":"FR: Cache and rollback DB changes","user":{"login":"nathanpitman","id":694545,"avatar_url":"https://avatars.githubusercontent.com/u/694545?v=3","gravatar_id":"","url":"https://api.github.com/users/nathanpitman","html_url":"https://github.com/nathanpitman","followers_url":"https://api.github.com/users/nathanpitman/followers","following_url":"https://api.github.com/users/nathanpitman/following{/other_user}","gists_url":"https://api.github.com/users/nathanpitman/gists{/gist_id}","starred_url":"https://api.github.com/users/nathanpitman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nathanpitman/subscriptions","organizations_url":"https://api.github.com/users/nathanpitman/orgs","repos_url":"https://api.github.com/users/nathanpitman/repos","events_url":"https://api.github.com/users/nathanpitman/events{/privacy}","received_events_url":"https://api.github.com/users/nathanpitman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-23T10:15:19Z","updated_at":"2016-08-23T10:15:19Z","closed_at":null,"body":"A feature I would absolutely love to see in Sequel Pro in a 'cache and rollback' facility for any given database. The purpose of this feature would be to allow a developer to 'quickly and easily rollback' to a previous version of a database.\r\n\r\nI see this being most useful to developers working on a local dev environment where they might be executing code that creates or destroys data and then need to 'adjust and re-run' the code as part of the development/testing process.\r\n\r\nIf you are working with a large database the process of 'rolling back' to a previous clean DB dump can be time consuming and it seems odd that no one has sought to solve this problem.\r\n\r\nRollback points would be configurable, i.e. \"create rollback state every X minutes\" or \"on demand\". I imagine that technically this might be achieved by creating a mirror DB and configuring that as such in Sequel Pro, i.e. \"Use this DB as a mirror for rollbacks\".\r\n\r\nObviously Sequel Pro would need to be running for this to be effective, but I don't see that as a problem, most developers will have the SQL client of their choice open while they are working on something which impacts on the DB.\r\n\r\nThoughts?"}}
{"actor":{"display_login":"nathanpitman"}}