Editing InterBase (section)

==History==
===Multiversion concurrency control before InterBase===
[[Multiversion concurrency control]] is described in some detail in sections 4.3 and 5.5 of the 1981 paper "Concurrency Control in Distributed Database Systems"<ref>{{cite journal|author1=Bernstein, Philip A.|author2=Goodman, Nathan|title=Concurrency Control in Distributed Database Systems|journal=ACM Computing Surveys|year=1981|volume=13|issue=2|pages=185–221|doi=10.1145/356842.356846|s2cid=30874|url=http://portal.acm.org/citation.cfm?id=356846&dl=GUIDE&coll=Portal|access-date=September 21, 2005|doi-access=free}}</ref> by [[Phil Bernstein|Philip Bernstein]] and Nathan Goodman while employed by the Computer Corporation of America. Bernstein and Goodman's paper cites a 1978 dissertation<ref>{{cite thesis|author=Reed, D.P.|title=Naming and Synchronization in a Decentralized Computer System|work=MIT dissertation|year=1978|hdl=1721.1/16279|url=http://hdl.handle.net/1721.1/16279|access-date=November 12, 2022|type=Thesis}}</ref> by D.P. Reed, which describes [[Multiversion concurrency control|MVCC]] and claims it as an original work.

===Early years===
{{more citations needed section|date=June 2014}}
[[Jim Starkey]] was working at [[Digital Equipment Corporation|DEC]] on their [[DATATRIEVE]] 4th generation language [[4GL]] product when he came up with an idea for a system to manage concurrent changes by many users. The idea simplified the existing problems of ''locking'' which were proving to be a serious problem for the new [[relational database]] systems being developed at the time. 

Although InterBase's implementation is much more similar to the system described by [[David P. Reed|Reed]] in his MIT dissertation than any other database that existed at the time and Starkey knew Bernstein from his previous position at the Computer Corporation of America and later at DEC, Starkey claims that he arrived at the idea of multiversion concurrency control independently.<ref>{{cite web|author=Starkey, Jim|title=Weblog comment|work=Multiversion Concurrency Control Before InterBase|url=http://blogs.teamb.com/craigstuntz/2005/02/18/2699/|access-date=September 21, 2005|archive-url=https://web.archive.org/web/20071023164250/http://blogs.teamb.com/craigstuntz/2005/02/18/2699|archive-date=October 23, 2007|url-status=dead}}</ref> According to his blog, Starkey says:

<blockquote>The inspiration for multi-generational concurrency control was a database system done by [[Prime Computer|Prime]] that supported page level snapshots. The intention of the feature was to give a reader a [[Consistency (database systems)|consistent]] view of the database without blocking writers. The idea intrigued me as a very useful characteristic of a database system.</blockquote>

===Open source===
In early 2000, [[Borland]] announced that InterBase would be released under [[open-source software|open-source]], and began negotiations to spin off a separate company to manage the product. The [[source code]] for InterBase version 6 was released under a variant of the [[Mozilla Public License]] in mid-2000.

With the InterBase division at Borland under new management, the company released a [[proprietary software|proprietary]] version of InterBase version 6 and then 6.5. Borland released several updates to the open source code before announcing that it would no longer actively develop the open source project. [[Firebird (database server)|Firebird]], an open source [[fork (software)|fork]] of the InterBase 6 code, however, remains in active development.

In 2001, a [[Backdoor (computing)|backdoor]] was discovered in the software that had been present in all versions since 1994 and then resolved.<ref name="Backdoor">
{{cite web|url=http://www.cert.org/advisories/CA-2001-01.html|date=11 January 2000|title=CERT Advisory CA-2001-01 Interbase Server Contains Compiled-in Back Door Account|url-status=dead|archive-url=https://web.archive.org/web/20011118011732/http://www.cert.org/advisories/CA-2001-01.html|archive-date=18 November 2001}}</ref><ref>{{cite web|url=https://www.cvedetails.com/cve/CVE-2001-0008/|date=12 January 2000|title=Backdoor account in Interbase database server allows remote attackers to overwrite arbitrary files using stored procedures. |url-status=live|archive-url=https://web.archive.org/web/20121207022037/https://www.cvedetails.com/cve/CVE-2001-0008/|archive-date=7 December 2012}}</ref><ref>{{cite web|url=https://www.kb.cert.org/vuls/id/247371/|date=11 January 2001|title=Borland/Inprise Interbase SQL database server contains backdoor superuser account with known password|url-status=live|archive-url=https://web.archive.org/web/20011217094921/https://www.kb.cert.org/vuls/id/247371/|archive-date=17 December 2001}}</ref>

===CodeGear===
On May 7, 2008, Borland and [[Embarcadero Technologies]] announced that Embarcadero had "signed a definitive asset purchase agreement to purchase CodeGear."<ref>{{cite web|url=http://dn.codegear.com/article/38132|title=Community Letter: Embarcadero Technologies agrees to acquire CodeGear from Borland|access-date=2008-05-08|last=Intersimone|first=David|date=2008-05-07|archive-date=2012-04-15|archive-url=https://web.archive.org/web/20120415164511/http://edn.embarcadero.com/article/38132|url-status=dead}}</ref> The acquisition, for approximately $24.5 million, closed on 30 June 2008.<ref>{{cite web|url=http://www.embarcadero.com/press-releases/embarcadero-technologies-closes-acquisition-of-codegear-from-borland-software|title=Embarcadero Technologies Closes Acquisition of CodeGear|access-date=2008-07-03|last=Bravo|first=Thoma|date=2008-07-01}}</ref>

===Recent releases===