knav_negi
In our application we have a code like below in Elixir:
Multi.new()
|> Multi.update(
:some_operation_name,
Entity
|> Repo.preload(:some_entity)
|> Ecto.Changeset.optimistic_lock(:lock_version)
|> Ecto.Changeset.change(some_id: some_uuid)
)
|> Repo.transaction()
We are using MYSql database, I find this code a little bit strange because it is using optimistic_locking inside a transation,I am wondering if we might run into issues because of using optimistic_locking inside a transction (pessimistic locking).
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #ai
- #umbrella
- #full-time-contract
- #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
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
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 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kip
A transaction essentially means “everything succeeds or nothing succeeds”, and although locking plays a part in determine the success or otherwise many other issues come into play: access control, timeouts, constraints and so on.
So here the optimistic lock may or may not succeed whether a lock of some kind is acquired or not. But if the optimistic lock fails, you want all of the
multisteps to rollback, which is what the transaction will accomplish.MySQL uses
REPEATABLE_READas the default isolation level so another transaction may have updated the optmistic lock column while the current transaction is in process. Therefore the optimistic lock will fail and the transaction would roll back.