1stSolo
Does lock_version need to be cast() into ChangeSet, or doing
changeset
|> optimistic_lock(:lock_version)
is enough?
I mean, AFAIK every attempt to update an object should have lock_version in the attributes map, so how does Ecto know what value to use for lock_version if we don’t put it into changeset by casting it?..
But when I look at examples online and in documentation all I see is ChangeSet.optimistic_lock/3 being called.
Trending in Questions
Hello everyone!
I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++.
Does anyone ...
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #security
- #processes
- #api
- #forms
- #hex










Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
woylie
It just gets the field from the changeset source:
https://github.com/elixir-ecto/ecto/blob/4a143348ab89e0174a1a5082fd47d868ebd9689b/lib/ecto/changeset.ex#L3418
You don’t need to cast just to access the source data. And you don’t want to cast the lock version, because you don’t want the value to be set from the parameters.
1stSolo
I don’t? For the value to be set from the parameters I need to put it in a changesset somehow - I thought it’s done by “casting”. And the whole point of optimistic lock is to make sure the caller doesn’t have the stale version of the data, so it would seem like having the most recent value of
lock_versionin the changeset should be required to avoid the stale object error?..woylie
When you call the changeset function, you pass the struct that you have, which has the
lock_versionvalue at the time you fetched it from the database. In the changeset, this original struct is under thedatafield. That’s where theoptimistic_lockfunction gets the current lock version from.1stSolo
In my case I have a absinthe client that pulls the object from the backend via graphql, and edits some fields on the object. The save operation takes
idof the object, the changed field, e.g.description, andlockVersionfrom the last time the data was pulled. Multiple users can edit the same object, hence optimistic locking to prevent overwriting someone else’s changes.So
lockVersionactually comes as part of parameters/arguments along with new value fordescription.Therefore I thought the right way to do it is to
which should result in Ecto preparing a SQL statement such as
UPDATE Object SET description=?, lock_version=? WHERE id=? AND lock_version=?, and bindingparams.data.descriptioninto 1st arg, incrementedlock_versioninto second arg,params.idinto 3rd arg andlockVersionfrom the client side into the last arg. Then if updated record count returned by the database driver is 1 then update succeeded and if it’s 0 then Ecto would raiseStaleStateError.So I actually do want to set lockVersion from the params. Is that incorrect?
woylie
Yes, in your case, you’d want to cast the lock version indeed.