Chrome 93 ignoring SQLite Triggers-CodePudding

Since I updated Chromium from version v91 to v93 it is no longer respecting the following trigger I cretated inside the history (which is a sqlite3 file) in the user profile:

CREATE TRIGGER IF NOT EXISTS no_urls BEFORE INSERT ON urls FOR EACH ROW BEGIN SELECT RAISE(ABORT, ''); END;

This trigger used to work fine preventing Chrome from saving any history on my profile.

Now, since v93 it somehow bypasses that trigger and keep storing the urls (history).

Is there a trick to make Chrome respect that trigger and do not save history?

CodePudding user response：

I'm reasonably sure the answer is: You can't do this.

From a recent check in to the source code to Chromium:

// The use of triggers is discouraged for Chrome code. Thanks to this
// configuration change, triggers are not executed. CREATE TRIGGER and DROP
// TRIGGER still succeed.
err = sqlite3_db_config(db_, SQLITE_DBCONFIG_ENABLE_TRIGGER, 0, nullptr);

They appear to be explicitly disabling the SQLite trigger functionality, with no option or configuration around it.

Short of convincing them to change this behavior, or creating a custom build, I don't see any way around this.