Scenic Integration Causes Issues with Multiple Databases #123
Description
We're using a multiple database setup in which we run TimescaleDB as a separate database alongside our primary database. Our primary database uses Scenic while our TimescaleDB instance does not.
When the timescaledb-ruby gem initializes it automatically hooks into Scenic overriding the database to use the TimescaleDB adapter. This is not a desirable behavior as it breaks migrations with our primary database.
Time timescaledb-ruby should expose a configuration to enable/disable the Scenic adapter, and further, should provide configuration options to make multi-database operations more stable.