libdb/docs/upgrading/upgrade_4_2_del.html
2012-11-14 16:35:20 -05:00

75 lines
3.7 KiB
HTML
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?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>DB-&gt;del</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 Upgrade Guide" />
<link rel="up" href="upgrade_4_2_toc.html" title="Chapter 8. Upgrading Berkeley DB 4.1 applications to Berkeley DB 4.2" />
<link rel="prev" href="upgrade_4_2_client.html" title="DB_CLIENT" />
<link rel="next" href="upgrade_4_2_priority.html" title="DB-&gt;set_cache_priority" />
</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">DB-&gt;del</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="upgrade_4_2_client.html">Prev</a> </td>
<th width="60%" align="center">Chapter 8. Upgrading Berkeley DB 4.1 applications to Berkeley DB 4.2</th>
<td width="20%" align="right"> <a accesskey="n" href="upgrade_4_2_priority.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="upgrade_4_2_del"></a>DB-&gt;del</h2>
</div>
</div>
</div>
<p>
In previous releases, the C++ <a href="../api_reference/CXX/dbdel.html" class="olink">Db::del</a> and
Java <code class="classname">Db.delete()</code> methods threw exceptions encapsulating the
<a href="../programmer_reference/program_errorret.html#program_errorret.DB_KEYEMPTY" class="olink">DB_KEYEMPTY</a> error in some
cases when called on Queue and Recno databases. Unfortunately, this was undocumented
behavior.
</p>
<p>
For consistency with the other Berkeley DB methods that handle
<a href="../programmer_reference/program_errorret.html#program_errorret.DB_KEYEMPTY" class="olink">DB_KEYEMPTY</a>, this is no longer the case. Applications calling the
<a href="../api_reference/CXX/dbdel.html" class="olink">Db::del</a> and Java
<code class="classname">Db.delete()</code> methods on Queue or Recno databases,
and handling the <a href="../programmer_reference/program_errorret.html#program_errorret.DB_KEYEMPTY" class="olink">DB_KEYEMPTY</a> exception specially, should be modified
to check for a return value of <a href="../programmer_reference/program_errorret.html#program_errorret.DB_KEYEMPTY" class="olink">DB_KEYEMPTY</a> instead.
</p>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="upgrade_4_2_client.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="upgrade_4_2_toc.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="upgrade_4_2_priority.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">DB_CLIENT </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> DB-&gt;set_cache_priority</td>
</tr>
</table>
</div>
</body>
</html>