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.10.15.03.47.33; 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: Dbc

Dbc

APIRef

import com.sleepycat.db.*;

public class Dbc extends Object { ... }

Description

This manual page describes the specific details of the Dbc class, which provides cursor support for the access methods in Db.

The Dbc functions are the library interface supporting sequential access to the records stored by the access methods of the Berkeley DB library. Cursors are created by calling the Db.cursor method which returns a Dbc object.

Class

Dbc

See Also

Dbc.close, Dbc.count, Dbc.del, Dbc.dup, Dbc.get, Dbc.pget, and Dbc.put.

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 d46 1 a46 1 APIRef @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d27 17 a43 7

The Dbc object is the handle for a cursor into a Berkeley DB database. The handle is not free-threaded, and cursors may not span threads; nor may cursors be used by more than a single thread. If the cursor is to be used to perform operations on behalf of a transaction, the cursor must be opened and closed within the context of that single transaction. Once Dbc.close has been called, the handle may not be accessed again, regardless of the method's return. @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d28 7 a34 17

This manual page describes the specific details of the Dbc class, which provides cursor support for the access methods in Db.

The Dbc functions are the library interface supporting sequential access to the records stored by the access methods of the Berkeley DB library. Cursors are created by calling the Db.cursor method which returns a Dbc object.

Class

Dbc

See Also

Dbc.close, Dbc.count, Dbc.del, Dbc.dup, Dbc.get, Dbc.pget, and Dbc.put. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d27 17 a43 7

The Dbc object is the handle for a cursor into a Berkeley DB database. The handle is not free-threaded, and cursors may not span threads; nor may cursors be used by more than a single thread. If the cursor is to be used to perform operations on behalf of a transaction, the cursor must be opened and closed within the context of that single transaction. Once Dbc.close has been called, the handle may not be accessed again, regardless of the method's return. @