[11.x] Fix SQLite schema dumps containing internal sqlite_*
objects
#52135
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.
This PR updates the SQLite schema dump to remove all
CREATE TABLE sqlite_*
statements. Laravel already removesCREATE TABLE sqlite_sequence(...);
if it exists, this PR ensures that we also removeCREATE TABLE sqlite_stat1(...);
,CREATE TABLE sqlite_stat4(...);
, etc.These SQLite internal schema object names are reserved and cannot be created except by SQLite itself, so trying to loading dumps that contain any of these statements will fail. The
sqlite_stat1
andsqlite_stat4
tables will exist in any SQLite database with data in it that has ever had thePRAGMA optimize;
command run, which is likely a significant portion of them since it's recommended in the SQLite docs. There may be other tables with reserved names too, likesqlite_stat2
orsqlite_autoindex_1
; this PR ensures they are all removed.Fixes #52131.