File: dbopen.html

package info (click to toggle)
db 5.1.29-9
  • links: PTS, VCS
  • area: main
  • in suites: jessie-kfreebsd
  • size: 150,348 kB
  • sloc: ansic: 400,169; java: 94,399; tcl: 70,967; sh: 37,399; cs: 30,758; cpp: 21,132; perl: 14,227; xml: 9,854; makefile: 3,777; yacc: 1,003; awk: 942; sql: 801; erlang: 461; python: 216; php: 24; asm: 14
file content (582 lines) | stat: -rw-r--r-- 29,661 bytes parent folder | download | duplicates (3)
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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <title>DB-&gt;open()</title>
    <link rel="stylesheet" href="apiReference.css" type="text/css" />
    <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
    <link rel="start" href="index.html" title="Berkeley DB C API Reference" />
    <link rel="up" href="db.html" title="Chapter 2.  The DB Handle" />
    <link rel="prev" href="dbkey_range.html" title="DB-&gt;key_range()" />
    <link rel="next" href="dbput.html" title="DB-&gt;put()" />
  </head>
  <body>
    <div class="navheader">
      <table width="100%" summary="Navigation header">
        <tr>
          <th colspan="3" align="center">DB-&gt;open()</th>
        </tr>
        <tr>
          <td width="20%" align="left"><a accesskey="p" href="dbkey_range.html">Prev</a> </td>
          <th width="60%" align="center">Chapter 2. 
                The DB Handle
        </th>
          <td width="20%" align="right"> <a accesskey="n" href="dbput.html">Next</a></td>
        </tr>
      </table>
      <hr />
    </div>
    <div class="sect1" lang="en" xml:lang="en">
      <div class="titlepage">
        <div>
          <div>
            <h2 class="title" style="clear: both"><a id="dbopen"></a>DB-&gt;open()</h2>
          </div>
        </div>
      </div>
      <pre class="programlisting">#include &lt;db.h&gt;

int
DB-&gt;open(DB *db, DB_TXN *txnid, const char *file,
    const char *database, DBTYPE type, u_int32_t flags, int mode);  </pre>
      <p>
        The <code class="methodname">DB-&gt;open()</code> method opens the database represented by the 
        <span class="bold"><strong>file</strong></span> and <span class="bold"><strong>database</strong></span>.
    </p>
      <p>
         The currently supported Berkeley DB file formats (or <span class="emphasis"><em>access
         methods</em></span>) are Btree, Hash, Queue, and Recno.  The Btree
         format is a representation of a sorted, balanced tree structure.  The
         Hash format is an extensible, dynamic hashing scheme.  The Queue
         format supports fast access to fixed-length records accessed
         sequentially or by logical record number.  The Recno format supports
         fixed- or variable-length records, accessed sequentially or by logical
         record number, and optionally backed by a flat text file.
    </p>
      <p>
         Storage and retrieval for the Berkeley DB access methods are based on
         key/data pairs; see <a class="link" href="dbt.html" title="Chapter 4.  The DBT Handle">DBT</a> 
         for more information.
    </p>
      <p>
         Calling <code class="methodname">DB-&gt;open()</code> is a relatively expensive operation, and
         maintaining a set of open databases will normally be preferable to
         repeatedly opening and closing the database for each new query.
    </p>
      <p>
         The <code class="methodname">DB-&gt;open()</code> <span>
            <span>
                  method returns a non-zero error value on failure and 0 on success.
            </span>
            
        </span>
         If <code class="methodname">DB-&gt;open()</code> fails, the 
         <a class="xref" href="dbclose.html" title="DB-&gt;close()">DB-&gt;close()</a>  method must be
         called to discard the <a class="link" href="db.html" title="Chapter 2.  The DB Handle">DB</a> 
         handle.
    </p>
      <div class="sect2" lang="en" xml:lang="en">
        <div class="titlepage">
          <div>
            <div>
              <h3 class="title"><a id="idp50079768"></a>Parameters</h3>
            </div>
          </div>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50072448"></a>txnid</h4>
              </div>
            </div>
          </div>
          <p>
                          If the operation is part of an application-specified transaction, the
                          <span class="bold"><strong>txnid</strong></span> parameter is a transaction
                          handle returned from <a class="xref" href="txnbegin.html" title="DB_ENV-&gt;txn_begin()">DB_ENV-&gt;txn_begin()</a>; 
                          if the operation is part of a Berkeley DB Concurrent Data Store group, the
                          <span class="bold"><strong>txnid</strong></span> parameter is a handle returned
                          from <a class="xref" href="envcdsgroup_begin.html" title="DB_ENV-&gt;cdsgroup_begin()">DB_ENV-&gt;cdsgroup_begin()</a>;
                          otherwise NULL. If no transaction handle is specified, but the
                          DB_AUTO_COMMIT flag is specified, the operation will be implicitly
                          transaction protected. Note that transactionally protected operations
                          on a <a class="link" href="db.html" title="Chapter 2.  The DB Handle">DB</a>  handle requires
                          the <a class="link" href="db.html" title="Chapter 2.  The DB Handle">DB</a>  handle itself be
                          transactionally protected during its open.  Also note that the
                          transaction must be committed before the handle is closed; see <a href="../../programmer_reference/program_scope.html" class="olink">Berkeley DB handles</a> for more
                          information.
                     </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50096944"></a>file</h4>
              </div>
            </div>
          </div>
          <p>
                          The <span class="bold"><strong>file</strong></span> parameter is used as the
                          name of an underlying file that will be used to back the database; see
                          <a href="../../programmer_reference/env_naming.html" class="olink">File naming</a> for more
                          information.
                     </p>
          <p>
                          In-memory databases never intended to be preserved on disk may be
                          created by setting the <span class="bold"><strong>file</strong></span> parameter
                          to NULL. Whether other threads of control can access this database is
                          driven entirely by whether the <span class="bold"><strong>database</strong></span>
                          parameter is set to NULL.
                     </p>
          <p>
                             When using a Unicode build on Windows (the default), the <span class="bold"><strong>file</strong></span> argument will be interpreted as a UTF-8 
                             string, which is equivalent to ASCII for Latin characters.
                     </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50019200"></a>database</h4>
              </div>
            </div>
          </div>
          <p>
                          The <span class="bold"><strong>database</strong></span> parameter is optional,
                          and allows applications to have multiple databases in a single file. 
                          Although no <span class="bold"><strong>database</strong></span> parameter needs
                          to be specified, it is an error to attempt to open a second database
                          in a <span class="bold"><strong>file</strong></span> that was not initially
                          created using a <span class="bold"><strong>database</strong></span> name. 
                          Further, the <span class="bold"><strong>database</strong></span> parameter is
                          not supported by the Queue format.  Finally, when opening multiple
                          databases in the same physical file, it is important to consider
                          locking and memory cache issues; see 
                          <a href="../../programmer_reference/am_opensub.html" class="olink">Opening multiple databases in a single file</a> 
                          for more information.
                     </p>
          <p>
                         If both the <span class="bold"><strong>database</strong></span> and
                         <span class="bold"><strong>file</strong></span> parameters are NULL,
                          the database is strictly temporary and cannot be opened
                          by any other thread of control. Thus the database can only be accessed
                          by sharing the single database handle that created it, in
                          circumstances where doing so is safe.  
                      </p>
          <p>
                         If the <span class="bold"><strong>database</strong></span> parameter is not 
                         set to NULL, the database can be opened by other threads of control 
                         and will be replicated to client sites in any replication group, regardless
                         of whether the <span class="bold"><strong>file</strong></span> parameter is set to
                         NULL.
                     </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50092304"></a>type</h4>
              </div>
            </div>
          </div>
          <p>
                          The <span class="bold"><strong>type</strong></span> parameter is of type DBTYPE,
                          and must be set to one of <code class="literal">DB_BTREE</code>, 
                          <code class="literal">DB_HASH</code>, <code class="literal">DB_QUEUE</code>,
                          <code class="literal">DB_RECNO</code>, or <code class="literal">DB_UNKNOWN</code>.  If <span class="bold"><strong>type</strong></span> is DB_UNKNOWN, the database must already
                          exist and <code class="methodname">DB-&gt;open()</code> will automatically determine its type.  The
                          <a class="xref" href="dbget_type.html" title="DB-&gt;get_type()">DB-&gt;get_type()</a>  method
                          may be used to determine the underlying type of databases opened using
                          DB_UNKNOWN.
                     </p>
          <p>
                         It is an error to specify the incorrect <span class="bold"><strong>type</strong></span> 
                         for a database that already exists.
                     </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50093848"></a>flags</h4>
              </div>
            </div>
          </div>
          <p>
                        The <span class="bold"><strong>flags</strong></span> parameter must be set to zero or
                        by bitwise inclusively <span class="bold"><strong>OR</strong></span>'ing together one
                        or more of the following values: 
                </p>
          <div class="itemizedlist">
            <ul type="disc">
              <li>
                <p><a id="open_DB_AUTO_COMMIT"></a>
                                     <code class="literal">DB_AUTO_COMMIT</code>
                                </p>
                <p>
                                        Enclose the <code class="methodname">DB-&gt;open()</code> call within a transaction. If the call
                                        succeeds, the open operation will be recoverable and all
                                        subsequent database modification operations based on this
                                        handle will be transactionally protected. If the call fails,
                                        no database will have been created.
                                </p>
              </li>
              <li>
                <p><a id="open_DB_CREATE"></a>
                                     <code class="literal">DB_CREATE</code>
                                </p>
                <p>
                                        Create the database. If the database does not already exist
                                        and the <code class="literal">DB_CREATE</code> flag is not specified, the 
                                        <code class="methodname">DB-&gt;open()</code> will fail.
                                </p>
              </li>
              <li>
                <p><a id="open_DB_EXCL"></a>
                                     <code class="literal">DB_EXCL</code>
                                </p>
                <p>
                                        Return an error if the database already exists. The
                                        <code class="literal">DB_EXCL</code> flag is only meaningful 
                                        when specified with the <code class="literal">DB_CREATE</code>.
                                        flag.
                                </p>
              </li>
              <li>
                <p><a id="dbopen_DB_MULTIVERSION"></a>
                                     <code class="literal">DB_MULTIVERSION</code>
                                </p>
                <p>
                                        Open the database with support for 
                                        <a href="../../programmer_reference/transapp_read.html" class="olink">multiversion concurrency control</a>. 
                                        This will cause updates to the database to follow a
                                        copy-on-write protocol, which is required to support
                                        snapshot isolation. The <code class="literal">DB_MULTIVERSION</code>
                                        flag requires that the database be transactionally protected during its open
                                        and is not supported by the queue format.
                                </p>
              </li>
              <li>
                <p><a id="open_DB_NOMMAP"></a>
                                     <code class="literal">DB_NOMMAP</code>
                                </p>
                <p>
                                        Do not map this database into process memory (see the
                                        <a class="xref" href="envset_mp_mmapsize.html" title="DB_ENV-&gt;set_mp_mmapsize()">DB_ENV-&gt;set_mp_mmapsize()</a>  
                                        method for further information).
                                </p>
              </li>
              <li>
                <p><a id="dbopen_DB_RDONLY"></a>
                                         <code class="literal">DB_RDONLY</code>
                                </p>
                <p>
                                        Open the database for reading only. Any attempt to modify
                                        items in the database will fail, regardless of the actual
                                        permissions of any underlying files.
                                </p>
              </li>
              <li>
                <p><a id="dbopen_DB_READ_UNCOMMITTED"></a>
                                         <code class="literal">DB_READ_UNCOMMITTED</code>
                                </p>
                <p>
                                        Support transactional read operations with degree 1
                                        isolation. Read operations on the database may request the
                                        return of modified but not yet committed data. This flag
                                        must be specified on all 
                                        <a class="link" href="db.html" title="Chapter 2.  The DB Handle">DB</a>  
                                        handles used to perform dirty
                                        reads or database updates, otherwise requests for dirty
                                        reads may not be honored and the read may block.
                                </p>
              </li>
              <li>
                <p><a id="open_DB_THREAD"></a>
                                         <code class="literal">DB_THREAD</code>
                                </p>
                <p>
                                        Cause the <a class="link" href="db.html" title="Chapter 2.  The DB Handle">DB</a>  
                                        handle returned by <code class="methodname">DB-&gt;open()</code> to be <span class="emphasis"><em>free-threaded</em></span>; that is,
                                        concurrently usable by multiple threads in the address
                                        space.
                                </p>
              </li>
              <li>
                <p><a id="open_DB_TRUNCATE"></a>
                                         <code class="literal">DB_TRUNCATE</code>
                                </p>
                <p>
                                        Physically truncate the underlying file, discarding all
                                        previous databases it might have held. Underlying filesystem
                                        primitives are used to implement this flag. For this reason,
                                        it is applicable only to the file and cannot be used to
                                        discard databases within a file.
                                </p>
                <p>
                                        The <code class="literal">DB_TRUNCATE</code> flag cannot be lock or
                                        transaction-protected, and it is an error to specify it in a
                                        locking or transaction-protected environment.
                                </p>
              </li>
            </ul>
          </div>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50125584"></a>mode</h4>
              </div>
            </div>
          </div>
          <p>
                          On Windows systems, the mode parameter is ignored.                    
                     </p>
          <p>
                          On UNIX systems or in IEEE/ANSI Std 1003.1 (POSIX) environments, files
                          created by the database open are created with mode <span class="bold"><strong>mode</strong></span> (as described in <span class="bold"><strong>chmod</strong></span>(2)) and modified by the process' umask
                          value at the time of creation (see <span class="bold"><strong>umask</strong></span>(2)).  Created files are owned by the
                          process owner; the group ownership of created files is based on the
                          system and directory defaults, and is not further specified by
                          Berkeley DB.  System shared memory segments created by the database
                          open are created with mode <span class="bold"><strong>mode</strong></span>,
                          unmodified by the process' umask value.  If <span class="bold"><strong>mode</strong></span> is 0, the database open will use a default
                          mode of readable and writable by both owner and group.
                     </p>
        </div>
      </div>
      <div class="sect2" lang="en" xml:lang="en">
        <div class="titlepage">
          <div>
            <div>
              <h3 class="title"><a id="idp50100120"></a>Environment Variables</h3>
            </div>
          </div>
        </div>
        <p>
                         If the database was opened within a database environment, the
                         environment variable <span class="bold"><strong>DB_HOME</strong></span> may be used as the path of the
                         database environment home.
                    </p>
        <p>
                            <code class="methodname">DB-&gt;open()</code> is affected by any database directory specified using the
                            <a class="xref" href="envset_data_dir.html" title="DB_ENV-&gt;set_data_dir()">DB_ENV-&gt;set_data_dir()</a> 
                            method, or by setting the "set_data_dir" string in
                            the environment's 
                            <a href="../../programmer_reference/env_db_config.html#env_db_config.DB_CONFIG" class="olink">DB_CONFIG</a>
                            file.
                    </p>
        <div class="itemizedlist">
          <ul type="disc">
            <li>
              <p>
                                            <span class="bold"><strong>TMPDIR</strong></span>
                                    </p>
              <p>
                                            If the <span class="bold"><strong>file</strong></span>
                                            and <span class="bold"><strong>dbenv</strong></span>
                                            parameters to <code class="methodname">DB-&gt;open()</code> are <code class="literal">NULL</code>,
                                            the environment variable 
                                            <span class="bold"><strong>TMPDIR</strong></span>
                                            may be used as a
                                            directory in which to create temporary backing files
                                    </p>
            </li>
          </ul>
        </div>
      </div>
      <div class="sect2" lang="en" xml:lang="en">
        <div class="titlepage">
          <div>
            <div>
              <h3 class="title"><a id="idp50145888"></a>Errors</h3>
            </div>
          </div>
        </div>
        <p>
                         The <code class="methodname">DB-&gt;open()</code> <span>
            <span>
                 method may fail and return one of the following non-zero errors:
            </span>
            
        </span>
                    </p>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50092616"></a>DB_LOCK_DEADLOCK</h4>
              </div>
            </div>
          </div>
          <p>
                A transactional database environment operation was selected to resolve
                a deadlock.
            </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50129520"></a>DB_LOCK_NOTGRANTED</h4>
              </div>
            </div>
          </div>
          <p>
                A Berkeley DB Concurrent Data Store database environment configured
                for lock timeouts was unable to grant a lock in the allowed time.
            </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50127976"></a>ENOENT</h4>
              </div>
            </div>
          </div>
          <p>
                The file or directory does not exist.
            </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50133824"></a>ENOENT</h4>
              </div>
            </div>
          </div>
          <p>
                A nonexistent <span class="bold"><strong>re_source</strong></span> file was specified.
            </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50097656"></a>DB_OLD_VERSION</h4>
              </div>
            </div>
          </div>
          <p>
                The database cannot be opened without being first upgraded.
            </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50148440"></a>EEXIST</h4>
              </div>
            </div>
          </div>
          <p>
                <code class="literal">DB_CREATE</code> and <code class="literal">DB_EXCL</code>
                were specified and the database exists.
            </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50143160"></a>EINVAL</h4>
              </div>
            </div>
          </div>
          <p>
                           If an unknown database type, page size, hash function, pad byte, byte order, or a flag value
                           or parameter that is incompatible with the specified database was specified; the 
                           <a class="link" href="envopen.html#envopen_DB_THREAD">DB_THREAD</a> 
                           flag was specified and fast mutexes are not available for this architecture; the 
                           <a class="link" href="envopen.html#envopen_DB_THREAD">DB_THREAD</a> 
                           flag was specified to <code class="methodname">DB-&gt;open()</code>, but was 
                           not specified to the <code class="methodname">DB_ENV-&gt;open()</code> call for the
                           environment in which the <a class="link" href="db.html" title="Chapter 2.  The DB Handle">DB</a> 
                           handle was created; a backing flat text file was specified with either the 
                           <a class="link" href="envopen.html#envopen_DB_THREAD">DB_THREAD</a> 
                           flag or the provided database environment supports transaction
                           processing; or if an invalid flag value or parameter was specified.
                     </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50098056"></a>  DB_REP_HANDLE_DEAD</h4>
              </div>
            </div>
          </div>
          <p>
                When a client synchronizes with the master, it is possible for committed
                transactions to be rolled back. This invalidates all  the database and cursor
                handles opened in the replication environment. Once this occurs, an attempt to use
                such a handle will 
                
                return <code class="literal">DB_REP_HANDLE_DEAD</code>.
                The application will need to discard the handle and open a new one in order to
                continue processing.
            </p>
        </div>
        <div class="sect3" lang="en" xml:lang="en">
          <div class="titlepage">
            <div>
              <div>
                <h4 class="title"><a id="idp50145352"></a>DB_REP_LOCKOUT</h4>
              </div>
            </div>
          </div>
          <p>
                The operation was blocked by client/master synchronization.
            </p>
        </div>
      </div>
      <div class="sect2" lang="en" xml:lang="en">
        <div class="titlepage">
          <div>
            <div>
              <h3 class="title"><a id="idp50144568"></a>Class</h3>
            </div>
          </div>
        </div>
        <p>
                <a class="link" href="db.html" title="Chapter 2.  The DB Handle">DB</a>  
            </p>
      </div>
      <div class="sect2" lang="en" xml:lang="en">
        <div class="titlepage">
          <div>
            <div>
              <h3 class="title"><a id="idp50113216"></a>See Also</h3>
            </div>
          </div>
        </div>
        <p>
                     <a class="xref" href="db.html#dblist" title="Database and Related Methods">Database and Related Methods</a> 
                </p>
      </div>
    </div>
    <div class="navfooter">
      <hr />
      <table width="100%" summary="Navigation footer">
        <tr>
          <td width="40%" align="left"><a accesskey="p" href="dbkey_range.html">Prev</a> </td>
          <td width="20%" align="center">
            <a accesskey="u" href="db.html">Up</a>
          </td>
          <td width="40%" align="right"> <a accesskey="n" href="dbput.html">Next</a></td>
        </tr>
        <tr>
          <td width="40%" align="left" valign="top">DB-&gt;key_range() </td>
          <td width="20%" align="center">
            <a accesskey="h" href="index.html">Home</a>
          </td>
          <td width="40%" align="right" valign="top"> DB-&gt;put()</td>
        </tr>
      </table>
    </div>
  </body>
</html>