{"action":"opened","issue":{"url":"https://api.github.com/repos/bundler/gemstash/issues/43","labels_url":"https://api.github.com/repos/bundler/gemstash/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/bundler/gemstash/issues/43/comments","events_url":"https://api.github.com/repos/bundler/gemstash/issues/43/events","html_url":"https://github.com/bundler/gemstash/issues/43","id":113955950,"number":43,"title":"DB Migration policy?","user":{"login":"smellsblue","id":150632,"avatar_url":"https://avatars.githubusercontent.com/u/150632?v=3","gravatar_id":"","url":"https://api.github.com/users/smellsblue","html_url":"https://github.com/smellsblue","followers_url":"https://api.github.com/users/smellsblue/followers","following_url":"https://api.github.com/users/smellsblue/following{/other_user}","gists_url":"https://api.github.com/users/smellsblue/gists{/gist_id}","starred_url":"https://api.github.com/users/smellsblue/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smellsblue/subscriptions","organizations_url":"https://api.github.com/users/smellsblue/orgs","repos_url":"https://api.github.com/users/smellsblue/repos","events_url":"https://api.github.com/users/smellsblue/events{/privacy}","received_events_url":"https://api.github.com/users/smellsblue/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-29T00:41:49Z","updated_at":"2015-10-29T00:41:49Z","closed_at":null,"body":"I added [a migration](https://github.com/bundler/gemstash/blob/master/lib/gemstash/migrations/03_version_full_name.rb) that altered an existing table originally created in [another migration](https://github.com/bundler/gemstash/blob/master/lib/gemstash/migrations/01_gem_dependencies.rb). The migration would be simplier if it was just folded into the original one, but it would require anyone with a Gemstash server to delete their database, migrate it manually, or otherwise deal with it. I think that is likely just a few test Gemstash instances right now amongst us, but I don't know for sure.\r\n\r\nThis brings up a question about DB migration policy... should we support someone cloning the repository against master and pulling the codebase and running from there? Or do we require they strictly go through the gem? I'm personally in favor of requiring they go through the gem, otherwise we would have to be super careful about any merges into master. This would allow me to merge the 2 migrations (maybe even all migrations into 1 migration?).\r\n\r\nThoughts?\r\n\r\nShould I merge the 2 migrations? All 3 migrations? Leave as is and treat each migration going forward as if there is a production database in the wild?"}}