Add db:drop and db:create to make compatible with databases with foreign keys

[houen]

No description provided.

[houen]

The drop tables part of db:schema:load is not compatible with databases containing foreign keys (in my case created by the Foreigner gem (https://github.com/matthuhiggins/foreigner). By using db:drop and then db:create before db:schema:load, we can get around that

[grosser]

so db:schema:load would not work in your app anyway -> make it drop+create and you should be good with parallel too

[sj26]

We should be using db:[schema|structure]:dump then parallel db:test:load_[schema|structure] which handles these cases.

[zenkalia]

what's the status on this? i'm hitting this issue myself and looking for a solution

[grosser]

would be nice to stay close to what rails is doing and not randomly dropping/creating a db,
does parallel:load_schema work ? if not, what do you use to normally load your schema ?

[zenkalia]

i drop the dbs entirely, actually:

alias psetup='bx rake parallel:drop parallel:create parallel:prepare'

[alexpjohnson]

I'm not sure where this is in the pipeline of getting merged, but Rails recently introduced the rake db:purge method, which will empty the database. The commit is here. This commit documents the change in behavior of db:schema:load, which causes this gem to break on the latest version of Rails.

[grosser]

Can you turn this into a PR ?
Ideally something that checks versions and then does load or purge ?

[alexpjohnson]

Sure #407