steps to reproduce.
- create host collection and target collection.
- create a
many to onerelationship attribute from host -> target. - delete the target collection as a whole.
- but the
many to onerelationship attribute that we created still exist.
is this the expected behavior?? or is this a bug for me only??
and also, i cannot delete that relationship attribute. its stuck on "deleting" . i cannot recreate relationship in the same attribute name to another collection either.
in the appwrite console. there are no errors. and in UI console also, it shows attribute it succesfully deleted.
TL;DR
User has encountered an issue where deleting a related collection does not delete the relationship attribute. They have tried deleting the target collection but the attribute still exists. They are unsure if this is a bug or expected behavior. They also mention being unable to delete the relationship attribute and it being stuck on "deleting". No errors are displayed in the appwrite console. A GitHub issue is suggested to report the bug.Probably a bug. Would you please create a GitHub issue for this?
ya can cofirm this have happen and needed to delete whole collection
did issue related to got created? Else happy to create...