After doing the Ash Livebook Getting started for several times over the last 2? years, I finally have a small project that I dare to tackle with Ash. Loving it so far. However, sometimes I am not quite sure what to do when receiving an error. Basic Idea / Context The system is meant to collect …

As far as I can tell, in the info block for Fully Atomic Updates it states An atomic update is one that can be done in a single operation in the data layer. This ensures that there are no issues with concurrent access to the record being updated, and that it is as performant as possible. Since y…

Exactly correct :slight_smile: If this can’t be done atomically, you can add require_atomic? false to the action definition.

[image] larshei: # is this how we would properly check the round_id? def validate(%{attributes: %{round_id: id}}, _opts, _context) when not is_nil(id) do This is probably easier to do in the action with present/2 validate present([:round_id])

Alright, thanks! in this scenario, race conditions do not really matter, cause all the steps are manual anyway, and the worst thing that could happen is someone submitting a proposal 5 ms after the round is being closed, which is not a big deal. However, I have to admin I have no idea what I would…

For that you’d have to figure out how to do a explicit blocking lock on the row, which would run your operation to validate the open status and then update the approval in a transaction. So any other processes are made to wait for the row to unlock before they can go on.

In Ash, this can be placed in your update action change get_and_lock(:for_update)

Ash - does not implement `atomic/3`

Questions & Help Questions

03juan May 31, 2024, 7:05pm 4

This is probably easier to do in the action with present/2

validate present([:round_id])