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?
Avoid overwriting rails db:* rake tasks