From 6b1f96f64fcfa026ef26c52124cf85fed7013f15 Mon Sep 17 00:00:00 2001 From: David Tekan Date: Tue, 1 Feb 2022 12:14:46 +0100 Subject: [PATCH] error message, when running migration 20220117234911 --- Using-the-MariaDB-(MySQL)-Backend.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Using-the-MariaDB-(MySQL)-Backend.md b/Using-the-MariaDB-(MySQL)-Backend.md index 6715987..ee665ca 100644 --- a/Using-the-MariaDB-(MySQL)-Backend.md +++ b/Using-the-MariaDB-(MySQL)-Backend.md @@ -194,7 +194,7 @@ The version jump may have added new database columns. Upgrade vaultwarden using ## Foreign key errors, collation and charset -Because some data stored within the vault is either binary, or plain-text like mail addresses, user names or organization names which can contain Unicode characters you need to make sure the collation and charset of your database and tables is correctly set. If this is not the case, it could cause issues during updates which then generates messages like `Cannot add or update a child row: a foreign key constraint fails ...` +Because some data stored within the vault is either binary, or plain-text like mail addresses, user names or organization names which can contain Unicode characters you need to make sure the collation and charset of your database and tables is correctly set. If this is not the case, it could cause issues during updates which then generates messages like `Cannot add or update a child row: a foreign key constraint fails ...` or `Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126.`. To solve this you need to update/change the collation and charset of both the whole database and the tables it contains. You can do that by following and executing the following sets via your perfered SQL tool, or using the CLI.