Chromium needs virtual tables in order to use FTS. I'm not sure why CREATE/DROP VIRTUAL TABLE have been disabled in WebKit since forever, but it seems to me like these instructions don't pose any security threat and should be allowed.
Created attachment 48602 [details] patch
Created attachment 48849 [details] patch Oops, uploaded the wrong patch.
If there is no reason to disallow them, why filter on moduleName? Maybe just denyBasedOnTableName(tableName) and not test the 'moduleName' at all.
Interesting. If there's no user demand for direct creation of virtual tables, I'd be tempted to play it safe, and restrict them to internal usage by fts2.
Comment on attachment 48849 [details] patch ok.
Landed as r54990.