Testing against MariaDB 11.8 for https://github.com/nextcloud/server/…

[nickvergessen]

…issues/51596

[kapcake]

As mentioned here #1252 (comment), the reason of the incompatibility with 11.8 is that vector is now a reserved keyword, but also the column name for table recognize_face_detections.

[marcelklehr]

Mmh, does that mean we need to rename the column, or can this be worked around by quoting the column?

[kapcake]

Honestly, I don’t know how quoting the column could be done in the db framework. I haven’t looked into that, and I didn’t spend a lot of time understanding the code. If it’s possible, that could be a workaround, but I don’t know if it’s a good solution in the sense of maintainability.But I see that changing the name is not something done easily either.On 27 Jul 2025, at 09:04, Marcel Klehr ***@***.***> wrote:marcelklehr left a comment (nextcloud/recognize#1295) Mmh, does that mean we need to rename the column, or can this be worked around by quoting the column? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[nickvergessen]

I guess rename (prefix) is easier and less problematic, because the missing quoting would be required in the migration schema logic of Doctrine DBAL etc.

1. Change column name in existing migration to fix new installs
2. Create a new migration that creates it if it does not exist yet
3. In the Post method copy data from old to new, if both columns exist
4. Create a new migration that deletes the old column if it exists