carlgleisner
Is it supported to have eager_check?: true run on identities when the identity consists of more than one attribute?
I have a compound identity that indeed returns errors on submission with Postgres as data layer. On another resource using an identity with a single attribute I do get eager checking on validation however, as one would expect of course.
identities do
identity :imaginative_party_name, [:host_id, :party_name] do
eager_check? true
message "success not possible if you insist on reusing party names all the time"
end
end
Looking at the documentation I cannot tell that this would not be supported. If so, then maybe this could be pointed out?
Trending in Questions
Hello everyone!
I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++.
Does anyone ...
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #security
- #processes
- #api
- #forms
- #hex










Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
Are you saying that eager checking is not working for your compound identity?
carlgleisner
Yes I’m sorry for failing to make that explicit.
I’ll revert with a reproduction (have a few of those outstanding at the moment).
zachdaniel
Interesting. It should work
If not then its a bug.
carlgleisner
It works
The thing was that I was using
argumentfor the input of the key of the related record together with achangewithmanage_relationship. As I understand it now this is intended behaviour.I dug up a few of your messages in the Discord which I think explain it:
You put examples in there as well, very helpful. Maybe I could copy these here as well if appropriate?
Humbly, maybe a note in the documentation could be of use for others? I’d be happy to provide a PR as a starting point if desirable.
Sidenote
I’m yet to try out the solutions you suggested since for now it’s just fine for me to not use
argument+change. But I did wonder whether that also solves not getting errors after submission when passing in input that does not relate to theidof an existing record.Reference codebase
I used this little reproduction for testing for future reference.
But I guess it’s technically not a “reproduction” when there is no actual issue
https://github.com/carlgleisner/ash_phoenix_reproduction
EDIT: I should edit the title of this post for posterity
zachdaniel
You would have my utmost gratitude
This one would probably be a separate issue? Likely has something to do with input names not matching? But curious to see if its still an issue after your change