
And, also, Is the error still the same?

Yes

It seems like I cant use indexes with names that I used before the update and that across collections.

But I dont really know 😄

Sometimes that indexes wasn't deleted

Cool and now? 😂

How can I delete them?

For that you'll need to access your database directly

And why cant I create an index with the same name in a new collection?

Ok nvm

That works

But only in a completely new collection created after the update

Mmm, maybe something got mix over there

If you'll connect to your database you can see all the indexes each collection has, check if you see some old collection index

How can I access this database?

I mean its closed from public access

Or not?

I've created a gist that explains the process https://gist.github.com/byawitz/885510a4d9789e97424337e9472276d7

Hmmm

Depends of your version, you can also use database api : https://appwrite.io/docs/server/databases?sdk=nodejs-default#databasesDeleteIndex with rest or graphql

It may be that you are not allowed to create an index that has the same name as an attribute

But if appwrite knew that the index exists it would display it in the console or am I wrong?

Yes, make sense, That why it's better to try with direct connection.

Don't know, you need to try that

Ok no that also not the case
Recommended threads
- 404 errors after 7 Days
Local hosted Appwrite via docker. Last version and current version. After exactly 7 days Appwrite stops working. I get 404 route not found, cannot access anyth...
- my database attribute stuck in processin...
when i created attributes in collection 3 of those attributes become "processing", and they are not updating, the worst thing is that i cant even delete them s...
- Forever Processing Issue
I encountered an issue when creating attributes in the collections . if you create an attribute of type string for example and choose a size of 200 or 250 or a...
