benonymus

benonymus

Hey there,

I have been using Ecto.Multi — Ecto v3.14.0 for a while now, and I was wondering what kind of convention do other people follow when they are naming the operations, especially when it is a Multi in an Enum.reduce/3.
With a regular Multi I usually use an atom as the examples do.

For a Multi in an reduce such as:

Enum.reduce(user_ids, Multi.new(), fn user_id, multi ->
      blocked_user = Accounts.get_user_by_hash_id(user_id)

      changeset = Block.changeset(%Block{}, user, blocked_user)

      multi
      |> Multi.insert("user_block_#{user.id}_#{blocked_user.id}", changeset)
    end)
    |> Repo.transaction()

I mostly use a string based on the structs I use, but this relies on both of them having an id and found.
Sometimes I use a uuid appended after the “user_block” for example, and in the docs I saw I could use a tuple.

How about you?

Showing Posts 1 to 4

jdj_dk

jdj_dk

I mostly use a string based on the structs I use, but this relies on both of them having an id and found.
Sometimes I use a uuid appended after the “user_block” for example, and in the docs I saw I could use a tuple.

I do the same as you. It works fine IMO. But perhaps there is a better way? :slight_smile:

LostKobrakai

LostKobrakai

You can use any term for naming you multi steps, not just atoms/strings. When mapping/reducing over lists I usually use tuples like {:products, product.id} or something like that.

jdj_dk

jdj_dk

I will start doing that going forward. Will make it much easier to pattern match on errors. Thanks for highlighting that.

dimitarvp

dimitarvp

I also use tuples. When you don’t know the ID beforehand you can just use a counter. See Enum.with_index.

When inserting I use tuples like {:insert, :product, index}.

— All posts loaded —

Where Next? Top

Trending in Discussions Top

AstonJ
As the title says, please share what you’ve been up to with Elixir. Whether that’s been learning it, looking into it, making stuff with i...
2977 92995 915
New
caslu
I want to open this thread for you all to discuss and help those who really like Ash but are still hesitant to use it in a real project. ...
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
GES233
I’m posting this in response to Jose’s recent tweet (Cr. link) : People are sleeping on Elixir for a coding harness: Hot-code swappi...
New
marciol
It would be helpful to have a list of companies worldwide that hire engineers without prior experience in Elixir. Often, it can be quite ...
New
durvia
Anyone running long-lived stateful processes on BEAM? We’re building an AI agent runtime and would love to compare notes. We’re a small ...
New
AstonJ
This might be a bit disturbing for some but it’s happening - computers running on living human neurons. They’ve made them smart enough t...
New

Other Trending Topics Top

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
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
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
Aludel - LLM Evaluation Workbench Aludel is an embeddable Phoenix LiveView dashboard for evaluating and comparing LLM prompts across mult...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews