benonymus
Hey there,
I am trying to create a unique id for a set of inserts to the database, and I want to make sure that it is unique.
Is this a good approach?
defp generate_random_unique_id() do
repeat_id = UUID.uuid4()
events =
Event
|> Event.by_repeat_id(repeat_id)
|> Repo.all()
case events do
[] -> repeat_id
_ -> generate_random_unique_id()
end
end
Is there ever a possibility that the process could get stuck here?
Thank you
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #ai
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
joshtaylor
Probably
Repo.aggregatewould be better (as it’s faster to count then get all records, deserialise them, etc), as you could just count then do what you need? Or just conflict?kip
In your approach there is a potential race condition in which two processes could theoretically create the same ID and then attempt to insert it. It may be better to delegate the creation of the ID to the database in a trigger.
cmkarlsson
Why not use the database? Create a table which holds the unique value, enforced with a unique constraint, and then reference this table from the multiple rows you are inserting?
Use and ecto transaction to make sure it is atomic.
benonymus
yesh, that works well, thanks!
benonymus
yes, thanks for pointing that out!
benonymus
I will go ahead with this approach!