Replies: 4 comments 6 replies
-
@mattiaz9 Hey, are you on 2.0? I think issues with changing select / group fields values are related to the old drizzle version that's not currently updated there (it is on 3.0 beta). |
Beta Was this translation helpful? Give feedback.
-
Amen! I'm having this issue in v3 beta also. In addition, I have a select field nested in a block that's nested in a Pages collection fields. I got an error saying the enum name was too long.
|
Beta Was this translation helpful? Give feedback.
-
There is an ongoing issue that drizzle knows about. We've been looking at ways to solve the underlying problem. I do think that enums offer some benefit over making everything a text field. Until it is fixed what you can do to workaround the issue is add If we decide to remove the use enums, it would be a flag to opt-out of this behavior which I totally understand might be helpful to some. |
Beta Was this translation helpful? Give feedback.
-
I also got this error in v3 beta.111 It looks, like it is related to ordering items in enum. In my case, I have changed options' ordering for select type field, and seems it wants to add a new enum label, that already exists. Related issue from Drizzle drizzle-team/drizzle-orm#2389 |
Beta Was this translation helpful? Give feedback.
-
Enums are kind of a mess. Changing an existing enum causes several problems and I'm not even sure what advantages could possible have for a cms.
Every time a new select field is added, a new enum is created every time, even when the same values are reused across multiple entities.
I just tried to remove a value from a select options and now it's all broken. I keep getting the error
enum label "zoom" already exists
, even after deleting and recreating the field.It just makes no sense to me to have such a constrained type. It creates more problems than it solves.
Beta Was this translation helpful? Give feedback.
All reactions