acrolink
Hi,
Table A:
Dishes: id and name fields.
Table B:
Users: with a field called favorite_dishes holding an array of id’s (of dishes).
Is there an Ecto way to treat this as an association ? e.g. for pre-loading ?
How to best do that. I am using PostgreSQL.
Thank you
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
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 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
benwilson512
In general it is better to use a join table instead of an array of integers. This ensures you can use foreign key references, and will index better. There is no built in support for driving associations via an array of integers. If you’re just doing has many then the associated table should hold the parent id. If you need M:N associations, use a join table.
acrolink
Thanks. Actually, this is only part of the story. There will be a Restaurants table, each serving various dishes. There will be joins across them e.g. user <> dishes he likes <> restaurants serving those dishes. But since PostgreSQL supports those array of integer fields, I thought that could ensure good performane and make it easy to look up the associations.
benwilson512
I would definitely start with the “normal” way of modeling this in Postgres which would be via join tables, and then optimize when you’ve got millions of rows and you have specific access patterns you know you need to optimize for.
Hermanverschooten
I definitely agree with @benwilson512, not only are you complicating things, but you lose all referential integrity that way.
FlyingNoodle
We have done this at work and we are in a world of pain because of it.
Don’t do it.
D4no0
What kind of database size we are talking about?
If it’s under 200GB for a table, I wouldn’t even bother with any optimisations besides indexes on most used columns.
dimitarvp
Do it the boring and the seemingly-inefficient way, run it in production, measure, then think of optimizing it.
Don’t put the cart before the horse.