You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SQLiteGrammar ignores table prefixes when ordered to compile a dropColumn statement.
This exception is thrown when SQLiteGrammar queries for existing columns in compileDropColumn resulting in a similar exception:
Doctrine\DBAL\Schema\SchemaException : There is no column with name 'col_name' on table 'table_name_without_prefix'.
This happens when using SQLite driver with a table prefix configured in the connection.
Steps To Reproduce:
Configure a (memory stored) SQLite connection with a table prefix.
Create a migration that creates a column.
Create a migration that drops the same column.
Notes
There is currently no test for SQLite grammar compileDropColumn() and prefixes are tested neither. It seems to me that creating the former would require me to mock many objects (right?). I've fixed the latter by adding a prefix to the grammar in DatabaseSQLiteSchemaGrammarTest though.
The text was updated successfully, but these errors were encountered:
Description:
SQLiteGrammar ignores table prefixes when ordered to compile a
dropColumn
statement.This exception is thrown when SQLiteGrammar queries for existing columns in
compileDropColumn
resulting in a similar exception:Doctrine\DBAL\Schema\SchemaException : There is no column with name 'col_name' on table 'table_name_without_prefix'.
This happens when using SQLite driver with a table prefix configured in the connection.
Steps To Reproduce:
Notes
There is currently no test for SQLite grammar
compileDropColumn()
and prefixes are tested neither. It seems to me that creating the former would require me to mock many objects (right?). I've fixed the latter by adding a prefix to the grammar inDatabaseSQLiteSchemaGrammarTest
though.The text was updated successfully, but these errors were encountered: