Attribute Limit Exceeded - Again ;-) - Threads

Hi @all, I migrated a table with around 50 attributes from MySQL to Supabase and like to migrate that to appwrite now.

My freelancer managed to create that collection somehow in the past, but I have no clue how he did that.

Now I need to adjust some sizes.

I am running in this annoying error "Attribute Limit Exceeded".

I can not even recreate the collection the freelancer did before. Not with the WebUI nor with the Python SDK.

I found a post from last year telling something about VARCHAR and TEXT, but appwrite only has the string type (beside URL, Email ....) But not string or text or some sort. So I do not understood how this can be helpful.

The MariaDB should be able to handle that table because I could create it on MySQL 5.5 InnoDB before.

So what can I do? Is there some sort of hack that my freelancer used or maybe some official way of creating the collection?

TL;DR

Developers faced attribute limit exceeded error while working on attribute sizes in a project. After some discussion, they figured out that setting long string fields to TEXT and adjusting attribute sizes can solve the issue. They also shared insights into optimizing the database schema for efficient querying. Additionally, developers discussed the limits and conversion of attributes to int or float types to manage space effectively.

TypeScript

 - width: string (Größe: 111111)
 - length: string (Größe: 111111)```
can be stored as int, no?

How you wanna query them?

That was only, because I could not even add a float attribute. So I assume that he tried to made it this way.

After 19 attributes I can not even add another one. So setting all other values to 111111 made it worked at least with TEXT. Otherwise no add attribute could be added.

Sorry for that bad english grammar. I hope you understood what I meant 😄

Don't worry I do.

I would just clean them all up before storing them. I know it's a pain in the arse but you will thank yourself later.

With your support I now have the key to set long string fields to TEXT, so that space is freed to add smaller attributes. So now it would make sense to clean the schema. Before that I could not add all attributes. The best way is that I now understand how that is handled with appwrite and having a switch to go from VARCHAR to TEXT.