2
<!--Copyright 1997-2002 by Sleepycat Software, Inc.-->
3
<!--All rights reserved.-->
4
<!--See the file LICENSE for redistribution information.-->
7
<title>Berkeley DB Reference Guide: Release 4.0: memp_XXX</title>
8
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
9
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
12
<table width="100%"><tr valign=top>
13
<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></h3></td>
14
<td align=right><a href="../../ref/upgrade.4.0/log.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/upgrade.4.0/txn.html"><img src="../../images/next.gif" alt="Next"></a>
17
<h1 align=center>Release 4.0: memp_XXX</h1>
18
<p>The C API for the Berkeley DB Memory Pool subsystem was reworked in the 4.0
20
<p><table border=1 align=center>
21
<tr><th>Historic functional interface</th><th>Berkeley DB 4.X method</th></tr>
22
<tr><td>memp_register</td><td><a href="../../api_c/memp_register.html">DB_ENV->memp_register</a></td></tr>
23
<tr><td>memp_stat</td><td><a href="../../api_c/memp_stat.html">DB_ENV->memp_stat</a></td></tr>
24
<tr><td>memp_sync</td><td><a href="../../api_c/memp_sync.html">DB_ENV->memp_sync</a></td></tr>
25
<tr><td>memp_trickle</td><td><a href="../../api_c/memp_trickle.html">DB_ENV->memp_trickle</a></td></tr>
26
<tr><td>memp_fopen</td><td><a href="../../api_c/memp_fcreate.html">DB_ENV->memp_fcreate</a></td></tr>
27
<tr><td>DB_MPOOL_FINFO: ftype</td><td><a href="../../api_c/memp_set_ftype.html">DB_MPOOLFILE->set_ftype</a></td></tr>
28
<tr><td>DB_MPOOL_FINFO: pgcookie</td><td><a href="../../api_c/memp_set_pgcookie.html">DB_MPOOLFILE->set_pgcookie</a></td></tr>
29
<tr><td>DB_MPOOL_FINFO: fileid</td><td><a href="../../api_c/memp_set_fileid.html">DB_MPOOLFILE->set_fileid</a></td></tr>
30
<tr><td>DB_MPOOL_FINFO: lsn_offset</td><td><a href="../../api_c/memp_set_lsn_offset.html">DB_MPOOLFILE->set_lsn_offset</a></td></tr>
31
<tr><td>DB_MPOOL_FINFO: clear_len</td><td><a href="../../api_c/memp_set_clear_len.html">DB_MPOOLFILE->set_clear_len</a></td></tr>
32
<tr><td>memp_fopen</td><td><a href="../../api_c/memp_fopen.html">DB_MPOOLFILE->open</a></td></tr>
33
<tr><td>memp_fclose</td><td><a href="../../api_c/memp_fclose.html">DB_MPOOLFILE->close</a></td></tr>
34
<tr><td>memp_fput</td><td><a href="../../api_c/memp_fput.html">DB_MPOOLFILE->put</a></td></tr>
35
<tr><td>memp_fset</td><td><a href="../../api_c/memp_fset.html">DB_MPOOLFILE->set</a></td></tr>
36
<tr><td>memp_fsync</td><td><a href="../../api_c/memp_fsync.html">DB_MPOOLFILE->sync</a></td></tr>
38
<p>Applications calling any of the memp_register, memp_stat, memp_sync or
39
memp_trickle interfaces should update those calls to use the enclosing
40
<a href="../../api_c/env_class.html">DB_ENV</a> handle's method (easily done as the first argument to the
41
existing call is the correct <a href="../../api_c/env_class.html">DB_ENV</a> handle).
42
<p>In addition, the <a href="../../api_c/memp_stat.html">DB_ENV->memp_stat</a> call has been changed in the 4.0
43
release to take a flags argument. To leave their historic behavior
44
unchanged, applications should add a final argument of 0 to any calls
45
made to <a href="../../api_c/memp_stat.html">DB_ENV->memp_stat</a>.
46
<p>Applications calling the memp_fopen interface should update those calls
47
as follows: First, acquire a <a href="../../api_c/mempfile_class.html">DB_MPOOLFILE</a> handle using the
48
<a href="../../api_c/memp_fcreate.html">DB_ENV->memp_fcreate</a> method. Second, if the DB_MPOOL_FINFO structure
49
reference passed to the memp_fopen interface was non-NULL, call the
50
<a href="../../api_c/mempfile_class.html">DB_MPOOLFILE</a> method corresponding to each initialized field in
51
the DB_MPOOL_FINFO structure. Third, call the <a href="../../api_c/memp_fopen.html">DB_MPOOLFILE->open</a> method
52
method to open the underlying file. If the <a href="../../api_c/memp_fopen.html">DB_MPOOLFILE->open</a> method call
53
fails, then <a href="../../api_c/memp_fclose.html">DB_MPOOLFILE->close</a> method must be called to destroy the allocated
55
<p>Applications calling the memp_fopen, memp_fclose, memp_fput, memp_fset,
56
or memp_fsync interfaces should update those calls to use the enclosing
57
<a href="../../api_c/mempfile_class.html">DB_MPOOLFILE</a> handle's method. Again, this is easily done as the
58
first argument to the existing call is the correct <a href="../../api_c/mempfile_class.html">DB_MPOOLFILE</a>
59
handle. With one exception, the calling conventions of the old a new
60
interfaces are identical; the one exception is the <a href="../../api_c/memp_fclose.html">DB_MPOOLFILE->close</a> method,
61
which requires an additional flag parameter that should be set to 0.
62
<table width="100%"><tr><td><br></td><td align=right><a href="../../ref/upgrade.4.0/log.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/upgrade.4.0/txn.html"><img src="../../images/next.gif" alt="Next"></a>
64
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>