You’re overthinking my response, I’m saying you literally can just leave out the from:
defp search(query, name) do
query
|> where([t], ilike(t.name, ^"%#{name}%"))
end
benwilson512
Author of Craft GraphQL APIs in Elixir with Absinthe
2
tenzil
here, you will get Item as _query, you can replace
from(query in Item) with (from i in query) and you can add where with a comma so the result would be
defp search(query, name) do
from i in query, where: ilike(i.name, ^"%#{name}%")
end
0
Kurisu
Note that this two query are not the same thing. the second query scope is just inside the from expression and it allows you to do things like.
from(s in schema, where: s.id == 10)
0
wolfiton
I am sorry to ask but where does the t come from in your code @benwilson512?
Any explanation will be appreciated.
Thanks
0
benwilson512
Author of Craft GraphQL APIs in Elixir with Absinthe
t is not a real variable, because where is not a function, it’s a macro. t is part of the syntax of the macro. Examples here: Ecto.Query — Ecto v3.14.0
The where macro basically just creates a t that you can use in the second part of where.
4
wolfiton
benwilson512
Author of Craft GraphQL APIs in Elixir with Absinthe
Yes. If you pipe a query struct into where, it grabs the schema you’re querying out of the query and makes it available as whatever variable you put in the list.
3
wolfiton
Kurisu
defp search(_query, name) do
query = from(query in Item)
query
|> where([t], ilike(t.name, ^"%#{name}%"))
end
this is the same as you’re writing
defp search(_query, name) do
Item
|> where([t], ilike(t.name, ^"%#{name}%"))
end
that’s why you’re escaping the query parameter to avoid the warning
0
wolfiton
Yes but now i can use the method mentioned by @benwilson512 and don’t need to ignore query anymore.
1