Db.upgrade

 APIRef 

import com.sleepycat.db.*;


public void upgrade(String file, int flags)
    throws DbException;

Description

The Db.upgrade method upgrades all of the databases included in the file file, if necessary. If no upgrade is necessary, Db.upgrade always returns success.

Database upgrades are done in place and are destructive. For example, if pages need to be allocated and no disk space is available, the database may be left corrupted. Backups should be made before databases are upgraded. See Upgrading databases for more information.

Unlike all other database operations, Db.upgrade may only be done on a system with the same byte-order adth="100%">
APIRef

Copyright Sleepycat Software ./usr/share/doc/db4.1-doc/api_java/db_set_re_pad.html0000644000000000000000000000551207540464750022434 0ustar rootroot00000000000000 Berkeley DB: Db.set_re_pad

Db.set_re_pad

 APIRef 

import com.sleepycat.db.*;


public void set_re_pad(int re_pad)
    throws DbException;

Description

Set the padding character for short, fixed-length records for the Queue and Recno access methods.

If no pad character is specified, <space> characters (that is, ASCII 0x20) are used for padding.

The Db.set_re_pad method configures a database, not only operations performed using the specified Db handle.

The Db.set_re_pad interface may not be called after the Db.open interface is called. If the database already exists when Db.open is called, the information specified to Db.set_re_pad will be ignored.

The Db.set_re_pad method throws an exception that encapsulates a non-zero error value on failure.

Errors

The Db.set_re_pad method may fail and throw an exception encapsulating a non-zero error for the following conditions:

EINVAL
An invalid flag value or parameter was specified.

Called after Db.open was called.

The Db.set_re_pad method may fail and throw an exception for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the Db.set_re_pad method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.