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.53.26; 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.09; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.59; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.08.05; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.57; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: DbEnv::set_lk_conflicts

DbEnv::set_lk_conflicts

 APIRef 

#include <db_cxx.h>


int
DbEnv::set_lk_conflicts(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 DbEnv::set_lk_conflicts is never called, a standard conflicts array is used; see Standard Lock Modes for more information.

The DbEnv::set_lk_conflicts interface may be used only to configure Berkeley DB before the DbEnv::open interface is called.

The DbEnv::set_lk_conflicts method either returns a non-zero error value or throws an exception that encapsulates a non-zero error value on failure, and returns 0 on success.

Errors

The DbEnv::set_lk_conflicts method may fail and throw an exception or return a non-zero error for the following conditions:

EINVAL
An invalid flag value or parameter was specified.

Called after DbEnv::open was called.

ENOMEM
No memory was available to copy the conflicts array.

The DbEnv::set_lk_conflicts method may fail and throw an exception or return a non-zero error for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the DbEnv::set_lk_conflicts method may fail and either return DB_RUNRECOVERY or throw an exception encapsulating DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DbEnv, DbLock

See Also

DbEnv::set_lk_conflicts, DbEnv::set_lk_detect, DbEnv::set_lk_max, DbEnv::set_lk_max_lockers, DbEnv::set_lk_max_locks, DbEnv::set_lk_max_objects, DbEnv::lock_detect, DbEnv::lock_get, DbEnv::lock_id, DbLock::put, DbEnv::lock_stat, and DbEnv::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 d17 1 a17 1 APIRef d61 1 d68 1 a68 2 DbEnv::lock_id_free, DbEnv::lock_put, d74 1 a74 1 APIRef @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d38 2 a39 7

The DbEnv::set_lk_conflicts method configures a database environment, not only operations performed using the specified DbEnv handle.

The DbEnv::set_lk_conflicts interface may not be called after the DbEnv::open interface is called. If the database environment already exists when DbEnv::open is called, the information specified to DbEnv::set_lk_conflicts will be ignored. d52 4 a55 4 If a catastrophic error has occurred, the DbEnv::set_lk_conflicts method may fail and either return DB_RUNRECOVERY or throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d57 1 a57 1 DbEnv, DbLock d59 13 a71 1 Locking Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d39 7 a45 2

The DbEnv::set_lk_conflicts interface may be used only to configure Berkeley DB before the DbEnv::open interface is called. d58 4 a61 4 If a catastrophic error has occurred, the DbEnv::set_lk_conflicts method may fail and either return DB_RUNRECOVERY or throw an exception encapsulating DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d63 1 a63 1 DbEnv, DbLock d65 1 a65 13 DbEnv::set_lk_conflicts, DbEnv::set_lk_detect, DbEnv::set_lk_max_lockers, DbEnv::set_lk_max_locks, DbEnv::set_lk_max_objects, DbEnv::lock_detect, DbEnv::lock_get, DbEnv::lock_id, DbEnv::lock_id_free, DbEnv::lock_put, DbEnv::lock_stat, and DbEnv::lock_vec. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d38 2 a39 7

The DbEnv::set_lk_conflicts method configures a database environment, not only operations performed using the specified DbEnv handle.

The DbEnv::set_lk_conflicts interface may not be called after the DbEnv::open interface is called. If the database environment already exists when DbEnv::open is called, the information specified to DbEnv::set_lk_conflicts will be ignored. d52 4 a55 4 If a catastrophic error has occurred, the DbEnv::set_lk_conflicts method may fail and either return DB_RUNRECOVERY or throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d57 1 a57 1 DbEnv, DbLock d59 13 a71 1 Locking Subsystem and Related Methods @