File: indexes.html

package info (click to toggle)
db5.3 5.3.28%2Bdfsg1-0.8
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 158,400 kB
  • sloc: ansic: 448,406; java: 111,824; tcl: 80,544; sh: 44,326; cs: 33,697; cpp: 21,604; perl: 14,557; xml: 10,799; makefile: 4,077; javascript: 1,998; yacc: 1,003; awk: 965; sql: 801; erlang: 342; python: 216; php: 24; asm: 14
file content (360 lines) | stat: -rw-r--r-- 13,285 bytes parent folder | download | duplicates (8)
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
<?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>Chapter 5. Secondary Databases</title>
    <link rel="stylesheet" href="gettingStarted.css" type="text/css" />
    <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
    <link rel="start" href="index.html" title="Getting Started with Berkeley DB" />
    <link rel="up" href="index.html" title="Getting Started with Berkeley DB" />
    <link rel="prev" href="CoreCursorUsage.html" title="Cursor Example" />
    <link rel="next" href="keyCreator.html" title="Implementing Key Extractors" />
  </head>
  <body>
    <div xmlns="" class="navheader">
      <div class="libver">
        <p>Library Version 11.2.5.3</p>
      </div>
      <table width="100%" summary="Navigation header">
        <tr>
          <th colspan="3" align="center">Chapter 5. Secondary Databases</th>
        </tr>
        <tr>
          <td width="20%" align="left"><a accesskey="p" href="CoreCursorUsage.html">Prev</a> </td>
          <th width="60%" align="center"> </th>
          <td width="20%" align="right"> <a accesskey="n" href="keyCreator.html">Next</a></td>
        </tr>
      </table>
      <hr />
    </div>
    <div class="chapter" lang="en" xml:lang="en">
      <div class="titlepage">
        <div>
          <div>
            <h2 class="title"><a id="indexes"></a>Chapter 5. Secondary Databases</h2>
          </div>
        </div>
      </div>
      <div class="toc">
        <p>
          <b>Table of Contents</b>
        </p>
        <dl>
          <dt>
            <span class="sect1">
              <a href="indexes.html#CoreDbAssociate">Opening and Closing Secondary Databases</a>
            </span>
          </dt>
          <dt>
            <span class="sect1">
              <a href="keyCreator.html">Implementing Key 
        
        <span>Extractors</span>
        </a>
            </span>
          </dt>
          <dd>
            <dl>
              <dt>
                <span class="sect2">
                  <a href="keyCreator.html#multikeys">Working with Multiple Keys</a>
                </span>
              </dt>
            </dl>
          </dd>
          <dt>
            <span class="sect1">
              <a href="readSecondary.html">Reading Secondary Databases</a>
            </span>
          </dt>
          <dt>
            <span class="sect1">
              <a href="secondaryDelete.html">Deleting Secondary Database Records</a>
            </span>
          </dt>
          <dt>
            <span class="sect1">
              <a href="secondaryCursor.html">
        
        <span>Using Cursors with Secondary Databases</span>
    </a>
            </span>
          </dt>
          <dt>
            <span class="sect1">
              <a href="joins.html">Database Joins</a>
            </span>
          </dt>
          <dd>
            <dl>
              <dt>
                <span class="sect2">
                  <a href="joins.html#joinUsage">Using Join Cursors</a>
                </span>
              </dt>
            </dl>
          </dd>
          <dt>
            <span class="sect1">
              <a href="coreindexusage.html">Secondary Database Example</a>
            </span>
          </dt>
          <dd>
            <dl>
              <dt>
                <span class="sect2">
                  <a href="coreindexusage.html#edlWIndexes">Secondary Databases with example_database_load</a>
                </span>
              </dt>
              <dt>
                <span class="sect2">
                  <a href="coreindexusage.html#edrWIndexes">Secondary Databases with example_database_read</a>
                </span>
              </dt>
            </dl>
          </dd>
        </dl>
      </div>
      <p>
    Usually you find database records by means of the record's key.  However,
    the key that you use for your record will not always contain the
    information required to provide you with rapid access to the data that you
    want to retrieve. For example, suppose your 
        
        <span>database</span>
    contains records related to users. The key might be a string that is some
    unique identifier for the person, such as a user ID. Each record's data,
    however, would likely contain a complex object containing details about
    people such as names, addresses, phone numbers, and so forth.
    While your application may frequently want to query a person by user
    ID (that is, by the information stored in the key), it may also on occasion
    want to locate people by, say, their name.
  </p>
      <p>
    Rather than iterate through all of the records in your database, examining
    each in turn for a given person's name, you create indexes based on names
    and then just search that index for the name that you want.  You can do this
    using secondary databases. In DB, the 
        
        <span>database</span> 
    that contains your data is called a
    <span class="emphasis"><em>primary database</em></span>. A database that provides an
    alternative set of keys to access that data is called a <span class="emphasis"><em>secondary
    database</em></span><span>.</span> In a secondary database, the keys are your alternative 
    (or secondary) index, and the data corresponds to a primary record's key.
  </p>
      <p>
    You create a secondary database by creating the database, opening it, and
    then <span class="emphasis"><em>associating</em></span> the database with 
    the <span class="emphasis"><em>primary</em></span> database (that is, the database for which
    you are creating the index). As a part of associating
    the secondary database to the primary, you must provide a callback that is
    used to create the secondary database keys. Typically this callback creates
    a key based on data found in the primary database record's key or data.
  </p>
      <p>
  Once opened, DB manages secondary databases for you. Adding or deleting
  records in your primary database causes DB to update the secondary as
  necessary. Further, changing a record's data in the primary database may cause
  DB to modify a record in the secondary, depending on whether the change
  forces a modification of a key in the secondary database.
  </p>
      <p>
    Note that you can not write directly to a secondary database. 

    

    <span>Any attempt to write to a secondary database
    results in a non-zero status return.</span>
    
    To change the data referenced by a 
        
        <span>secondary</span>
    record, modify the primary database instead. The exception to this rule is
    that delete operations are allowed on the
         
        <span>secondary database.</span> 
    
    See <a class="xref" href="secondaryDelete.html" title="Deleting Secondary Database Records">Deleting Secondary Database Records</a> for more
    information.
  </p>
      <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
        <h3 class="title">Note</h3>
        <p>

        Secondary database records are updated/created by DB 
        only if the 
            
            <span>key creator callback function</span>
        returns 
             
            <span><code class="literal">0</code>.</span> 
        If 
             
            <span>a value other than <code class="literal">0</code></span>
        is returned, then DB will not add the key to the secondary database, and 
        in the event of a record update it will remove any existing key. 

        <span>Note that the callback can use either
        <code class="literal">DB_DONOTINDEX</code> or some error code outside of DB's
        name space to indicate that the entry should not be indexed.</span>

     </p>
        <p>
        See <a class="xref" href="keyCreator.html" title="Implementing Key Extractors">Implementing Key 
        
        <span>Extractors</span>
        </a> for more
            
            <span>information.</span>
    
    </p>
      </div>
      <p>
    When you read a record from a secondary database, DB automatically
    returns 
         
        <span>the data and optionally the key</span> 
    from the corresponding record in the primary database.
    
  </p>
      <div class="sect1" lang="en" xml:lang="en">
        <div class="titlepage">
          <div>
            <div>
              <h2 class="title" style="clear: both"><a id="CoreDbAssociate"></a>Opening and Closing Secondary Databases</h2>
            </div>
          </div>
        </div>
        <p>
        You manage secondary database opens and closes in the same way as you
        would any normal database. The only difference is that:
    </p>
        <div class="itemizedlist">
          <ul type="disc">
            <li>
              <p>
                You must associate the secondary to a primary database using
                    <span><code class="methodname">DB-&gt;associate()</code>.</span>
                    
            </p>
            </li>
            <li>
              <p>
                When closing your databases, it is a good idea to make sure you
                close your secondaries before closing your primaries. This is
                particularly true if your database closes are not single
                threaded.
            </p>
            </li>
          </ul>
        </div>
        <p>
        When you associate a secondary to a primary database, you must provide a
        callback that is used to generate the secondary's keys. These
        callbacks are described in the next section.
     </p>
        <p>
        For example, to open a secondary database and associate it to a primary
        database:
     </p>
        <a id="c_index1"></a>
        <pre class="programlisting">#include &lt;db.h&gt;

...

DB *dbp, *sdbp;    /* Primary and secondary DB handles */
u_int32_t flags;   /* Primary database open flags */
int ret;           /* Function return value */

/* Primary */
ret = db_create(&amp;dbp, NULL, 0);
if (ret != 0) {
  /* Error handling goes here */
}

/* Secondary */
ret = db_create(&amp;sdbp, NULL, 0);
if (ret != 0) {
  /* Error handling goes here */
}

/* Usually we want to support duplicates for secondary databases */
ret = sdbp-&gt;set_flags(sdbp, DB_DUPSORT);
if (ret != 0) {
  /* Error handling goes here */
}


/* Database open flags */
flags = DB_CREATE;    /* If the database does not exist,
                       * create it.*/

/* open the primary database */
ret = dbp-&gt;open(dbp,        /* DB structure pointer */
                NULL,       /* Transaction pointer */
                "my_db.db", /* On-disk file that holds the database. */
                NULL,       /* Optional logical database name */
                DB_BTREE,   /* Database access method */
                flags,      /* Open flags */
                0);         /* File mode (using defaults) */
if (ret != 0) {
  /* Error handling goes here */
}

/* open the secondary database */
ret = sdbp-&gt;open(sdbp,          /* DB structure pointer */
                 NULL,          /* Transaction pointer */
                 "my_secdb.db", /* On-disk file that holds the 
                                   database. */
                 NULL,          /* Optional logical database name */
                 DB_BTREE,      /* Database access method */
                 flags,         /* Open flags */
                 0);            /* File mode (using defaults) */
if (ret != 0) {
  /* Error handling goes here */
}

/* Now associate the secondary to the primary */
dbp-&gt;associate(dbp,            /* Primary database */
               NULL,           /* TXN id */
               sdbp,           /* Secondary database */
               get_sales_rep,  /* Callback used for key creation. Not
                                * defined in this example. See the next
                                * section. */
               0);              /* Flags */</pre>
        <p>
    Closing the primary and secondary databases is accomplished exactly as you
    would for any database:
  </p>
        <a id="c_index2"></a>
        <pre class="programlisting">/* Close the secondary before the primary */
if (sdbp != NULL)
    sdbp-&gt;close(sdbp, 0);
if (dbp != NULL)
    dbp-&gt;close(dbp, 0); </pre>
      </div>
    </div>
    <div class="navfooter">
      <hr />
      <table width="100%" summary="Navigation footer">
        <tr>
          <td width="40%" align="left"><a accesskey="p" href="CoreCursorUsage.html">Prev</a> </td>
          <td width="20%" align="center"> </td>
          <td width="40%" align="right"> <a accesskey="n" href="keyCreator.html">Next</a></td>
        </tr>
        <tr>
          <td width="40%" align="left" valign="top">Cursor Example </td>
          <td width="20%" align="center">
            <a accesskey="h" href="index.html">Home</a>
          </td>
          <td width="40%" align="right" valign="top"> Implementing Key 
        
        <span>Extractors</span>
        </td>
        </tr>
      </table>
    </div>
  </body>
</html>