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
Fix removing schema from table name on asset filtering
The resolveTableName() method has been removed entirely because it is no
longer needed and was causing inconsistent behavior. On platforms that
support schemas (e.g., PostgreSQL, SQL Server), DBAL provides qualified
table names (schema.table) which should be preserved for proper filtering.
On platforms that don't support schemas (e.g., MySQL, SQLite), DBAL already
provides unqualified table names, making the schema stripping unnecessary.
The original purpose of resolveTableName() was to handle cases where table
names might contain dots on platforms without schema support, but this
approach was flawed because it incorrectly assumed any dot represented a
schema separator. This could break legitimate table names containing dots
on platforms like SQLite. By removing this method and letting DBAL handle
the platform-specific table name formatting, we achieve consistent behavior
across all platforms while fixing the schema filtering issue.
Testing confirms that removing this method works correctly: on schema-aware
platforms, qualified names are properly filtered, and on non-schema
platforms, table names are already unqualified by DBAL.
Fixes#1487
0 commit comments