[10.x] Remove warning about schema dumps and in-memory SQLite databases. #9312
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The docs have a warning in the "Squashing Migrations" section that schema dumps may not be restored to in-memory SQLite database. However, I believe this issue was resolved in PR #45375, which was released in v9.45.1.
To test this, I ran the following steps in a project that had existing migrations:
database/schema/sqlite-schema.dump
php artisan migrate
) and see them all succeed.According to a previous issue #35162, this normally would have failed with all the migration files stating "SQLSTATE[HY000]: General error: 1 no such table: migrations". However, it appears to be working fine now.