Regression regarding unavailable database in 4.x+ versions

[colszowka]

Hi there,

I believe the bugfix for #179 via #182 has introduced a regression for the original fix introduced in #156 - we are failing to upgrade to version 4, which is blocking us from upgrading forward to Rails 7.2, because (only on CI) our application fails to boot on an accepts_nested_attributes_for store model property, as it complains about a missing table.

I am failing to reproduce this locally so far, but on CI our setup is like this:

• Postgres docker image with credentials configured
• Rails app rspec specs get connected via a DATABASE_URL env var that points to that single instance

I can imagine this has to do with the "missing" test/development database, as we only provide a single database here, and I know rails has a bit of a history of trying to connect to development in test env regardless IIRC.

Not sure either what the fix for this is, considering https://github.com/rails/rails/issues/52685, but as it stands we're blocked from upgrading here and it would be great if we could get the original problem fixed by #156 back in order somehow