Release 4.0: lock_XXX
Prev | Chapter 37. Upgrading Berkeley DB 3.3 applications to Berkeley DB 4.0 | Next

## Release 4.0: lock_XXX

The C API for the Berkeley DB Locking subsystem was reworked in the 4.0 release as follows:

Historic functional interface | Berkeley DB 4.X method
--- | ---
lock_detect | DB_ENV->lock_detect()
lock_get | DB_ENV->lock_get()
lock_id | DB_ENV->lock_id()
lock_put | DB_ENV->lock_put()
lock_stat | DB_ENV->lock_stat()
lock_vec | DB_ENV->lock_vec()

Applications calling any of these functions should update their calls to use the enclosing DB_ENV handle's method (easily done as the first argument to the existing call is the correct handle to use).

In addition, the DB_ENV->lock_stat() call has been changed in the 4.0 release to take a flags argument. To leave their historic behavior unchanged, applications should add a final argument of 0 to any calls made to DB_ENV->lock_stat().

The C++ and Java APIs for the DbLock::put (DbLock.put) method was reworked in the 4.0 release to make the lock put interface a method of the DB_ENV handle rather than the DbLock handle. Applications calling the DbLock::put or DbLock.put method should update their calls to use the enclosing DB_ENV handle's method (easily done as the first argument to the existing call is the correct handle to use).

Prev | Up | Next
Release 4.0: db_deadlock | Home | Release 4.0: log_XXX