ryanzidago
How do you go around structs ideally having less than 32 fields?
In the official docs, it’s written that ideally structs should have less than 32 fields (source here).
Do you go around that limitation? If yes, how?
It’s very easy for an ecto schema to have more than 32 fields, especially as your application grows in complexity …
Adding belongs_to already adds 2 fields to the struct (the association and the association_id keys).
Most Liked
Schultzer
You should always consult the guide Maps — Erlang System Documentation v28.0.2
dimitarvp
What problem are you solving?
The theoretical performance problems pointed in the official docs will be completely overshadowed by DB access and literally everything else in your app. You will never know they were there.
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
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.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"