In SQLite 3.25.2, the authorizer is called for the internal functions
sqlite_rename_columns, sqlite_rename_table and sqlite_rename_test. Either
the description above is misleading, or the code does not behave as
This can impact existing deployments, because sqlite_rename_columns and
sqlite_rename_test have not showed up in authorizer calls for 3.24.0.
sqlite_rename_columns is tied with new functionality, but
sqlite_rename_test is used for table-renaming functionality that was
supported before. Example: I've noticed this problem while upgrading SQLite
In case it helps prioritize, this bug is not urgent for Chrome. We'll just
update our authorizer to allow the new internal functions.
I suspect the solution will involve more blocks like the ones introduced in
the diff I referenced above. Blocks below for convenience.