Deleted a column but can't reuse name

I deleted a relationship column because I was having trouble with deleting a row and I was suspicious of the relationship. After deleting the column the row was successfully deleted, however now I can't add the relationship column back since it says the column name is already being used.

Deleted a column but can't reuse name

https://discord.com/channels/564160730845151244/1239545933839073301

Which version are you using? In 2024 I had the same problem, it was solved with an update. I sent the link, is it a similar event?

This is on cloud, so I can't update anything

can you share exact steps including what relationship attributes you had so we can reproduce the issue?

So I had a two-way one-to-many relationship and I tried deleting a row that had this relationship filled, but I kept getting an error saying it wasn't able to delete the row. So I deleted the relationship attribute and then was able to delete the row. Then I tried adding the relationship back and I get this error.

I just tried to recreate the situation but now I can't delete the new rows I created. The rows don't have any relationships so I'm not sure what is going on. I can give you my project ID if you want to check it out.

Hey Steven, any progress on this? I switched from the relationships to just using document Ids, but I'm getting blocked. When trying to create a new row I'm getting AppwriteException('Invalid query: Attribute not found in schema: field'), but I'm not providing field in my query. It seems like there are just extra attributes somewhere in my database that I don't have any method of deleting. If possible, could someone delete all the relationship attributes that are still in my project? I removed them all myself but it seems like there's some lingering.

what SDK are you using and what version is it? What's your project ID, database ID, collection ID, and column that is having issues?

I was using the Python SDK, but I ended up fixing the issue by migrating my database to a self hosted instance then migrating back. This seemed to have cleared all the 'ghost' attribute errors I was getting. Do you still want the IDs?

if it's not happening anymore, i probably won't be able to find out details looking at it in the backend