Access table checking if still updating

posted by | Leave a comment

The subsequent history of Berkeley DB is a simpler and more traditional timeline: Berkeley DB 2.0 (1997) introduced transactions to Berkeley DB; Berkeley DB 3.0 (1999) was a re-designed version, adding further levels of abstraction and indirection to accommodate growing functionality.

Berkeley DB 4.0 (2001) introduced replication and high availability, and Oracle Berkeley DB 5.0 (2010) added SQL support.

The Berkeley DB project began with the modest goal of replacing the in-memory library that Margo Seltzer wrote [SY91] was based on Litwin's Extensible Linear Hashing research.Berkeley DB provides much of the same functionality that people expect from more conventional systems, such as relational databases, but packages it differently.For example, Berkeley DB provides fast data access, both keyed and sequential, as well as transaction support and recovery from failure.Mike Olson, also a graduate student at the University of California, Berkeley, had written a number of Btree implementations, and agreed to write one more.The three of us transformed Margo's hash software and Mike's Btree software into an access-method-agnostic API, where applications reference hash tables or Btrees via database handles that had handle methods to read and modify data.

Leave a Reply

not updating since new heads added