Berkeley DB: DB->rename
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->rename |

`

###

    #include <db.h>

    int
    DB->rename(DB *db, const char *file,
        const char *database, const char *newname, u_int32_t flags);

# Description

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.

# Environment Variables

DB_HOME
  If the dbenv argument to db_create was initialized using DB_ENV->open, the environment variable DB_HOME may be used as the path of the database environment home. Specifically, DB->rename is affected by the configuration value DB_DATA_DIR.

# Errors

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

EINVAL
  A database in the file is currently open.

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.

# See Also

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.`

Copyright Sleepycat Software