1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
diff -Nur -x '*.orig' -x '*~' libdb-ruby-0.6.5/bdb.html libdb-ruby-0.6.5.new/bdb.html
--- libdb-ruby-0.6.5/bdb.html 2005-02-15 11:06:21.000000000 -0600
+++ libdb-ruby-0.6.5.new/bdb.html 2008-12-09 10:37:05.000000000 -0600
@@ -37,22 +37,22 @@
of the database, or mutable, permitting new records to be inserted
between existing records. </li>
</ul>
-<p><a href="docs/env.html">Berkeley DB environnement</a></p>
+<p><a href="env.html">Berkeley DB environnement</a></p>
<p>Berkeley DB environment is an encapsulation of one or more databases,
log files and shared information about the database environment such
as shared memory buffer cache pages.</p>
<p>Acces Methods</p>
<ul>
-<li><a href="docs/hashlike.html">Hash like interface</a>
+<li><a href="hashlike.html">Hash like interface</a>
these are the common methods for BDB::Btree,
BDB::Hash, BDB::Recno, BDB::Queue</li>
-<li><a href="docs/arraylike.html">Array like interface</a>
+<li><a href="arraylike.html">Array like interface</a>
methods for BDB::Recnum</li>
</ul>
-<p><a href="docs/sequence.html">Sequence</a></p>
+<p><a href="sequence.html">Sequence</a></p>
<p>A sequence is created with BDB::Common::create_sequence or
BDB::Common::open_sequence (only with db >= 4.3)</p>
-<p><a href="docs/transaction.html">Transaction Manager</a></p>
+<p><a href="transaction.html">Transaction Manager</a></p>
<p>The transaction subsystem makes operations atomic, consistent,
isolated, and durable in the face of system and application
failures. The subsystem requires that the data be properly logged and
@@ -60,20 +60,20 @@
the components necessary to transaction-protect the Berkeley DB access
methods and other forms of data may be protected if they are logged
and locked appropriately.</p>
-<p><a href="docs/cursor.html">Cursor operation</a></p>
+<p><a href="cursor.html">Cursor operation</a></p>
<p>A database cursor is a sequential pointer to the database entries. It
allows traversal of the database and access to duplicate keyed
entries. Cursors are used for operating on collections of records,
for iterating over a database, and for saving handles to individual
records, so that they can be modified after they have been read.</p>
-<p>See also iterators in <a href="docs/hashlike.html#each">Acces Methods</a></p>
-<p><a href="docs/lock.html">Lock system</a></p>
+<p>See also iterators in <a href="hashlike.html#each">Acces Methods</a></p>
+<p><a href="lock.html">Lock system</a></p>
<p>The lock subsystem provides interprocess and intraprocess concurrency
control mechanisms. While the locking system is used extensively by
the Berkeley DB access methods and transaction system, it may also be
used as a stand-alone subsystem to provide concurrency control to any
set of designated resources.</p>
-<p><a href="docs/log.html">Logging subsystem</a></p>
+<p><a href="log.html">Logging subsystem</a></p>
<p>The logging subsystem is the logging facility used by Berkeley DB. It
is largely Berkeley DB specific, although it is potentially useful
outside of the Berkeley DB package for applications wanting
|
