Never used it that I know of in php, but have in other databases. Say you click on a record and start editing, 2 seconds later another user does the same on same record. If you hit save, your edit is saved theirs is not. The record is locked while you are editing, but still viewable. Again it may be different in laravel/php but foxpro, dbase, and access was that way.

So what would happen if say, one process locks a record, and while it's modifying it another process tries to lock and update the same record, does it wait until the first lock is removed or it just fails, or it goes normally but does not update the record?

Should fail. But on an internet database it should be rare two users editing the same record.

jimgwhit said:

Should fail. But on an internet database it should be rare two users editing the same record.

Thanks, we do have have a case where this is happening, although is not a user rather a sensor which is trying to update the same record. Do you know if it throws any kind of exception? Trying to make sure that when it happens, data is not lost and just deferred until the previous update completes. We know that this update process is not going to cause a deadlock and that it should be rather quick.

I'd test it on some test data.