Matt-Yorkley 39fa315ecc Guard against calls to the database during db:create ...

Rails 5.2 has changed the way initializers are called during certain rake tasks including `db:create`. Initializers that were previously not loaded are now loaded (basically the whole app is loaded). This means any calls to #table_exists? that appear in the app will throw fatal errors as the database doesn't exist yet during that task, but those calls are made before `db:create` has even started, which means the database can't be created.

There are also a few other places in Spree code where #table_exists? is called, and they already call #connected? first to guard against this issue.

2021-04-13 16:55:19 -07:00

..

environments

Raise errors in specs with missing translations

2021-03-30 17:08:17 +11:00

initializers

Enable customer_balance toggle in tests

2021-04-12 09:31:23 +02:00

locales

Updating translations for config/locales/ru.yml

2021-04-13 01:05:34 +10:00

routes

match any API version

2021-03-27 11:21:18 -07:00

application.rb

Guard against calls to the database during db:create

2021-04-13 16:55:19 -07:00

application.yml.example

Enable new customer balance for the core team

2020-12-16 11:09:54 +01:00

boot.rb

new rails 3.1.4 app

2012-03-27 10:10:26 +11:00

database.yml

Increase DB connection pool size for specs

2021-04-12 12:15:59 +10:00

environment.rb

Use require_relative introduced in Ruby 1.9.2

2016-07-20 16:07:35 +10:00

newrelic.yml.example

Add config/newrelic.yml.example for newrelic_rpm gem

2019-04-12 13:57:50 +08:00

ng-test.conf.js

Create a new angularjs module: OFNShared

2021-03-18 09:48:17 +01:00

routes.rb

move controller and mailer outside of spree namespace; use haml in template

2021-01-21 09:18:29 -08:00

schedule.rb

Run data cleanup job at 4:30am

2021-01-28 21:51:50 +00:00

spree.yml

spree install.

2012-03-27 11:06:49 +11:00