msyavuz
Ecto schema inside its own context?
Hello, i am a newbie in both phoenix and elixir and its been a blast so far. I have a question about ecto schemas and phoenix contexts.
Suppose i have two tables called clubs and club_members. While generating a new schema with phx.gen.schema
-
Should i create the club schema under club context ?
-
Or should i create club schema without context and put member schema under club context?
First approach results in module name being Club.Club but directory structure seems better. While module naming in second approach seems better but club schema sits outside club directory.
I guess what i am asking is which one of these is better?
/001 club/ member.ex
/002 club.ex
/001 club/ member.ex
/001 club/ club.ex
Marked As Solved
sodapopcan
Generally if you are using contexts as a boundary, then you put all the schemas belonging to a context under it.
Also by convention, if there isn’t a good unique name for a context (which there often isn’t) then it’s the pluralized version of its primary schema. You could just call your context Club if you want, but this can become confusing and it also makes it impossible to alias the schema within the context as they will have the same name. So the “normal” thing to do is this:
lib/my_app/clubs/club.ex
lib/my_app/clubs/member.ex
lib/my_app/clubs.ex
This way the directory structure mimics the module structure. Some people like to put the context file in the context directory, which is fine, whatever floats your boat!
Technically, though, you are free to do whatever you want! The generators push us towards certain conventions, but otherwise Phoenix doesn’t impose any conventions on us.
Also Liked
zachallaun
The most common way to solve this would be to call the context clubs, so you would have Clubs.Club and Clubs.Member.
msyavuz
Popular in Questions
Other popular topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
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
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
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!"