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.55.58; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.38; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.38; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.12; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.49.04; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.10.15.03.47.35; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.05.00; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @
|
![]() ![]() ![]() |
The DB structure is now opaque for applications in the Berkeley DB 3.0 release. Accesses to any fields within that structure by the application should be replaced with method calls. The following example illustrates this using the historic type structure field. In the Berkeley DB 2.X releases, applications could find the type of an underlying database using code similar to the following:
DB *db; DB_TYPE type;type = db->type;
in the Berkeley DB 3.X releases, this should be done using the DB->get_type method, as follows:
DB *db; DB_TYPE type;type = db->get_type(db);
The following table lists the DB fields previously used by applications and the methods that should now be used to get or set them.
DB field | Berkeley DB 3.X method |
---|---|
byteswapped | DB->get_byteswapped |
db_errcall | DB->set_errcall |
db_errfile | DB->set_errfile |
db_errpfx | DB->set_errpfx |
db_paniccall | DB->set_paniccall |
type | DB->get_type |
![]() ![]() ![]() |
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
The DB structure is now opaque for applications in the Berkeley DB 3.0 d33 1 a33 1
The following table lists the DB fields previously used by d36 1 a36 1
The DB structure is now opaque for applications in the Berkeley DB 3.0 d33 1 a33 1
The following table lists the DB fields previously used by d36 1 a36 1
The DB structure is now opaque for applications in the Berkeley DB 3.0 d34 1 a34 1
The following table lists the DB fields previously used by d37 1 a37 1
The DB structure is now opaque for applications in the Berkeley DB 3.0 d33 1 a33 1
The following table lists the DB fields previously used by d36 1 a36 1