-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
🐛 Bug Report: Recreate Same Name Relationship Attribute Only Self-Hosted #8116
Comments
Also tested on Windows 10. Bug causes problems here too |
Hey, I am Tanu Sharma having 2 number of exp in backend development, can I take this issue up. |
@SafakB, thanks for creating this issue! 🙏 Let's continue troubleshooting in https://discord.com/channels/564160730845151244/1239545933839073301 |
I'll be sharing a status update When I check via MariaDB, I see that the column has not really been deleted Database worker logs after relationship rebuilding SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'blogCategory' There are also remnants in the
|
The fix for this should be released in 1.5.6 which has #8080 |
👟 Reproduction steps
The error occurs after deleting the existing relationship attribute and adding it again with the same name.
Relationship Settings
Steps
I found this
After step 3, in the background the attribute is deleted from the list, but the attribute values remain in the rows
👍 Expected behavior
Deleted relationship should be able to be added again with the same name
👎 Actual Behavior
After adding a relationship, it gives a “Failed” warning. The process is not completed.
Error only occurs in Self-Hosted
Our Live Server 1.5.5 [ ❌ Not working]
Our Test Server 1.5.5 [ ❌ Not working]
Zero installation 1.5.5 [ ❌ Not working]
Cloud [ ✅ Working]
🎲 Appwrite version
Version 1.5.x
💻 Operating system
Linux
Windows 10 (Edited)
🧱 Your Environment
Used Appwite 1.5.5
The bug is not dependent on any SDK
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: