Allow configuration to skip the execute_inline! call

README.md

@@ -109,6 +109,11 @@ end
 to prevent accidental data loss. After successful or failed LHM migrations, these leftover
 tables must be cleaned up.
 
+**Note:** When developing locally or running tests, LHM runs 'inline' by default, meaning that the
+extra table is not used and the original table is not replaced. If this behavior is not desirable
+for your project, you can disable it by setting `Lhm.disallow_inline!` in the appropriate
+environment file or initializer.
+
 ### Usage with ProxySQL
 LHM can recover from connection loss. However, when used in conjunction with ProxySQL, there are multiple ways that
 connection loss could induce data loss (if triggered by a failover). Therefore  it will perform additional checks to
@@ -278,7 +283,7 @@ To run the tests:
 ```bash
 bundle exec rake unit # unit tests
 bundle exec rake integration # integration tests
-bundle exec rake unit # all tests
+bundle exec rake specs # all tests
 ```
 
 You can run an individual test as follows:

lib/lhm.rb

@@ -116,6 +116,18 @@ def self.logger
       end
   end
 
+  @@disallow_inline = false
+
+  # Use to control the inline-execution of Lhm migrations - by default migrations are inlined
+  # in test and development environments, and in some cases that's not desireable.
+  def self.disallow_inline!
+    @@disallow_inline = true
+  end
+
+  def self.inline_allowed?
+    !@@disallow_inline
+  end
+
   private
 
   def drop_tables_and_triggers(run = false, triggers, tables)

lib/lhm/railtie.rb

@@ -2,7 +2,7 @@ module Lhm
   class Railtie < Rails::Railtie
     initializer "lhm.test_setup" do
       if Rails.env.test? || Rails.env.development?
-        Lhm.execute_inline!
+        Lhm.execute_inline! if Lhm.inline_allowed?
       end
     end
   end