Installation: db:prepare with pre-created databases

[pglombardo]

I just deployed solid_cable (latest) to production and hit a few problems. The largest of which was this this from the README:

Then run db:prepare in production to ensure the database is created and the schema is loaded.

db:prepare will only execute if the database doesn't exist.

Problem

For those who use managed databases, the DB is pre-created and the path forward isn't clear.

So I had an empty solid_cable DB with no tables causing app failures.

Failed Solution

I tried bin/rails db:schema:load:cable which errored out with:

TypeError Invalid type for configuration. Expected Symbol, String, or Hash. Got nil

which I didn't investigate unfortunately.

Solution

Copying db/cable_schema.rb to a migration in db/cable_migrate resolved the issue for me.

I'm not sure if this was the best path to resolution but I wanted to point out the obstacle that likely others will hit.

BTW the same problem scenario exists for solid_cache.

[bellenss]

confirming I bumped into the same issue - the solution / workaround helped me. Thx.

[smarquezs]

Confirming I faced the same issue and this workaround worked for me, thanks.

[safeforge]

I'm experiencing similar issues when setting up solid_cable. Specifically, the command rake db:setup:cable depends on db:test:purge:cable, which fails when a test database is not configured.

In my case, I have only the development environment set up for solid_cable with the following configuration:

development:
  primary:
    <<: *default
    database: myapp_development
  cable:
    <<: *default
    migrations_paths: db/cable_migrate
    database: myapp_development_cable

test:
  primary:
    <<: *default
    database: myapp_test

Attempting to run rails db:schema:load:cable results in:

bin/rails aborted!
TypeError: Invalid type for configuration. Expected Symbol, String, or Hash. Got nil (TypeError)

        raise TypeError, "Invalid type for configuration. Expected Symbol, String, or Hash. Got #{config.inspect}"
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Tasks: TOP => db:schema:load:cable => db:test:purge:cable
(See full trace by running task with --trace)

From what I can see in activerecord-8.0.1/lib/active_record/railties/databases.rake, the db:test:purge:cable task attempts to purge the test database, even when one isn’t explicitly configured.

# desc "Empty the #{name} test database"
namespace :purge do
  task name => %w(load_config check_protected_environments) do
    ActiveRecord::Tasks::DatabaseTasks.with_temporary_pool_for_each(env: "test", name: name) do |pool|
      db_config = pool.db_config
      ActiveRecord::Tasks::DatabaseTasks.purge(db_config)
    end
  end
end

I'm wondering if it's necessary to define test environment entries in database.yml, even when the solid_cable adapter is configured only for development in cable.yml.

development:
  adapter: solid_cable
  connects_to:
    database:
      writing: cable
  polling_interval: 0.5.seconds
  message_retention: 1.day

test:
  adapter: test

Of course, the same behavior occurs across all solid_{cable, cache, queue}.

[npezza93]

Happy to take any updates to the readme for this but it sounds like a test db wasnt being configured for cable. bin/rails db:schema:load:cable should do the trick.

[nimmolo]

@npezza93 I'm getting the same issue, bin/rails db:schema:load:cable doesn't do it.

Hm. Why would a test db need to be configured for cable on production? Or, if it should be, I feel like it should be in the README. It doesn't mention anything about setting up a test cable db.