Rake tasks coupled to regular db tasks in rails #312

Closed
mfilej opened this Issue Feb 11, 2013 · 4 comments

Projects

None yet

5 participants

@mfilej
Contributor
mfilej commented Feb 11, 2013

I'm finding that having ripple's tasks (create, drop) run together with rails' regular db tasks takes away some of the flexibility, for example when I want to drop either the data in riak or in postgres, but not both.

In addition I think this could catch someone off guard. When a developer wants do drop the database that activerecord is using by issuing rake db:drop it would inadvertently also drop the data from riak.

Is there a way to run the original db tasks without affecting riak?

Would you accept a patch that would move the tasks into a separate namespace?

@thunder-

+1

@rodrigues

+1

@seancribbs
Contributor

PRs accepted

@seancribbs seancribbs pushed a commit that closed this issue Feb 13, 2013
@mfilej mfilej Avoid overwriting rails db:* rake tasks
Closes #312.
8cbefbb
@mfilej mfilej added a commit to Clubjudge/ripple that referenced this issue Feb 14, 2013
@mfilej mfilej Avoid overwriting rails db:* rake tasks
Closes #312.
1b7b0ce
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment