rake db:automigrate "default store already setup"

[Larry Kelly]

I've created an app and a resource with merb-gen.
When I run rake db:automigrate I get the message:

Rake Aborted!
Default store already setup

The schema was not created. No tables are visible in the store.
Using SQLite3, Latest version of Fedora. Any ideas on how I can get
past this?

[Bill Turner]

I believe the "default store" in question is the default cache store,
and not anything DB related. There is some more info here in this
ticket:

http://merb.lighthouseapp.com/projects/7433/tickets/1191-rake-dbmigrate-initrb-gets-loaded-2-times

I had thought a fix had already been released, but perhaps not. In the
meantime, there are a couple of workarounds in that ticket thread.

Bill

[myabc]

> On Feb 3, 12:17 pm, Larry Kelly <ldk2...@gmail.com> wrote:
> > I've created an app and a resource with merb-gen.
> > When I run rake db:automigrate I get the message:
> >
> > Rake Aborted!
> > Default store already setup
> >
> > The schema was not created.  No tables are visible in the store.
> > Using SQLite3, Latest version of Fedora.  Any ideas on how I can get
> > past this?

If you can survive without caching (at least during your development
process) then just go ahead and comment out the merb-cache dependency.
I've had to do this for a few newly generated projects over the last
couple days (see http://github.com/nedap/locomotive_sample_app/commit/6d8ced5b9b1d547a36a6f408735313ba6352727e)

Alex

[Matt Aimonetti]

I fixed this problem in the 1.0.x branch. As a quick fix, you can just make sure that the default cache isn't set:

dependency("merb-cache", merb_gems_version) do
  Merb::Cache.setup do
    register(Merb::Cache::FileStore) unless Merb.cache
  end
end

- Matt