How do you make optimistic lock for updating a content item?

[aaronamm]

I know that there are some optimistic check options in Orchard Core CMS project.

However, I can't reason this will work. This is because according to YesSql project.
We need to have Version property in Document type because we don't override VersionAccessorFactory configuration in
/src/YesSql.Core/Configuration.cs of YesSql project.

I also couldn't find any code in Orchard Core project that tries to set a version number from a form input to content item/content part for optimistic lock checking.

I would be glad if you could explain or give me some example to get optimistic lock work in Orchard Core project.

Thank you.

FYI, this test in YesSql project is a good one.
https://github.com/sebastienros/yessql/blob/main/test/YesSql.Tests/CoreTests.cs#L5899

[aaronamm]

I think we need to add Version property to ContentItemClass class to get optimistic lock works properly.

Here is the code that I try to test if can update version number.

        var car = new Car()
        {
            Name = "Honda",
            Version = 111
        };
        _session.Save(car);

and the result:

Id	Type	Content	Version
1421	Bidmun.Commerce.Models.Car, Bidmun.Commerce	{"Id":1421,"Version":111,"Name":"Honda"}	111

We can then set Version property from form's input. If the version has changed, ConcurrencyException will throw.

[aaronamm]

The following code throws ConcurrencyException as expected.

        var car = await _session.GetAsync<Car>(1421);
        car.Version = 110;
        car.Name = "Honda";
        _session.Save(car, checkConcurrency: true);

[aaronamm]

The version property is read by YesSql which uses Refection so setting contentItem.Content.Version = 111 does not work.

https://github.com/sebastienros/yessql/blob/main/src/YesSql.Core/Data/PropertyAccessorFactory.cs#L37-L62