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.49; 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.55; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.07.56; 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 @
DB->rename |
![]() ![]() |
#include <db.h>int DB->rename(DB *db, const char *file, const char *database, const char *newname, u_int32_t flags);
The DB->rename interface renames the database specified by the file and database arguments to newname. If no database is specified, the underlying file represented by file is renamed, incidentally renaming all databases that it contained.
Applications should not rename databases that are currently in use. If an underlying file is being renamed and logging is currently enabled in the database environment, no database in the file may be open when the DB->rename function is called. In particular, some architectures do not permit renaming files with open handles. On these architectures, attempts to rename databases that are currently in use by any thread of control in the system will fail.
The flags parameter is currently unused, and must be set to 0.
After DB->rename has been called, regardless of its return, the DB handle may not be accessed again.
The DB->rename function returns a non-zero error value on failure and 0 on success.
The DB->rename function may fail and return a non-zero error for the following conditions:
The DB->rename 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->rename 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 d26 1 a26 1 const char *database, const char *newname, u_int32_t flags); d43 1 a43 1 DB handle may not be accessed again. @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 3 a3 1 d29 1 a29 1
The DB->rename method renames the database specified by the d37 1 a37 1 DB->rename method is called. In particular, some architectures do d42 3 a44 3
The DB handle may not be accessed again after DB->rename is called, regardless of its return.
The DB->rename method returns a non-zero error value on failure and 0 on success. d47 4 a50 6
DB->rename is affected by any database directory specified using the DB_ENV->set_data_dir method, or by setting the "set_data_dir" string in the environment's DB_CONFIG file. d53 1 a53 1
The DB->rename method may fail and return a non-zero error for the following conditions: d55 1 a55 3
A database in the file is currently open.
Called after DB->open was called. d57 4 a60 6
The DB->rename 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->rename method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
The DB->rename interface renames the database specified by the d39 1 a39 1 DB->rename function is called. In particular, some architectures do d44 3 a46 3
After DB->rename has been called, regardless of its return, the DB handle may not be accessed again.
The DB->rename function returns a non-zero error value on failure and 0 on success. d49 6 a54 4
The DB->rename function may fail and return a non-zero error for the following conditions: d59 3 a61 1
The DB->rename 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->rename function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d70 1 a70 46 db_create, DB->associate, DB->close, DB->cursor, DB->del, DB->err, DB->errx DB->fd, DB->get, DB->pget, DB->get_byteswapped, DB->get_type, DB->join, DB->key_range, DB->open, DB->put, DB->remove, DB->rename, DB->set_alloc, DB->set_append_recno, DB->set_bt_compare, DB->set_bt_minkey, DB->set_bt_prefix, DB->set_cachesize, DB->set_dup_compare, DB->set_errcall, DB->set_errfile, DB->set_errpfx, DB->set_feedback, DB->set_flags, DB->set_h_ffactor, DB->set_h_hash, DB->set_h_nelem, DB->set_lorder, DB->set_pagesize, DB->set_paniccall, DB->set_q_extentsize, DB->set_re_delim, DB->set_re_len, DB->set_re_pad, DB->set_re_source, DB->stat, DB->sync, DB->truncate, DB->upgrade, and DB->verify. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 3 a3 1 d29 1 a29 1
The DB->rename method renames the database specified by the d37 1 a37 1 DB->rename method is called. In particular, some architectures do d42 3 a44 3
The DB handle may not be accessed again after DB->rename is called, regardless of its return.
The DB->rename method returns a non-zero error value on failure and 0 on success. d47 4 a50 6
DB->rename is affected by any database directory specified using the DB_ENV->set_data_dir method, or by setting the "set_data_dir" string in the environment's DB_CONFIG file. d53 1 a53 1
The DB->rename method may fail and return a non-zero error for the following conditions: d55 1 a55 3
A database in the file is currently open.
Called after DB->open was called. d57 4 a60 6
The DB->rename 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->rename method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.