Deleting attribute: The maximum row size for the used table type, not counting BLOBs, is 8126.
That's also what I think 🙂 I've got the same yesterday and I removed an URL attrib (2000 chars) that solved my problem, even if I was far from reaching the limit.
Not sure if it's related but I'm heavily playing with the creation/deletion of attribs by scripting.
Weird as it's a MariaDB error and looking at the tables with Navicat doesn't show any big fields...
Did this error happen when you had the url attribute?
No when I tried to add a new 10chars attribute. Even an Integer one failed until I successfully removed the URL.
And also, adding some indexes display "failed" even if it works! Not sure if this is related.
"works" because the query works?
And now adding a attribute still fails?
In fact I thought my indexes were created but it really doesn't work, except sometimes for some
I delete my collection but I can try again
The url attribute could have been the problem. I don't think I can reproduce with the list you gave me if that wasn't the list of attributes you had when you were experiencing the problem.
If you can reproduce the problem, feel free to create an issue with the exact steps
Sorry can you clarify what you mean?
Thanks, I will try to reproduce it. Regarding the indexes, I thought the "failed" ones were really created but they don't show on the DB (in my Navicat MySQL client) so it really fails. Will try to reproduce too! Thanks for your help.
BTW, does the indexes need a unique key database-wide or only in their collection? Because I fail to create an index named index_4 (no other index with this key in the collection) but I can with index_44 (with same attribs and options)
Failed means the index wasn't created
Yes, this time I checked on Navicat. The logs show appwrite-worker-databases | Index already exists
So there are 2 places. If you see the index in the Appwrite Console, theres an index metadata. Then, there's the actual index created in the database
index_4 shows a failed tag, then I remove it (in Web Console), then I recreate it as index_44, it works, delete it again and retry as index_4 -> failed again.
And the database worker logs say index already exists?
Yes it does
Weird...I wonder if there's a ghost index or something...
@Gildas Quiniou Chiming in on this. Was this project migrated from earlier Appwrite versions?
Trying to see if this could be related to migration. While this doesn't help you solve your issue... would definitely help with us narrowing down the problem
Hi, no it is not a migration. I also recreated a brand new database from the latest (1.2) release. The only thing is I'm heavily playing with creating and deleting attributes and indexes with the API (scripted), not the Web console. I've a script that deals with reordering the attribs for which I clone attribs using temporary names to be able to finally recreate them in the expected order. Doing so I may stress the create/delete attribs API a little bit as I also need to loop until the actions go from "processing" to "available", could this be a reason?
hmm...if you can reproduce it reliably, you can share the steps so that we could troublesohot too
