LSylvester
I have a query I want to run on a user object. I’m using Select to reduce the throughput from the database. Each user has a many to many relationship with departments. What I want to do is return a list of the department id’s in the select. So far, I have this:
context
|> join(:left, [u], ud in assoc(u, :user_departments))
|> select([u, ud], %{
id: u.id,
name: u.name,
email: u.email,
...
departments: ud.department_id
})
There are a lot more items called in my actual query. Obviously, the above fails because it returns only one id and errors if more than one are returned.
I’ve tried group_by, but unsuccessfully. Has anyone got a good example of this? I can’t find any Googling.
Thanks
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
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
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
idi527
Can you post the errors?
I think you can either use a
preloadin the query which will still be a join but it will collect the returned rows into some parent struct (user in your case, it seems), or use aRepo.preloadwhich would avoid a join but rather make a second request.How to Query a User with has_many Post in Ecto might be relevant.
LSylvester
I get a “field
departmentsinselectdoes not exist in schema” or “fielduser_departmentsinselectdoes not exist in schema”, even though the User schema has ahas_manyassociation touser_departmentsand amany_to_manyassociation todepartments.LSylvester
Okay, so I guess the answer is I can’t streamline it with a select, but instead I have to return the whole schema and relationships. That’s disappointing, but at least I can associate it with its SQL counterpart, now.
Many thanks @idi527, for your help.
idi527
I think you can write an ecto query that won’t require you to return unnecessary data …
MrSidecar
Yes, you can streamline the fields of the association.
try something along these lines (assuming a User and a many_to_many relation to departments):