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.54.29; 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.11; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.01; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.07.23.20.09.17; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.04.59; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB: db dup
dbc dup
|
 
|
dbc dup
[-position]
Description
The dbc dup command duplicates the cursor, creates a new cursor
that uses the same transaction and locker ID as the original cursor. This
is useful when an application is using locking and requires two or more
cursors in the same thread of control.
The options are as follows:
- -position
- The newly created cursor is initialized to refer to the same position
in the database as the original cursor and hold the same locks. If the
-position flag is not specified, the created cursor is
uninitialized and will behave like a cursor newly created using the
db cursor command.
The dbc dup command returns 0 on success, and in the case of error, a Tcl error
is thrown.
Copyright Sleepycat Software
@
1.1
log
@Initial revision
@
text
@d1 2
a2 2
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 2
a2 2
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d1 3
a3 3
a4 1
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d1 3
a3 3
d5 1
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d1 3
a3 3
a4 1
@