Work around a bug in DatabaseCleaner when using the deletion strategy on MySQL
This commit is contained in:
parent
93ea3234df
commit
bbe00038da
1 changed files with 15 additions and 0 deletions
|
@ -1,3 +1,18 @@
|
||||||
|
require 'database_cleaner/active_record/deletion'
|
||||||
|
|
||||||
|
module FakeInformationSchema
|
||||||
|
# Work around a bug in DatabaseCleaner when using the deletion strategy:
|
||||||
|
# https://github.com/DatabaseCleaner/database_cleaner/issues/347
|
||||||
|
#
|
||||||
|
# On MySQL, if the information schema is said to exist, we use an inaccurate
|
||||||
|
# row count leading to some tables not being cleaned when they should
|
||||||
|
def information_schema_exists?(_connection)
|
||||||
|
false
|
||||||
|
end
|
||||||
|
end
|
||||||
|
|
||||||
|
DatabaseCleaner::ActiveRecord::Deletion.prepend(FakeInformationSchema)
|
||||||
|
|
||||||
RSpec.configure do |config|
|
RSpec.configure do |config|
|
||||||
# Ensure all sequences are reset at the start of the suite run
|
# Ensure all sequences are reset at the start of the suite run
|
||||||
config.before(:suite) do
|
config.before(:suite) do
|
||||||
|
|
Loading…
Reference in a new issue