Optimistic concurrency control: Difference between revisions

Revision as of 21:47, 30 November 2023

Revision as of 11:44, 22 December 2023

Line 26:

* [[Microsoft]]'s [[Entity Framework]] (including Code-First) has built-in support for OCC based on a binary timestamp value.<ref>{{cite web | url = http://blogs.msdn.com/b/alexj/archive/2009/05/20/tip-19-how-to-use-optimistic-concurrency-in-the-entity-framework.aspx | title = Tip 19 – How to use Optimistic Concurrency with the Entity Framework | work = MSDN Blogs | date = 19 May 2009}}

* Most [[revision control]] systems support the "merge" model for concurrency, which is OCC.</ref>

* [[Mimer SQL]] is a [[DBMS]] that only implements optimistic concurrency control.<ref>{{cite web | url = httphttps://developer.mimer.com/featuresarticle/transaction-concurrency-optimistic-concurrency-control/feature_15.htm | title = Transaction Concurrency - Optimistic Concurrency Control | work = Mimer Developers - Features | date = 26 February 2010 | access-date = 622 May 2013 | archive-url = https://web.archive.org/web/20130321105959/http://developer.mimer.com/features/feature_15.htm | archive-date = 21 March 2013 | url-status = dead | df = dmy-allDec 2023}}</ref>

* [[Google App Engine]] data store uses OCC.<ref>{{cite web | url = http://code.google.com/appengine/docs/whatisgoogleappengine.html | title = The Datastore | work = What Is Google App Engine? | date = 27 August 2010}}</ref>

* The [[Apache Solr]] search engine supports OCC via the _version_ field.<ref>{{cite web|url=https://lucene.apache.org/solr/guide/6_6/updating-parts-of-documents.html|title=Updating Parts of Documents|access-date=2018-06-28}}</ref>