head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.54; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.08; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.56; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.07.58; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: DB_ENV->set_lk_conflicts

DB_ENV->set_lk_conflicts

 APIRef 

#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, DB_ENV->set_lk_max_lockers, DB_ENV->set_lk_max_locks, DB_ENV->set_lk_max_objects, lock_detect, lock_get, lock_id, lock_put, lock_stat, and lock_vec.

APIRef

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d58 1 d62 5 a66 6 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, d68 1 a68 1 DB_ENV->lock_vec. @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d39 3 a41 8

The DB_ENV->set_lk_conflicts method configures a database environment, not only operations performed using the specified DB_ENV handle.

The DB_ENV->set_lk_conflicts interface may not be called after the DB_ENV->open interface is called. If the database environment already exists when DB_ENV->open is called, the information specified to DB_ENV->set_lk_conflicts will be ignored.

The DB_ENV->set_lk_conflicts method returns a non-zero error value on failure and 0 on success. d43 1 a43 1

The DB_ENV->set_lk_conflicts method may fail and return a non-zero error for the following conditions: d51 4 a54 6

The DB_ENV->set_lk_conflicts method 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 method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_LOCK d56 13 a68 1 Locking Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d40 8 a47 3

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. d49 1 a49 1

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

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. d64 1 a64 13 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. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d39 3 a41 8

The DB_ENV->set_lk_conflicts method configures a database environment, not only operations performed using the specified DB_ENV handle.

The DB_ENV->set_lk_conflicts interface may not be called after the DB_ENV->open interface is called. If the database environment already exists when DB_ENV->open is called, the information specified to DB_ENV->set_lk_conflicts will be ignored.

The DB_ENV->set_lk_conflicts method returns a non-zero error value on failure and 0 on success. d43 1 a43 1

The DB_ENV->set_lk_conflicts method may fail and return a non-zero error for the following conditions: d51 4 a54 6

The DB_ENV->set_lk_conflicts method 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 method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_LOCK d56 13 a68 1 Locking Subsystem and Related Methods @