MatijaL

MatijaL

Hello,

I’m having a bit of trouble creating a function with EctoMulti. I have support_tickets which have many support_ticket_messages. When I want to insert new message, I have the following function which takes the attrs and puts association to ticket and user and this function works just fine.

def create_support_ticket_message(%SupportTicket{} = ticket, %User{} = user, attrs) do
    %SupportTicketMessage{seen: false}
    |> SupportTicketMessage.changeset(attrs)
    |> Ecto.Changeset.put_assoc(:support_ticket, ticket)
    |> Ecto.Changeset.put_assoc(:user, user)
    |> Repo.insert()
end

Now, I want to send notification to the user when new message is created so I wanted to use Ecto.Multi() but I’m not sure how to write it properly. The following function doesn’t work because I need to use a function to use Ecto.build_assoc() and I have only a changeset which contain message attrs.

changeset = SupportTicketMessage.changeset(attrs)

Multi.new()
    |> Multi.insert(:support_ticket_message, changeset ->
        Ecto.build_assoc(ticket, :support_ticket_messages)
        Ecto.build_assoc(user, :user)
      end)
    |> Repo.transaction()

How to write this function properly?

Showing Posts 1 to 3

MatijaL

MatijaL OP

Just solved it this way but if someone knows a better way, I would be happy to hear it.

changeset =
      %SupportTicketMessage{user_id: user.id, ticket_id: ticket.id}
      |> SupportTicketMessage.changeset(attrs)

    Multi.new()
    |> Multi.insert(:support_ticket_message, changeset)
    |> Repo.transaction()
sodapopcan

sodapopcan

Looks like you got it but since I typed this all out I’m gonna post anyway :sweat_smile: I included the run function you can use if you want notifying the user to be part of the transaction.

def support_ticket_message_changeset(%SupportTicket{} = ticket, %User{} = user, attrs) do
  %SupportTicketMessage{seen: false}
  |> SupportTicketMessage.changeset(attrs)
  |> Ecto.Changeset.put_assoc(:support_ticket, ticket)
  |> Ecto.Changeset.put_assoc(:user, user)
end

Multi.new()
|> Multi.insert(:ticket, support_ticket_changeset(ticket, user, attrs))
|> Multi.run(:notification, fn _repo, %{ticket: ticket} ->
  notify_user_about_ticket(ticket, user)
end)
|> Repo.transaction()
sodapopcan

sodapopcan

It’s worth noting though that if there isn’t a good reason to fail the operation if the user isn’t notified (and I would think this is generally the case) you don’t need a Multi here as a changeset with associations is automatically run in a transaction with Repo.insert and friends.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews