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.56; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.37; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.37; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.10; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.49.00; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.08.09; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.58; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: Db.set_lorder

Db.set_lorder

 APIRef 

import com.sleepycat.db.*;


public void set_lorder(int lorder)
	throws DbException;

Description

Set the byte order for integers in the stored database metadata. The number should represent the order as an integer; for example, big endian order is the value 4,321, and little endian order is the value 1,234. If lorder is not explicitly set, the host order of the machine where the Berkeley DB library was compiled is used.

The value of lorder is ignored except when databases are being created. If a database already exists, the byte order it uses is determined when the database is opened.

The access methods provide no guarantees about the byte ordering of the application data stored in the database, and applications are responsible for maintaining any necessary ordering.

The Db.set_lorder interface may be used only to configure Berkeley DB before the Db.open interface is called.

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

Errors

The Db.set_lorder 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_lorder 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_lorder method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

Db

See Also

Db.associate, Db.close, Db.cursor, Db.del, 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_append_recno, Db.set_bt_minkey, Db.set_cachesize, Db.set_errcall, Db.set_errpfx, Db.set_feedback, Db.set_flags, Db.set_h_ffactor, Db.set_h_nelem, Db.set_lorder, Db.set_pagesize, 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.

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 d25 1 a25 1 throws DbException; d95 1 a95 1 APIRef @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d33 3 d39 2 a40 10

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

The Db.set_lorder 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_lorder will be ignored. If creating additional databases in a file, the byte order specified must be consistent with the existing databases in the file or an error will be returned. d50 3 a52 3 If a catastrophic error has occurred, the Db.set_lorder method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d56 37 a92 1 Databases and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 a33 3

The value of lorder is ignored except when databases are being created. If a database already exists, the byte order it uses is determined when the database is opened. d37 10 a46 2

The Db.set_lorder interface may be used only to configure Berkeley DB before the Db.open interface is called. d56 3 a58 3 If a catastrophic error has occurred, the Db.set_lorder method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d62 1 a62 37 Db.associate, Db.close, Db.cursor, Db.del, 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_append_recno, Db.set_bt_minkey, Db.set_cachesize, Db.set_errcall, Db.set_errpfx, Db.set_feedback, Db.set_flags, Db.set_h_ffactor, Db.set_h_nelem, Db.set_lorder, Db.set_pagesize, 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 2 a3 1 d33 3 d39 2 a40 10

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

The Db.set_lorder 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_lorder will be ignored. If creating additional databases in a file, the byte order specified must be consistent with the existing databases in the file or an error will be returned. d50 3 a52 3 If a catastrophic error has occurred, the Db.set_lorder method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d56 37 a92 1 Databases and Related Methods @