Conflict Resolution ?

[MentalGear]

After browsing through the docs, I couldn't find a note on what conflict resolution is used?

Is it last updated .. ? Is there any lock or note when a user tries to access an item that is being edited in the admin UI by another user ?

[jacobsfletch]

Is there any lock or note when a user tries to access an item that is being edited in the admin UI by another user ?

We don't currently have support for this but it's a great idea. WordPress does this nicely, I think we can take queues from them.

Besides that, updates are processed in the order that they arrive.

[DanRibbens]

As jacobsfletch said, the last call to update the DB wins.

[dawidmachon]

As jacobsfletch said, the last call to update the DB wins.

Okay, so it's not like findAndUpdate from mongo.

From mongo blog:

A findAndModify operation on a document is atomic: if the find condition matches a document, the update is performed on that document. Concurrent queries and additional updates on that document are not affected until the current update is complete.

[DanRibbens]

Yeah, I was thinking your followup question was unrelated to the conflict question DB operations! Sorry for that confusion.

[dawidmachon]

Yeah, I was thinking your followup question was unrelated to the conflict question DB operations! Sorry for that confusion.

Maybe I was not clear. But now everything is okay ;) Payload CMS is game changer for me as a CMS, but I'm using it for commerce app so atomic operations, transactions, rollbacks are crucial on longer run ;) So probably I picked a wrong tool for that for now, but Payload is so fun to use I will not pass it ; ) There is a lot of room left for own implementations, so it's a just bit more coding to implement that lacking things for my project for now ;)

[DanRibbens]

We're happy to work together on any of these requirements! I have a PR for transactions that I put on hold until we get multiple DB options further along.
There are also plans to handle document locking and handling concurrent updates—#2538

Our long term strategy is to make Payload 100% viable for these kinds of app framework level requirements.