© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
Drizzle TeamDT
Drizzle Team•3y ago•
2 replies
Murk418

Renaming pgEnum results in truncation?

I've been using drizzle with MySQL for a while, but I'm new to PG. I encountered an error where I had two different enums with the same column name
status
status
on two different tables, and Drizzle just chose one of the enums for the migration and didn't include the other. I was able to solve this by just changing the column names to
project_status
project_status
and
comment_status
comment_status
(which might be better anyways, so its fine). But when pushing that migration I got a new warning saying that changing the column datatype from
status
status
to
project_status
project_status
would truncate the table, even though neither the enum datatype itself nor the default value had changed at all. Just the name.

So I guess I'm just wondering if anyone has encountered anything similar, and if you were able to find a solution, or if this might be worth opening issue over. Or rather if I just clearly have a misunderstanding of how PG works, please let me know lol. Thanks in advance!
Drizzle TeamJoin
The official Discord for all Drizzle related projects, such as Drizzle ORM, Drizzle Kit, Drizzle Studio and more!
11,879Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

pgEnum in multiple tables
Drizzle TeamDTDrizzle Team / help
3y ago
PostgreSQL RQB truncation
Drizzle TeamDTDrizzle Team / help
3y ago
PGEnum -> Typescript Enum
Drizzle TeamDTDrizzle Team / help
3y ago
PgEnum Error on relation
Drizzle TeamDTDrizzle Team / help
15mo ago