Feel free to open any issues for things like that?
zachdaniel
Creator of Ash
BartOtten
Now I know it should be up to date I’ll raise an issues (or PR) when found. Thanks for the rapid response.
0
TwistingTwists
do the live book tutorials work with Ash 3.0 ?
I am getting
** (Ash.Error.Framework) Framework Error
* Tutorial.Support.Ticket.assign must be performed atomically, but it could not be
Reason: cannot atomically manage relationships
See https://hexdocs.pm/ash/3.0.0-rc.15/update-actions.html#atomic-updates for more on atomics.
(elixir 1.15.7) lib/process.ex:860: Process.info/2
(ash 3.0.0-rc.33) lib/ash/error/framework/must_be_atomic.ex:5: Ash.Error.Framework.MustBeAtomic.exception/1
(ash 3.0.0-rc.33) lib/ash/actions/update/update.ex:170: Ash.Actions.Update.run/4
(ash 3.0.0-rc.33) lib/ash.ex:2447: Ash.update/2
(ash 3.0.0-rc.33) lib/ash.ex:2408: Ash.update!/2
(elixir 1.15.7) src/elixir.erl:396: :elixir.eval_external_handler/3
(stdlib 5.1.1) erl_eval.erl:750: :erl_eval.do_apply/7
(elixir 1.15.7) src/elixir.erl:375: :elixir.eval_forms/4
(elixir 1.15.7) lib/process.ex:860: Process.info/2
this is from 9 - Managing relationships.
0
zachdaniel
Creator of Ash
An, right this is a consequence of a recent change to support atomics in ETS. I will update the tutorial. Are there any other broken places that you saw?
0
zachdaniel
Creator of Ash
Okay, I’ve addressed this in the tutorial. Specifically, I’ve removed the need to use manage_relationship at all in the Livebook tutorial, and therefore all of the actions are atomic safe 
Would you mind taking a look to see what you think?
1
TwistingTwists
TwistingTwists
I think there is a need for a ‘showcase’ repo / livebook depicting various use cases for many-many relationships. especially, showcasing manage_relationship – that is most common use case where I get stuck frequently.
Here are a few scenarios I have come across. Feel free to add more to the list.
- user many-many orgs
throughuser_orgs
user_orgs has keys :user_role + user_id + org_id
A. when deleting user → delete from user_orgs but don’t delete orgs
B. when deleting user → also delete user_orgs and orgs
C. when creating user → also create org and pass the user_role in manage_relationship
- artist many-many album
throughartist_album
album many-many songsthroughalbum_songs
A. create_song_with_artist_and_album → takes song attributes and artist_id, album_id to manage those
as of now, hooking into after_action has been a goto strategy to make these work. But ideally, I would love to understand how can I achieve the same using manage_relationship.
1
zachdaniel
Creator of Ash
Agreed! Please add these suggestions to the documentation overhaul community suggestions issue if you don’t mind: Community suggestions for documentation overhaul · Issue #995 · ash-project/ash · GitHub
1