Skip to content
This repository

Rake tasks coupled to regular db tasks in rails #312

mfilej opened this Issue February 11, 2013 · 4 comments

5 participants

Miha Filej Sean Cribbs Gert van der Spoel Panayotis Matsinopoulos Victor Rodrigues
Miha Filej

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?

Sean Cribbs

PRs accepted

Sean Cribbs seancribbs closed this in 8cbefbb February 13, 2013
Miha Filej mfilej referenced this issue from a commit in Clubjudge/ripple February 13, 2013
Miha Filej Avoid overwriting rails db:* rake tasks
Closes #312.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.