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
- SELF HOSTING ISSUE, DATA NOT MIGRATING T...
Hey, devs, I recently tried to migrate my cloud instance to a self hosted version but my data is not transferred fully only the table structure is transferred ...
- No Document ID?
Hi I have a self hosted appwrite. My documents get a document ID but are not visible in the console. I don't know why this happens and how to fix this
- AppwriteException: Invalid query: Query ...
```js console.log(typeof interaction.user.id) console.log(interaction.user.id) const user_check = await TablesDB.listRows({ databaseId: "db", ...