Not sure what the intended purpose of disabling DQS by default is, but it is already breaking emby-server and sonarr. Sonarr reports database corruption and emby-server fails to execute some database operations.
Created attachment 240493 [details] Emby Log
Created attachment 240494 [details] Sonarr Log
As emby-server maintainer, I'm taking this upstream how we will deal with it. Ideally the source code gets adapted.
For now I didn't have much time to look at Sonarr and see if I can find where the SQL queries are and if we can fix them. I did however create an issue in the Sonarr Github https://github.com/Sonarr/Sonarr/issues/5464 I hope to find some time over the weekend to look at this some more.
Sonarr is not going to fix it in sonarr v3 (current stable) and in sonarr v4 (currently in beta) this is not a problem. While I agree that disabling DQS is in line with upstream sqlite3, and probably the way to go, the easy way out here is to enable it again for the port, to help downstream ports.
Note that the DQS feature can be enabled on a per connection basis with code like this: sqlite3_db_config(db, SQLITE_DBCONFIG_DQS_DDL, 0, (void*)0); sqlite3_db_config(db, SQLITE_DBCONFIG_DQS_DML, 0, (void*)0); I suppose a patch that just sets up these options when connecting to the database should not be too hard to come up with.
Just confirmed: the multimedia/tautulli port is also affected. Updating sqlite3 in my tautulli jail breaks it: [tautulli.vanbaak.eu] [1/1] Upgrading sqlite3 from 3.40.1,1 to 3.41.0,1... Log after this upgrade: ==> /var/db/tautulli/logs/tautulli.log <== 2023-03-06 11:11:20 - ERROR :: ('CP Server Thread-7',) : Tautulli Database :: Database error: no such column: movie 2023-03-06 11:11:20 - WARNING :: ('CP Server Thread-7',) : Tautulli DataFactory :: Unable to execute database query for get_home_stats: top_movies: no such column: movie. Rolling back the sqlite3 upgrade fixes it
Created attachment 240620 [details] tautulli log
Reported issue with upstream tautulli: https://github.com/Tautulli/Tautulli/issues/2015
(In reply to Matt from comment #2) sonarr fixed the issue upstream, update to the port is here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270004
DQS is now disabled by default. Can we close this ticket?
(In reply to Robert Clausecker from comment #11) ok by me.
The DQS option has been temporarily reinstated to give ports some time to fix their queries. It will be turned off permanently on 2024-01-01.