From: Fred Drake <fdrake@acm.org>
Date: Tue, 10 Aug 2004 19:22:48 +0000 (+0000)
Subject: clarify the behavior of the .first() and .last() methods for empty
X-Git-Tag: v2.4a3~289
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ba100c98adf59baa695eb30e561e16ebe0fae4d6;p=python

clarify the behavior of the .first() and .last() methods for empty
databases

this should be backported to the release23-maint branch
---

diff --git a/Doc/lib/libbsddb.tex b/Doc/lib/libbsddb.tex
index bb1e6b0f5b..a25d39b98b 100644
--- a/Doc/lib/libbsddb.tex
+++ b/Doc/lib/libbsddb.tex
@@ -135,6 +135,7 @@ database.
 \begin{methoddesc}{first}{}
 Set the cursor to the first item in the DB file and return it.  The order of 
 keys in the file is unspecified, except in the case of B-Tree databases.
+This method raises \exception{bsddb.error} if the database is empty.
 \end{methoddesc}
 
 \begin{methoddesc}{next}{}
@@ -153,6 +154,7 @@ with \function{hashopen()}).
 Set the cursor to the last item in the DB file and return it.  The
 order of keys in the file is unspecified.  This is not supported on
 hashtable databases (those opened with \function{hashopen()}).
+This method raises \exception{bsddb.error} if the database is empty.
 \end{methoddesc}
 
 \begin{methoddesc}{sync}{}