And, also, Is the error still the same?
Cannot create any index
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 2: Process
Yes
Rank 2: Process
It seems like I cant use indexes with names that I used before the update and that across collections.
Rank 2: Process
But I dont really know 😄
Sometimes that indexes wasn't deleted
Rank 2: Process
Cool and now? 😂
Rank 2: Process
How can I delete them?
For that you'll need to access your database directly
Rank 2: Process
And why cant I create an index with the same name in a new collection?
Rank 2: Process
Ok nvm
Rank 2: Process
That works
Rank 2: Process
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
Rank 2: Process
How can I access this database?
Rank 2: Process
I mean its closed from public access
Rank 2: Process
Or not?
I've created a gist that explains the process
https://gist.github.com/byawitz/885510a4d9789e97424337e9472276d7
Rank 2: Process
Hmmm
Rank 4: Virtual Machine
Depends of your version, you can also use database api : https://appwrite.io/docs/server/databases?sdk=nodejs-default#databasesDeleteIndex with rest or graphql
Rank 2: Process
It may be that you are not allowed to create an index that has the same name as an attribute
Rank 2: Process
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.
Rank 4: Virtual Machine
Don't know, you need to try that
Rank 2: Process
Ok no that also not the case