From ff8d58c5d13259e5e8489a0a194672a7a65fbdf5 Mon Sep 17 00:00:00 2001 From: Daniel Pan Date: Mon, 11 Mar 2024 12:36:56 +0800 Subject: [PATCH] Update upgrade_notes_for_11.0.x.md --- manual/upgrade/upgrade_notes_for_11.0.x.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/manual/upgrade/upgrade_notes_for_11.0.x.md b/manual/upgrade/upgrade_notes_for_11.0.x.md index 280496be7..611c9dbdd 100644 --- a/manual/upgrade/upgrade_notes_for_11.0.x.md +++ b/manual/upgrade/upgrade_notes_for_11.0.x.md @@ -36,11 +36,13 @@ If you use OAuth authentication, the configuration need to be changed a bit. If you use SAML, you don't need to change configuration files. -### Deprecating SQLite Database Support +### Dropped SQLite Database Support -Seafile 11.0 deprecates using SQLite as the database. There are several reasons driving this change: +Seafile 11.0 **dropped** using SQLite as the database. It is better to migrate from SQLite database to MySQL database before upgrading to version 11.0. -* Focus on collaborative features - SQLite's limitations make advanced concurrency and locking difficult, which collaborative editing requires. Different Seafile components need simultaneous database access. +There are several reasons driving this change: + +* Focus on collaborative features - SQLite's limitations make advanced concurrency and locking difficult, which collaborative editing requires. Different Seafile components need simultaneous database access. Especially after adding seafevents component in version 11.0 for the community edition. * Docker deployments - Our official Docker images do not support SQLite. MySQL is the preferred option. * Migration difficulties - Migrating SQLite databases to MySQL via SQL translation is unreliable.