Level 104
Squash your migrations and you won't be dealing with dropping FKs. Your tests will run faster as well!
Dec 8, 2023
7
Level 1
how do you do testing with migrations (drop foreign key, dropcolumns, add new)?
Hello! I have 54 migrations. I was removing, adding columns, dropping indexes, adding indexes, etc.
Now tests (phpunit) don't run . I have bunch o sqlite problem like
BadMethodCallException: SQLite doesn't support dropping foreign keys (you would need to re-create the table).
and porbably many more.
Is there any good way so test will run fast (in memory?) and without errors?
Level 41
Working with foreign keys in migrations with sqlite can be annoying.
@tykus solution probably works. Alternatively, in the config/database.php, sqlite section, you can disable foreign_key_constraints.
connections => [
'sqlite' => [
'driver' => 'sqlite',
'url' => env('DATABASE_URL'),
'database' => env('DB_DATABASE', database_path('database.sqlite')),
'prefix' => '',
'foreign_key_constraints' => env('DB_FOREIGN_KEYS', false),
],
]
Level 1
@kevinbui same error as before =(
Level 74
I would strongly suggest moving over you dev database to whatever you have in production, and then install the plannr/laravel-fast-refresh-database package, and as @tykus suggested, squash your migrations.
https://packagist.org/packages/plannr/laravel-fast-refresh-database
Level 1
the sqlite memory database doesn't want to use dumped sql file.
Illuminate\Database\QueryException: SQLSTATE[HY000]: General error: 1 near "AUTO_INCREMENT": syntax error (Connection: sqlite, SQL: /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
I'm using mysql now for testing. This feels wrong
Level 74
@restart93 I don't agree. It's the correct move to make, SQLite is really good for starting your application, but as the complexity in the database grows, you will and should sooner or later move to a RDBMS, and when you do so, make sure it is the same as in production. That way you will not get any nasty surprises on deploy day.
1 like
Level 80
@restart93 Because the dump file will be a MySQL dump; not a SQLite dump.
Squashing migrations is not the answer. Using the same database engine in your tests is.
Please or to participate in this conversation.