Drizzle-Kit pushing not respecting enum changes?
Does drizzle-kit push not respect enum changes? Currently dealing with something that makes development annoying :(
I have this enum in my schema and when I add, edit, or remove enum values it won't push to the database because existing values in the database contain them e.g. "messageEdit" already exists
I'd expect drizzle-kit to just alter the rows correctly instead of forcing me to do this manually via SQL or repeatedly drop my dev db
1 Reply
specific error for clarity:
error: invalid input value for enum action_log_type: "messageEdit"
I haven't tried using migrations to test this but I don't want to create unnecessary migrations that are meant for prod, so any migrations made would need to be deleted if I had to repeatedly generate & migrate for development