Sophie

Sophie

distrib > Fedora > 15 > i386 > by-pkgid > c9a08a0a19ffad09f746f4815730d201 > files > 2527

libdb-devel-5.1.25-3.fc15.i686.rpm

<?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>Opening the 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="Berkeley DB Programmer's Reference Guide" />
    <link rel="up" href="transapp.html" title="Chapter 11.  Berkeley DB Transactional Data Store Applications" />
    <link rel="prev" href="transapp_env_open.html" title="Opening the environment" />
    <link rel="next" href="transapp_put.html" title="Recoverability and deadlock handling" />
  </head>
  <body>
    <div class="navheader">
      <table width="100%" summary="Navigation header">
        <tr>
          <th colspan="3" align="center">Opening the databases</th>
        </tr>
        <tr>
          <td width="20%" align="left"><a accesskey="p" href="transapp_env_open.html">Prev</a> </td>
          <th width="60%" align="center">Chapter 11. 
		Berkeley DB Transactional Data Store Applications
        </th>
          <td width="20%" align="right"> <a accesskey="n" href="transapp_put.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="transapp_data_open"></a>Opening the databases</h2>
          </div>
        </div>
      </div>
      <p>Next, we open three databases ("color" and "fruit" and "cats"), in the
database environment.  Again, our <a href="../api_reference/C/db.html" class="olink">DB</a> database handles are
declared to be free-threaded using the <a href="../api_reference/C/dbopen.html#open_DB_THREAD" class="olink">DB_THREAD</a> flag, and so
may be used by any number of threads we subsequently create.</p>
      <pre class="programlisting">int
main(int argc, char *argv)
{
    extern int optind;
    DB *db_cats, *db_color, *db_fruit;
    DB_ENV *dbenv;
    int ch;

    while ((ch = getopt(argc, argv, "")) != EOF)
        switch (ch) {
        case '?':
        default:
            usage();
        }
    argc -= optind;
    argv += optind;

    env_dir_create();
    env_open(&amp;dbenv);

<span class="bold"><strong>    /* Open database: Key is fruit class; Data is specific type. */
    if (db_open(dbenv, &amp;db_fruit, "fruit", 0))
        return (1);

    /* Open database: Key is a color; Data is an integer. */
    if (db_open(dbenv, &amp;db_color, "color", 0))
        return (1);

    /*
     * Open database:
     *    Key is a name; Data is: company name, cat breeds.
     */
    if (db_open(dbenv, &amp;db_cats, "cats", 1))
        return (1);</strong></span>

    return (0);
}

<span class="bold"><strong>int
db_open(DB_ENV *dbenv, DB **dbp, char *name, int dups)
{
    DB *db;
    int ret;

    /* Create the database handle. */
    if ((ret = db_create(&amp;db, dbenv, 0)) != 0) {
        dbenv-&gt;err(dbenv, ret, "db_create");
        return (1);
    }

    /* Optionally, turn on duplicate data items. */
    if (dups &amp;&amp; (ret = db-&gt;set_flags(db, DB_DUP)) != 0) {
        (void)db-&gt;close(db, 0);
        dbenv-&gt;err(dbenv, ret, "db-&gt;set_flags: DB_DUP");
        return (1);
    }

    /*
     * Open a database in the environment:
     *    create if it doesn't exist
     *    free-threaded handle
     *    read/write owner only
     */
    if ((ret = db-&gt;open(db, NULL, name, NULL, DB_BTREE,
        DB_AUTO_COMMIT | DB_CREATE | DB_THREAD, S_IRUSR | S_IWUSR)) != 0) {
        (void)db-&gt;close(db, 0);
        dbenv-&gt;err(dbenv, ret, "db-&gt;open: %s", name);
        return (1);
    }

    *dbp = db;
    return (0);
}</strong></span></pre>
      <p>After opening the database, we can use the <a href="../api_reference/C/db_stat.html" class="olink">db_stat utility</a> to
display information about a database we have created:</p>
      <pre class="programlisting">prompt&gt; db_stat -h TXNAPP -d color
53162   Btree magic number.
8       Btree version number.
Flags:
2       Minimum keys per-page.
8192    Underlying database page size.
1       Number of levels in the tree.
0       Number of unique keys in the tree.
0       Number of data items in the tree.
0       Number of tree internal pages.
0       Number of bytes free in tree internal pages (0% ff).
1       Number of tree leaf pages.
8166    Number of bytes free in tree leaf pages (0.% ff).
0       Number of tree duplicate pages.
0       Number of bytes free in tree duplicate pages (0% ff).
0       Number of tree overflow pages.
0       Number of bytes free in tree overflow pages (0% ff).
0       Number of pages on the free list.</pre>
      <p>The database open must be enclosed within a transaction in order to be
recoverable.  The transaction will ensure that created files are
re-created in recovered environments (or do not appear at all).
Additional database operations or operations on other databases can be
included in the same transaction, of course.  In the simple case, where
the open is the only operation in the transaction, an application can
set the <a href="../api_reference/C/envset_flags.html#envset_flags_DB_AUTO_COMMIT" class="olink">DB_AUTO_COMMIT</a> flag instead of creating and managing
its own transaction handle.  The <a href="../api_reference/C/envset_flags.html#envset_flags_DB_AUTO_COMMIT" class="olink">DB_AUTO_COMMIT</a> flag will
internally wrap the operation in a transaction, simplifying application
code.</p>
      <p>The previous example is the simplest case of transaction protection for
database open.  Obviously, additional database operations can be done
in the scope of the same transaction.  For example, an application
maintaining a list of the databases in a database environment in a
well-known file might include an update of the list in the same
transaction in which the database is created.  Or, an application might
create both a primary and secondary database in a single transaction.</p>
      <p><a href="../api_reference/C/db.html" class="olink">DB</a> handles that will later be used for transactionally protected
database operations must be opened within a transaction.  Specifying a
transaction handle to database operations using <a href="../api_reference/C/db.html" class="olink">DB</a> handles not
opened within a transaction will return an error.  Similarly, not
specifying a transaction handle to database operations that will modify
the database, using handles that were opened within a transaction, will
also return an error.</p>
    </div>
    <div class="navfooter">
      <hr />
      <table width="100%" summary="Navigation footer">
        <tr>
          <td width="40%" align="left"><a accesskey="p" href="transapp_env_open.html">Prev</a> </td>
          <td width="20%" align="center">
            <a accesskey="u" href="transapp.html">Up</a>
          </td>
          <td width="40%" align="right"> <a accesskey="n" href="transapp_put.html">Next</a></td>
        </tr>
        <tr>
          <td width="40%" align="left" valign="top">Opening the environment </td>
          <td width="20%" align="center">
            <a accesskey="h" href="index.html">Home</a>
          </td>
          <td width="40%" align="right" valign="top"> Recoverability and deadlock handling</td>
        </tr>
      </table>
    </div>
  </body>
</html>