script
Select merge with joins and count
I am using select merge to build the query dynamically. But i can’t understand why ecto give me these errors.
this is the query
Ecto.Query<from r0 in Room,
select: merge(f0, %{"$aggregate": %{"$count": %{^"floor" => count(f0.floor)}}})>
this is the code:
from(
r in rooms,
select_merge: %{"$aggregate": %{"$count": %{^field => count(field(r, ^atom_field))}}}
)
and I got this error:
struct Room `does not have the key :"$aggregate".
And if i use it in joins:
this is the query:
from(
h in Hospital,
right_join: r in "rooms",
on: h.id == r.hospital_id,
where: r.name == ^"room 1" and ^true,
select: merge(h, %{^:rooms => map(r, [:name, :purpose, :description])})
)
this is the code:
from(
[h, ..., r] in hospital,
select_merge: %{
^String_to_atom(rooms) => map(r, [:fields])
}
)
the error is:
Postgrex expected a binary, got :rooms. Please make sure the value you are passing matches the
definition in your table or in your query or convert the value accordingly.
If i change the rooms to string it will throw the same error i am getting in the count query.
May be I am missing something very obvious here.
Any help will be much appreciated
Thanks
Most Liked
LostKobrakai
If you use from x in Schema ecto will implicitly expect you want …, select: x. This will return a list of %Schema{} structs, so each field you select must be part of the struct.
script
Thanks for your reply.
I figured out the problem.
In the select merge in the last paragraph . It states that you have to supply the map or struct to merge on. If you supply struct it’s value must be present in the key in the merge map. Thats why i am getting these errors.
By supplying an empty map or selecting fields from the struct and then pass them to select merge solved the problem.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security









