Added migration for upgrade_versions on rolling_capabilities #42

Merged
merged 3 commits into from Jan 9, 2013

Conversation

Projects
None yet
3 participants

No description provided.

@@ -11,7 +11,7 @@
#
# It's strongly recommended to check this file into your version control system.
README.md
+Your best bet is to get the current heroku dataset with `pg_dump`. You need the heroku database url, which you can get with `heroku config` if you have access. If you don't, you shouldn't be doing this.
+
+```
+pg_dump postgres://whatever > heroku.sql
@seancribbs

seancribbs Jan 9, 2013

Add -O -x to the pg_dump command. This omits role/permissions information that doesn't make sense for a dev version.

+ def up
+ say_with_time "adding upgrade_version to rolling_capabilities" do
+ @projects = Project.where(:name => %w{riak riak_ee}).all
+ %w{rolling_capabilities}.each do |name|
@seancribbs

seancribbs Jan 9, 2013

Is it really necessary to make this a loop?

@joedevivo

joedevivo Jan 9, 2013

nope, not even a little necessary, but I totally copied it from another migration and the less I changed, the less could go wrong.

@seancribbs

seancribbs Jan 9, 2013

Not significant, really. Perhaps we should do a deeper review at some point and pull these into a library file.

done, added some line breaks too

The migrations mostly come out at night, mostly.

The migrations mostly come out at night, mostly.

👍

Contributor

cmeiklejohn commented Jan 9, 2013

@seancribbs is on point today.

joedevivo added a commit that referenced this pull request Jan 9, 2013

Merge pull request #42 from basho/jd-rolling-caps-legacy-data
Added migration for upgrade_versions on rolling_capabilities

@joedevivo joedevivo merged commit 48c50ae into master Jan 9, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment