Berkeley DB: DB_ENV->set_lk_conflicts
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++

# DB_ENV->set_lk_conflicts |

`

###

    #include <db.h>

    int
    DB_ENV->set_lk_conflicts(DB_ENV *dbenv,
        u_int8_t *conflicts, int nmodes);

# Description

Set the locking conflicts matrix. The conflicts argument is an nmodes by nmodes array. A non-0 value for the array element indicates that requested_mode and held_mode conflict:

>     conflicts[requested_mode][held_mode]

The not-granted mode must be represented by 0.

If DB_ENV->set_lk_conflicts is never called, a standard conflicts array is used; see Standard Lock Modes for more information.

The DB_ENV->set_lk_conflicts interface may be used only to configure Berkeley DB before the DB_ENV->open interface is called.

The DB_ENV->set_lk_conflicts function returns a non-zero error value on failure and 0 on success.

# Errors

The DB_ENV->set_lk_conflicts function may fail and return a non-zero error for the following conditions:

EINVAL
  An invalid flag value or parameter was specified.

  Called after DB_ENV->open was called.

ENOMEM
  No memory was available to copy the conflicts array.

The DB_ENV->set_lk_conflicts function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_lk_conflicts function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

# See Also

DB_ENV->set_lk_conflicts, DB_ENV->set_lk_detect, DB_ENV->set_lk_max_lockers, DB_ENV->set_lk_max_locks, DB_ENV->set_lk_max_objects, DB_ENV->lock_detect, DB_ENV->lock_get, DB_ENV->lock_id, DB_ENV->lock_id_free, DB_ENV->lock_put, DB_ENV->lock_stat, and DB_ENV->lock_vec.`

Copyright Sleepycat Software