I have once again nose-dived into the treeline while attempting to follow the official docs… I’m trying to stay positive here, but I am really feeling malnourished when it comes to nutritious examples. I would love some help clarifying the mystery presented on Ecto.Query — Ecto v3.14.0 dynamic = f…

author = params[“author”] author_selection = dynamic([p], p.author == ^author) Ecto.Query — Ecto v3.14.0 There’s where: … and or_where: … or where: (p.published == true or p.preview == true) and p.id > 100 Ecto.Query — Ecto v3.14.0 Ecto.Query — Ecto v3.…

Thank you, this is vastly more useful than what is currently in the docs. The join examples on the Query page frequently use where… there must be cases when it is equivalent to on? The “or” that was (is) specifically bothering me is in here: dynamic([p], p.is_public or ^dynamic) – why are we inte…

[image] fireproofsocks: The join examples on the Query page frequently use where … there must be cases when it is equivalent to on ? where is like in SQL just where. The on part in joins can be skipped for join: c in assoc(a, :comments), because by using the association between schemas ecto d…

Interesting. Thanks for the further clarifications! I’ve got it working now, it just ends up being pretty long. Have you ever tried to use a loop to define all filterable columns? Something like this: dynamic = false for column <- ["id", "state", "country"] do dynamic = if …

Nice. Ok, I see how to use the field() function now, thanks! Is there any way to dynamically set the operator? For flexibility, it would be really useful for CRUD searches and the like to be able to have a function that would allow the user to specify which operator to use for each field – the de…

[image] fireproofsocks: I have once again nose-dived into the treeline while attempting to follow the official docs… I’m not entirely sure what the point of commentary like this is. The Elixir community is still relatively small, and the docs and code that exist are almost always the work of …

Sorry, you’re right: there’s nothing positive in commentary like that. I apologize. I was writing from a point of extreme frustration and exhaustion. I would like to submit some examples once I can get things working.

[image] fireproofsocks: I was writing from a point of extreme frustration and exhaustion We’ve definitely all been there, and I understand. Thanks for the apology, and I’m sure that the docs will benefit greatly from your examples!

iex(1)> alias MusicDB.{Repo,Album,Track} [MusicDB.Repo, MusicDB.Album, MusicDB.Track] iex(2)> import Ecto.Query Ecto.Query iex(3)> dynamic_where = fn (album_id, params) -> ...(3)> default = dynamic([t], t.album_id == ^album_id) ...(3)> case params do ...(3)> %{name: name, value: value, op: :…

Dynamic Queries in Ecto

Questions & Help Questions

LostKobrakai June 26, 2018, 1:52pm 6

Enum.reduce can do that quite nicely (you need to aggregate the dynamic not overwrite it on each iteration).