This repository has been archived by the owner on Dec 31, 2022. It is now read-only.
Support null database driver #98
Comments
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 24, 2017
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 24, 2017
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 24, 2017
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 25, 2017
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 28, 2017
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 29, 2017
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 29, 2017
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 30, 2017
yurivm
pushed a commit
to homeday-de/opsworks_ruby
that referenced
this issue
Jun 11, 2018
dotnofoolin
pushed a commit
to dotnofoolin/opsworks_ruby
that referenced
this issue
Nov 23, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some Ruby applications use no RDBMS whatsoever. For these applications, the default database driver setting of
sqlite3causes an error because the sqlite3 configure code expects the existence of adb/subdirectory into which it can symlink theshared/db/data.sqlite3file.A cleaner workaround for this situation is to simply have a "null" DB driver that short-circuits all database-related setup/configuration/migration operations as no-ops.
The text was updated successfully, but these errors were encountered: