mlen
I seem to be stuck on some basic Ecto logic.
my Ecto version is 3.7.1
Given some schema:
schema :users do
field :name, string
field :zone, Ecto.Enum, values: ["Zone A": 1, "Zone B": 2, "Zone A and B": 3] # stored as integer in db
..
end
FYI: I don’t want to use composite types of :array, neither :string type for the zone.
Then when I do query the data:
# simplified for brevity
from(
u in Users,
select: [:id, :name, :zone],
where: [name: ^some_name]
)
|> Repo.all()
Each user object’s zone is shown as atom:
%MyApp.Users.User{
__meta__: ...,
id: 1,
name: "User A",
zone: :"Zone A" # I need this as integer
}
How do I make Ecto return the corresponding ids for zone field?
The reason I need that is later in the code I’m trying to create two list of users (with one db query), like so:
users = Users.get_all_active_users()
users_zone_a = Enum.reject(users, fn u -> u.zone == 2 end)
users_zone_b = Enum.reject(users, fn u -> u.zone == 1 end)
Any help greatly appreciated 
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
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
- #ai
- #ecto-query
- #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!
Practical resources that improve the lives of professional developers.
**Building the future of software with AI, trust, and human connection.**
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
krasenyp
That’s the idea of the enum in this case, to separate the presented value from the persisted one. What I would advise is to create a helper module which can encode and decode integers to and from
:"Zone A",:"Zone B"and so on. You should do the encoding/decoding at the “points” where your code interacts with the external word e.g. HTTP endpoints, database. This would allow you to work only with meaningful values and your comparisons will work.mlen
I realised (during breakfast..) that I could filter by the atom instead
e.g.
Not ideal but it works. Probably would be wise to have some encode/decode helper for those so it’s not spread all over the codebase.
LostKobrakai
The whole idea of
Ecto.Enumis to not spread the persisted value (the integers in your case) all over the codebase. You’re expected to use the atoms wherever you interact with the field, not the integers. Otherwise you could just use an:integerfield to begin with.But also there’s
Ecto.Enum.mappingsif you want to map between the representations.