[SOLVED] 500 error after extending enum with a new value
- 0
- Resolved
- Self Hosted
- Databases
- General
I have this enum with these possible values: client, coach, manager and I added a new value: coach_manager. Updating the enum went fine but if I now try to create a document with this new coach_manager value I get an 500 error back from Appwrite.
When I delete the attribute and recreate it with coach_manager as a value I don't get a 500 error. This isn't a solution for me because data is removed when I delete the attribute.
Are you on cloud or self hosting?
The problem with adding a value is a known issue: https://github.com/appwrite/appwrite/issues/5595
Hm I did see that issue but didn't know it was the same. So if an enum with a bigger length already exists I should be able to extend the enum without any issues?
[SOLVED] 500 error after extending enum with a new value
Recommended threads
- TEAM INVITE
There is a problem with the team invitation. When a user invites other users, that time, the newly created email address they don't get the invite link and old ...
- I'm getting an error on the console "j?....
On my self hosted instance version 1.8.1 the console is giving me this error when trying to view the rows for a table I recently created. My application is read...
- local build `composer installer:dev` iss...
setup - dev container (default linux universal) WSL (test with gh codespace too) - php 8.5.7 - all extensions installed - `composer install` fine - `composer...