Not necessarily, using or on different field with index usually result in query optimizer combine these two different index in bitwise or operation. Usually it’s not faster to do lookup one then the other because it cause two DB request network latency.

image1207×1273 36.3 KB

Hey @travisf you’d simply do something like instead of:

Thing |> where([t], t.id == ^params.id) |> Repo.one

you

Thing |> where([t], t.id == ^params.id or t.slug == ^params.id) |> Repo.one

Have a look at Phoenix.Param. You could do something like:

defimpl Phoenix.Param, for: YourApp.SomeContext.SomeSchema do
  def to_param(schema) do
    Map.get(schema, :slug, schema.id)
  end
end

To offer some unsolicited advice, I think it’ll be far less of a headache in the future if you make slugs non-nullable fields and auto-generate them based off of some other field as to not force users to specify one. Take it or leave it, of course!