Question

I have question about managing transaction in asp.net application.

For example i have application for planning vacations.

Controller has form to approving vacations.

One user – click save and approve vacation —- employee which want vacation has – 1 day
second user – clik save and approve vacation and ?

//pseudocode

    public void ApproveVacation(int vacationId)
    {
        //pull vacationdata from db
        var vacation = _dbContext.Vacations.FirstOrDefault(x => x.Id == vacationId);
        if (vacation != null && vacation.State != approved) //
        {
            using (TransactionScope scope = new TransactionScope())
            {
                vacation.state = approved;
                vacation.Employee.Days = -1;
                _dbContext.saveChanges();
                scope.complete();
            }
        }
    }

And question is simple, is transaction enough for this scenario or I must use one of concurency technique?

Thanks

EDIT : Context is created one per request.

Answer 1

Transaction handles atomicity of the operation so if operation modifies multiple database records it will always result in consistent state where all records are correctly modified (if operation succeeds) or all changes are rolled back (if operation fails).

Concurrency handles possible modification of the same record by multiple processes / users because both could load original version of the record but one could save it first so when the second process tries to save a record it can silently override previous changes.

So what are you trying to handle in your code?