Back

Deleting attribute: The maximum row size for the used table type, not counting BLOBs, is 8126.

  • 0
  • Databases
Gildas Quiniou
12 Mar, 2023, 23:17

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.

TL;DR
User is experiencing an issue with deleting attributes in the Appwrite database. They suspect it may be related to their scripted API actions involving attribute creation and deletion. Another user suggests checking if the project was migrated from previous versions. The conversation continues with discussions about ghost indexes, index metadata, and failed index creation. The user mentions that the issue seems to be related to the "url" attribute and that removing it solves the problem. They also mention that they are heavily playing with attribute creation and deletion through scripting. There is no solution provided in the thread.
Gildas Quiniou
12 Mar, 2023, 23:18

Not sure if it's related but I'm heavily playing with the creation/deletion of attribs by scripting.

Gildas Quiniou
12 Mar, 2023, 23:20

Weird as it's a MariaDB error and looking at the tables with Navicat doesn't show any big fields...

Drake
12 Mar, 2023, 23:21

Did this error happen when you had the url attribute?

Gildas Quiniou
12 Mar, 2023, 23:31

No when I tried to add a new 10chars attribute. Even an Integer one failed until I successfully removed the URL.

Gildas Quiniou
12 Mar, 2023, 23:33

And also, adding some indexes display "failed" even if it works! Not sure if this is related.

Drake
12 Mar, 2023, 23:36

"works" because the query works?

Drake
12 Mar, 2023, 23:36

And now adding a attribute still fails?

Gildas Quiniou
12 Mar, 2023, 23:44

In fact I thought my indexes were created but it really doesn't work, except sometimes for some

Gildas Quiniou
12 Mar, 2023, 23:45

I delete my collection but I can try again

Drake
12 Mar, 2023, 23:46

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

Drake
12 Mar, 2023, 23:48

Sorry can you clarify what you mean?

Gildas Quiniou
12 Mar, 2023, 23:50

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.

Gildas Quiniou
13 Mar, 2023, 00:03

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)

Drake
13 Mar, 2023, 00:06

Failed means the index wasn't created

Gildas Quiniou
13 Mar, 2023, 00:07

Yes, this time I checked on Navicat. The logs show appwrite-worker-databases | Index already exists

Drake
13 Mar, 2023, 00:11

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

Gildas Quiniou
13 Mar, 2023, 00:16

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.

Drake
13 Mar, 2023, 00:21

And the database worker logs say index already exists?

Gildas Quiniou
13 Mar, 2023, 00:24

Yes it does

Drake
13 Mar, 2023, 00:48

Weird...I wonder if there's a ghost index or something...

VincentGe
14 Mar, 2023, 15:46

@Gildas Quiniou Chiming in on this. Was this project migrated from earlier Appwrite versions?

VincentGe
14 Mar, 2023, 15:46

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

Gildas Quiniou
14 Mar, 2023, 16:17

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?

Drake
14 Mar, 2023, 16:19

hmm...if you can reproduce it reliably, you can share the steps so that we could troublesohot too

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more