-
Notifications
You must be signed in to change notification settings - Fork 4k
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: Limbo Attribute if Related Collection is Deleted #6012
Comments
Hello @stnguyen90, could you please assign this issue to me. Thanks |
Assigning it to you. |
Thanks, will start working on it by tomorrow. |
Raised the MR, kindly review. Thanks |
fix: delete attribute even if related collection does not exist This pull request fixes an issue where deleting an attribute from a document would fail if the related collection did not exist. This could happen if the collection had been deleted since the attribute was created. |
PR created |
👟 Reproduction steps
👍 Expected behavior
The attribute gets deleted
👎 Actual Behavior
Attribute is stuck at deleting:
appwrite-worker-databases logs:
Discord Thread: https://discord.com/channels/564160730845151244/1141837364575076462
🎲 Appwrite version
Version 1.3.x
💻 Operating system
Linux
🧱 Your Environment
Appwrite 1.3.8
👀 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: