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.
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...
Recommended threads
- TablesDB `updateRows` returns `database_...
Hi Appwrite team! I’m seeing a strange issue with TablesDB bulk row updates on a self-hosted Appwrite instance. **Environment** - Appwrite self-hosted `1.9.0` ...
- Update row sheet not loading
After right clicking a row header and click update, the sidebar fails to load (never-ending skeleton)
- DB Relational Table Request
Hi, I'd like to suggest a rewording of the relationships between tables. - Current wording: storeOperatingDays can contain one storeId ...