Music collection update fails due to SQL error about rompr HOT 4 OPEN

You can switch to SQLite without losing anything. First you need to create a metadta backup, using the plugin from the drop down menu above the info panel. Then switch to SQLite, rebuild your music colection, then restore the metadata backup.

from rompr.

Sigh. MariaDB is an absolute arse to work with. I'm also running that same version, on Rasberry Pi OS, and old_style_sql needs to be 0 for me - which makes it use the format of SQL that is causing you that issue. There is no consistency in versioning so there's no way I can make it work on every system.
Is there some reason you need to use mariadb? Unless you have an enormous music collection SQLite is always better - it's faster and uses less resources. If you really need an SQL server I can only suggest you use MySQL instead - they have a deb repo here https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/

from rompr.

I mean for me, using the old_style_sql=1 works, so no need to fix something for me (until this is deprecated). From your documentation I already realized that you are not happy about mysql/mariadb. I would have switched already but I am not sure what I would loose upon using a clean sqlite database.

Others face the same issue and use the following code to enable the alias in insert duplicates:
sqlalchemy .

from rompr.

Yes it happens here.

Debian (raspbian) 12.4
ii  mariadb-server-10.5                              1:10.11.4-1~deb12u1 
rompr 2.10

I switched to Sqlite, and this is fixed. At least this should be documented.

from rompr.