crhg / laravel-sqlite-named-memory-connection
SQLite connector which supports named in-memory database connection
Installs: 9 378
Dependents: 0
Suggesters: 0
Security: 0
Stars: 2
Watchers: 2
Forks: 1
Open Issues: 2
Requires
- php: >=7.0.0
- ext-pdo: *
- illuminate/database: ^5.5 || ^6.0 || ^7.0
- illuminate/support: ^5.5 || ^6.0 || ^7.0
Requires (Dev)
- phpunit/phpunit: ^7.3
README
This package provides sqlite-named
driver that extends Laravel's sqlite
driver.
Using this driver allows you to specify a database in the form named-memory:<name>
.
(<name>
is an arbitrary string (including empty string))
It connects to SQLite's in-memory database as well as :memory:
.
:memory:
creates a new database for each connection, whereas :named-memory:<name>
returns the same connection 
if <name>
is same.
INSTALL
composer require crhg/laravel-sqlite-named-memory-connection
CONFIGURATION
Specify sqlite-named
for driver
in config/database.php
.
config/database.php
:
'connections' => [ //... 'sqlite-named' => [ 'driver' => 'sqlite-named', 'url' => env('DATABASE_URL'), 'database' => env('DB_DATABASE', database_path('database.sqlite')), 'prefix' => '', 'foreign_key_constraints' => env('DB_FOREIGN_KEYS', true), ], //... ],
.env
:
DB_CONNECTION=sqlite-named DB_DATABASE=:named-memory:foo
BACKGROUND
SQLite's in-memory database is effective to speed up tests using the database.
However, using refreshApplication()
caused the problem of emptying the database.
This is due to the following reasons.
- Since the IoC container is regenerated,
\Illuminate\Database\DatabaseManager
that was registered as singleton is discarded and replaced with a new one. - Information on the connected database managed by
DatabaseManager
is not passed to the newly generatedDatabaseManager
. - When a connection to the DB is requested for the first time after
refreshApplication()
, the DatabaseManager has no connection, so a new connection to:memory:
is generated - The connection to
:memory:
is a connection to a newly created empty in-memory database.
If you use :named-memory:<name>
instead of :memory:
,
this problem can be avoided by returning the connection identified by <name>
which was used before refreshApplication ()
.