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
- Current User is Not authorized
recreating same Thread
- Account Status
Hello! I'm a student and am in the GitHub Student Organization, and according to GitHub, I am recieving pro membership via the Student Dev Pack. However, when I...
- Refund Request - Just purchased 2 mins a...
Hello Appwrite Team! I am a student and like 2 minutes ago I purchased Appwrite Pro ($15) because I had reached a limit on the number of attributes in a collect...