db_env_set_func_exists
db_env_set_func_exists |
|
#include <db.h>int db_env_set_func_exists(int (*func_exists)(const char *path, int *isdirp));
The Berkeley DB library requires the ability to determine whether a file exists and whether it is a file of type directory. The func argument must conform to the following interface:
int exists(const char *path, int *isdirp);
The path argument is the pathname of the file to be checked.
If the isdirp argument is non-NULL, it must be set to non-0 if path is a directory, and 0 if path is not a directory.
The func_exists function must return the value of errno on failure and 0 on success.
The db_env_set_func_exists interface affects the entire application, not a single database or database environment.
Although the db_env_set_func_exists interface may be used to configure Berkeley DB at any time during the life of the application, it should normally be called before making any calls to the db_env_create or db_create functions.
The db_env_set_func_exists function returns a non-zero error value on failure and 0 on success.
The db_env_set_func_exists function may fail and return a non-zero error for the following conditions:
The db_env_set_func_exists 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_func_exists function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
|
|
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 @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d35 1 a35 1
The func_exists interface must return the value of errno on d37 6 a42 7
The db_env_set_func_exists method configures all operations performed by a process and all of its threads of control, not operations confined to a single database environment.
Although the db_env_set_func_exists interface may be called at any time during the life of the application, it should normally be called before making calls to the db_env_create or db_create methods.
The db_env_set_func_exists method returns a non-zero error value on failure and 0 on success. d44 1 a44 1
The db_env_set_func_exists method may fail and return a non-zero error for the following conditions: d48 4 a51 4
The db_env_set_func_exists 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_func_exists method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d53 19 a71 1 Run-time configuration @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d36 1 a36 1
The func_exists function must return the value of errno on d38 7 a44 6
The db_env_set_func_exists interface affects the entire application, not a single database or database environment.
Although the db_env_set_func_exists interface may be used to configure Berkeley DB at any time during the life of the application, it should normally be called before making any calls to the db_env_create or db_create functions.
The db_env_set_func_exists function returns a non-zero error value on failure and 0 on success. d46 1 a46 1
The db_env_set_func_exists function may fail and return a non-zero error for the following conditions: d50 4 a53 4
The db_env_set_func_exists 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_func_exists function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d55 1 a55 19 db_env_set_func_close, db_env_set_func_dirfree, db_env_set_func_dirlist, db_env_set_func_exists, db_env_set_func_free, db_env_set_func_fsync, db_env_set_func_ioinfo, db_env_set_func_malloc, db_env_set_func_map, db_env_set_func_open, db_env_set_func_read, db_env_set_func_realloc, db_env_set_func_seek, db_env_set_func_sleep, db_env_set_func_unlink, db_env_set_func_unmap, db_env_set_func_write, and db_env_set_func_yield. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d35 1 a35 1
The func_exists interface must return the value of errno on d37 6 a42 7
The db_env_set_func_exists method configures all operations performed by a process and all of its threads of control, not operations confined to a single database environment.
Although the db_env_set_func_exists interface may be called at any time during the life of the application, it should normally be called before making calls to the db_env_create or db_create methods.
The db_env_set_func_exists method returns a non-zero error value on failure and 0 on success. d44 1 a44 1
The db_env_set_func_exists method may fail and return a non-zero error for the following conditions: d48 4 a51 4
The db_env_set_func_exists 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_func_exists method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d53 19 a71 1 Run-time configuration @