Chapter 3. - Access Method Operations -

Chapter 3. Access Method Operations

@@ -52,24 +48,25 @@

- Opening multiple databases in a single file + Opening multiple databases in a + single file

- Configuring databases sharing a file + Configuring databases sharing a file
- Caching databases sharing a file + Caching databases sharing a file
- Locking in databases based on sharing a file + Locking in databases based on sharing a file

@@ -83,17 +80,20 @@

- Specifying partition keys + Specifying partition + keys
- Partitioning callback + Partitioning + callback
- Placing partition files + Placing partition + files

@@ -130,7 +130,8 @@

- Database verification and salvage + Database verification and + salvage

@@ -152,7 +153,7 @@

- Error Handling With Secondary Indexes + Error Handling With Secondary Indexes

@@ -171,7 +172,8 @@

- Retrieving records with a cursor + Retrieving records with a + cursor
@@ -208,21 +210,33 @@

Once a database handle has been created using db_create(), there -are several standard access method operations. Each of these operations -is performed using a method referred to by the returned handle. -Generally, the database will be opened using DB->open(). If the -database is from an old release of Berkeley DB, it may need to be upgraded to -the current release before it is opened using DB->upgrade().

Once a database has been opened, records may be retrieved (DB->get()), -stored (DB->put()), and deleted (DB->del()).

Additional operations supported by the database handle include -statistics (DB->stat()), truncation (DB->truncate()), -version upgrade (DB->upgrade()), verification and salvage -(DB->verify()), flushing to a backing file (DB->sync()), -and association of secondary indices (DB->associate()). Database -handles are eventually closed using DB->close().

For more information on the access method operations supported by the database handle, see the Database and Related Methods section in the Berkeley DB C API Reference Guide.

+ Once a database handle has been created using db_create(), + there are several standard access method operations. Each of + these operations is performed using a method referred to by + the returned handle. Generally, the database will be opened + using DB->open(). If the database is from an old release of + Berkeley DB, it may need to be upgraded to the current release + before it is opened using DB->upgrade(). +

+ Once a database has been opened, records may be retrieved + (DB->get()), stored (DB->put()), and deleted (DB->del()). +

+ Additional operations supported by the database handle + include statistics (DB->stat()), truncation (DB->truncate()), + version upgrade (DB->upgrade()), verification and salvage + (DB->verify()), flushing to a backing file (DB->sync()), and + association of secondary indices (DB->associate()). Database + handles are eventually closed using DB->close(). +

+ For more information on the access method operations + supported by the database handle, see the Database and Related + Methods section in the + Berkeley DB C API Reference Guide. +

@@ -232,7 +246,8 @@ handles are eventually closed using

- The DB->open() method opens a database, and takes five arguments: + The DB->open() method opens a database, and takes five + arguments:

@@ -240,7 +255,7 @@ handles are eventually closed using file

- The name of the file to be opened. + The name of the file to be opened.

database @@ -251,23 +266,24 @@ handles are eventually closed using type

- The type of database to open. This value will be one of - the five access methods Berkeley DB supports: DB_BTREE, - DB_HASH, DB_HEAP, DB_QUEUE or DB_RECNO, or the special - value DB_UNKNOWN, which allows you to open an existing file - without knowing its type. +

+ The type of database to open. This value will + be one of the five access methods Berkeley DB + supports: DB_BTREE, DB_HASH, DB_HEAP, DB_QUEUE or + DB_RECNO, or the special value DB_UNKNOWN, which + allows you to open an existing file without knowing + its type.

mode

The permissions to give to any created file.

- There are a few flags that you can set to customize open: +

+ There are a few flags that you can set to customize open:

- Create the underlying database and any necessary physical files. +; + Create the underlying database and any + necessary physical files.
@@ -301,8 +318,9 @@ handles are eventually closed using: - The returned handle is free-threaded, that is, it can be - used simultaneously by multiple threads within the process. + The returned handle is free-threaded, that is, + it can be used simultaneously by multiple threads + within the process.
@@ -310,19 +328,19 @@ handles are eventually closed using: - Physically truncate the underlying database file, - discarding all databases it contained. Underlying - filesystem primitives are used to implement this flag. For - this reason it is only applicable to the physical file and - cannot be used to discard individual databases from within - physical files. + Physically truncate the underlying database + file, discarding all databases it contained. + Underlying filesystem primitives are used to implement + this flag. For this reason it is only applicable to + the physical file and cannot be used to discard + individual databases from within physical files.
DB_UPGRADE: +; Upgrade the database format as necessary.

@@ -342,7 +360,8 @@ handles are eventually closed using Home -

Chapter 3. - Access Method Operations -			Chapter 3. Access Method Operations
Prev	Opening multiple databases in a single file	Opening multiple databases in a + single file