1<!--$Id: cksum.so,v 1.4 2004/09/28 14:13:08 bostic Exp $--> 2<!--Copyright (c) 1997,2008 Oracle. All rights reserved.--> 3<!--See the file LICENSE for redistribution information.--> 4<html> 5<head> 6<title>Berkeley DB Reference Guide: Release 4.2: DB_CHKSUM_SHA1</title> 7<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> 8<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> 9</head> 10<body bgcolor=white> 11<table width="100%"><tr valign=top> 12<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></b></td> 13<td align=right><a href="../upgrade.4.2/queue.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.2/client.html"><img src="../../images/next.gif" alt="Next"></a> 14</td></tr></table> 15<p align=center><b>Release 4.2: DB_CHKSUM_SHA1</b></p> 16<p>The flag to enable checksumming of Berkeley DB databases pages was renamed 17from DB_CHKSUM_SHA1 to <a href="../../api_c/db_set_flags.html#DB_CHKSUM">DB_CHKSUM</a>, as Berkeley DB uses an internal 18function to generate hash values for unencrypted database pages, not 19the SHA1 Secure Hash Algorithm. Berkeley DB continues to use the SHA1 Secure 20Hash Algorithm to generate hashes for encrypted database pages. 21Applications using the DB_CHKSUM_SHA1 flag should change that use to 22<a href="../../api_c/db_set_flags.html#DB_CHKSUM">DB_CHKSUM</a>; no other change is required.</p> 23<table width="100%"><tr><td><br></td><td align=right><a href="../upgrade.4.2/queue.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.2/client.html"><img src="../../images/next.gif" alt="Next"></a> 24</td></tr></table> 25<p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> 26</body> 27</html> 28
