-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Primary index name "id" for table "oc_forms_v2_uploaded_files" collides with the constraint on table "oc_e2e_encryption_lock". #2346
Comments
@RainerEmrich do you have the e2e app installed and updated to the latest version? I saw that there are several changes in the DB table schema for their app related to the indexes. Also there's this open issue I linked. So I'm unsure, if we can do anything here. The new table is created just like all our other tables. |
No, I don't have any end to end encryption app installed. |
Ok, then this is the problem... you had it installed in the past and there are some leftovers in your database that haven't been upgraded to the latest schema version. Please try to remove all tables starting with |
I only have oc_e2e_encryption_lock table in the database. So i will remove it and try again. |
Short summary. I don't know why, but I had the oc_e2e_encryption_lock table in some of my nextcloud instances, but not in all. |
@RainerEmrich thanks for the feedback and glad you could fix your issue 👍🏻 |
Describe the bug
Updating tthe Forms app to Version 4.3.0 gives the error:
{"reqId":"6xRpvk0LJJZu7sdEXy2W","level":2,"time":"2024-10-05T04:50:55+00:00","remoteAddr":"","user":"--","app":"forms","method":"","url":"--","message":"Primary index name "id" for table "oc_forms_v2_uploaded_files" collides with the constraint on table "oc_e2e_encryption_lock".","userAgent":"--","version":"29.0.7.1","data":{"app":"forms"}}
To Reproduce
Steps to reproduce the behavior:
Updating Forms to version 4.3.0
Expected behavior
There should be no database index collision.
Nextcloud (please complete the following information):
The text was updated successfully, but these errors were encountered: