sezaru
Is there support for using Postgres ENUM with Ash.Type.Enum?
I do know that you can do that if you create the migration yourself like it is done in this commit: chore: test enum types · ash-project/ash_postgres@a6577d5 · GitHub
But, the question is more if there is now support for it in the migration layer.
Basically, I would like to be able to create an Ash.TypeEnum and ash_postgres would handle the migration to create the type, add new values, remove old ones, etc.
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Schultzer
Postgres Enums can be annoying to maintain if you ever need to change a value etc. if it was me I would use a text column and something similar to Ecto.Enum, not sure if Ash has that, but I imagine it would.
sezaru
It has, but that became an issue if you have a huge table with a bunch of enums since that will increase the size of the table a lot. At the same time I don’t want to use integers since it decreases readability when querying the DB directly.
AFAIK, that annoying part was more prevalent before Postgres 9 since it could only add new values to the end of the enum. after that you can add in any position.
Also, needing a migration to add/remove values can be seen as something annoying, but it can also be seen as a advantage since it makes sure that no one can add wrong data to it.
Schultzer
True, worst of all is mostly in a distributed application, as the db is central, if you have a few applications running then you got a race condition, especially if you rarely have any low usage periods. But again YMMV, and I have no idea what constraints you’re working with.
garrison
Can you elaborate? Is there something wrong with
ALTER TYPE?Schultzer
No there is not something inherently wrong with it, although it does imposes constraints that can be completely avoided by having the logic live in the application, that way you can run two different version of your application without any downtime or performance degradation. As software is rarely set in stone.
Some of the constraints are complicating your migration and deployments due to table lock and consistency issues with application and database.
I’ve worked on codebases that leveraged Postgres Enums heavily, and it can be frustrating, especially when your application is the only writer to the database.