grangerelixx
Hi, I have an ecto schema whose changeset function is in the following structure
def changeset(post, attrs) do
post
|> cast(attrs, @fields)
|> cast_embed(:blog)
|> unique_constraint([:name])
|> validate_required(@fields)
end
When there is a duplicate name and also some error in blog cast_embed, it should return errors from cast_embed and unique_constraint error but it only returns cast_embed error. How to get all errors?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
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
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
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.
Bringing learning, work and compliance together since 1987.
**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!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
joey_the_snake
It shouldn’t and here’s why:
The unique constraint can’t be validated unless the command is sent to the database. Your application won’t know if there’s a duplicate entry in the database table without doing so. If there’s an error with anything else the command won’t be sent to the database because there is a problem and it shouldn’t be attempted.
trisolaran
As @joey_the_snake mentioned,
unique_constraint/3only adds the error if your changest hits the database. You can however add an unsafe_validate_unique/4 to optimistically check for duplicate entries before insertion and add an error to the changeset if a duplicate is found. This is useful to show the user early on that the operation can’t succeed (and will probably catch most of the cases, the rest will be caught byunique_constraint/3)