laiboonh
Although in programming phoenix, the author tries to explain why not match on %{:id => id}. I still do not understand. Can someone explain this to me? I thought it will be better to match on atom since the key in the connection struct is :id
def show(conn, %{"id" => id}) do
user = Repo.get(Rumbl.User, id)
render conn, "show.html", user: user
end
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
aseigo
The params map (which is the second parameter there) maps strings to values, all of this coming from the user (via the http request). The conn struct contains information related to the connection and uses atoms for its keys since it is defined and populated in the server (as opposed to reflecting data from the user).
Of course, params could convert the strings to atoms, but as atoms are constants which are not garbage collected (they are intended to be used as identifiers, not as a general purpose data type), it would be possible for a user to DOS a Phoenix application just by sending lots and lots of unique keys via http requests.
(It’s also almost certainly more performant to use strings due to how substring sharing is done with bitstrings in the BEAM ..)
tl;dr → Te params map is keyed by strings because it is data that comes from the user, and the conn struct is an internal datatype with a static shape and so happily uses atoms.
HTH.
gregvaughn
Atoms, once generated in the BEAM are never garbage collected. If Phoenix blindly converts user supplied data into atoms, it is effectively a Denial of Service hole in every Phoenix app.
Last Post!
aseigo
Exactly; the request parameters are parsed out into the params argument and stored using string keys.
This prevents a possible security / DOS issue, and so requires that pattern matching on those params is done with strings.