Gecko [ 122.154.134.11 ]

Name	Size	Permission
cput.html	1.73 KB	-rw-r--r--
disk.html	1.67 KB	-rw-r--r--
enomem.html	2.93 KB	-rw-r--r--
err.html	2.21 KB	-rw-r--r--
fileopen.html	1.51 KB	-rw-r--r--
intro.html	1.62 KB	-rw-r--r--
java.html	3.62 KB	-rw-r--r--
log.html	2.12 KB	-rw-r--r--
repl.html	2.56 KB	-rw-r--r--
rtc.html	1.68 KB	-rw-r--r--
stat.html	1.7 KB	-rw-r--r--
toc.html	1.85 KB	-rw-r--r--
verb.html	2.43 KB	-rw-r--r--

Code Editor : enomem.html

<html>
<head>
<title>Berkeley DB Reference Guide: Release 4.3: ENOMEM and DbMemoryException</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<table width="100%"><tr valign=top>
<td><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></td>
<td align=right><a href="../upgrade.4.3/fileopen.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.4.3/repl.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Release 4.3: ENOMEM and DbMemoryException
In versions of Berkeley DB before 4.3, the error ENOMEM was used to
indicate that the buffer in a <a href="../../api_c/dbt_class.html">DBT</a> configured with
<a href="../../api_c/dbt_class.html#DB_DBT_USERMEM">DB_DBT_USERMEM</a> was too small to hold a key or data item being
retrieved. The 4.3 release adds a new error, <a href="../../api_c/dbt_class.html#DB_BUFFER_SMALL">DB_BUFFER_SMALL</a>,
that is returned in this case.
The reason for the change is that the use of ENOMEM was
ambiguous: calls such as <a href="../../api_c/db_get.html">DB-&gt;get</a> or <a href="../../api_c/dbc_get.html">DBcursor-&gt;get</a> could return
ENOMEM either if a <a href="../../api_c/dbt_class.html">DBT</a> was too small or if some resource
was exhausted.
The result is that starting with the 4.3 release, C applications should
always treat ENOMEM as a fatal error. Code that checked for
the ENOMEM return and allocated a new buffer should be changed
to check for <a href="../../api_c/dbt_class.html#DB_BUFFER_SMALL">DB_BUFFER_SMALL</a>.
In C++ applications configured for exceptions, a
<a href="../../api_cxx/memp_class.html">DbMemoryException</a> will continue to be thrown in both cases,
and applications should check the errno in the exception to determine
which error occurred.
In Java applications, a DbMemoryException will be thrown
when a Dbt is too small to hold a return value, and an
OutOfMemoryError will be thrown in all cases of resource
exhaustion.
<table width="100%"><tr><td> </td><td align=right><a href="../upgrade.4.3/fileopen.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.4.3/repl.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

${this.title}

Code Editor : enomem.html