The RDBMs classes treat table names as application-supplied rather than user-supplied, since it does not make sense for the user to be able to blindly pick the schema (likely causing query errors). Table names are generally non-problematic [a-zA-Z0-9_]+ strings. However, they still should be escaped as identifiers, since they might have problematic characters. Fix the SQLite backend to apply escaping here, similar to MySQL and Postgres. Fix incorrect use of tableName() in DatabaseSqlite::fieldInfo(). It should work the same as in tableExists(). Bug: T72510 Change-Id: I3713f81e6e1eca84cc51c12c9307d4c5dc737043 |
||
|---|---|---|
| .. | ||
| DatabaseMysqlTest.php | ||
| DatabasePostgresTest.php | ||
| DatabaseSqliteTest.php | ||
| DatabaseSqliteUpgradeTest.php | ||