Upgrade to new version 2.19 #1440

New Issue

OVERLORD · 2025-10-09T17:15:20+03:00

OVERLORD commented

2025-10-09 17:15:20 +03:00

Originally created by @gkl1368 on GitHub.

Running migration 20210311190243
BitWarden | Executing migration script 20210311190243/up.sql
BitWarden | [2021-03-15 10:39:46.977][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError.
BitWarden | [CAUSE] QueryError(
BitWarden | DatabaseError(
BitWarden | __Unknown,
BitWarden | "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'NOT NULL,\n password_hash BLOB,\n password_salt BLOB,\n password_iter...' at line 11",

I have this problem when I upgrade to 2.19，I use docker with MySQL. It work ok before update.

Originally created by @gkl1368 on GitHub. Running migration 20210311190243 BitWarden | Executing migration script 20210311190243/up.sql BitWarden | [2021-03-15 10:39:46.977][bitwarden_rs::util][WARN] Can't connect to database, retrying: DieselMigError. BitWarden | [CAUSE] QueryError( BitWarden | DatabaseError( BitWarden | __Unknown, BitWarden | "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near \'NOT NULL,\n password_hash BLOB,\n password_salt BLOB,\n password_iter...\' at line 11", I have this problem when I upgrade to 2.19，I use docker with MySQL. It work ok before update.

OVERLORD closed this issue

2025-10-09 17:15:20 +03:00

OVERLORD commented

2025-10-09 17:15:22 +03:00

@dani-garcia commented on GitHub:

I think MySQL doesn’t allow using key as a column name, might need to rename it to akey like with the user table.

We’ll need to modify the existing MySQL migration and create two new ones for the other two.

@dani-garcia commented on GitHub: I think MySQL doesn’t allow using key as a column name, might need to rename it to akey like with the user table. We’ll need to modify the existing MySQL migration and create two new ones for the other two.

OVERLORD commented

2025-10-09 17:15:22 +03:00

@gkl1368 commented on GitHub:

After upgrade to new docker image, it works. Thanks.

@gkl1368 commented on GitHub: After upgrade to new docker image, it works. Thanks.

OVERLORD commented

2025-10-09 17:15:22 +03:00

@gkl1368 commented on GitHub:

I think MySQL doesn’t allow using key as a column name, might need to rename it to akey like with the user table.

We’ll need to modify the existing MySQL migration and create two new ones for the other two.

OK. I will wait for your modify. Thanks

@gkl1368 commented on GitHub: > I think MySQL doesn’t allow using key as a column name, might need to rename it to akey like with the user table. > > > > We’ll need to modify the existing MySQL migration and create two new ones for the other two. OK. I will wait for your modify. Thanks

OVERLORD commented

2025-10-09 17:15:23 +03:00

@BlackDex commented on GitHub:

Please check your database Collation.
See: https://github.com/dani-garcia/bitwarden_rs/issues/1305#issuecomment-774558466 for some info.
This could cause some strange issues when it has a different collation, it could very well be this issue.

@BlackDex commented on GitHub: Please check your database Collation. See: https://github.com/dani-garcia/bitwarden_rs/issues/1305#issuecomment-774558466 for some info. This could cause some strange issues when it has a different collation, it could very well be this issue.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1440