1<?xml version="1.0" encoding="UTF-8" standalone="no"?> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3<html xmlns="http://www.w3.org/1999/xhtml"> 4 <head> 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 6 <title>Release 3.2: DB_ENV->set_tx_recover</title> 7 <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> 8 <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> 9 <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" /> 10 <link rel="up" href="upgrade_3_2_toc.html" title="Chapter��35.��Upgrading Berkeley DB 3.1 applications to Berkeley DB 3.2" /> 11 <link rel="prev" href="upgrade_3_2_incomplete.html" title="Release 3.2: DB_INCOMPLETE" /> 12 <link rel="next" href="upgrade_3_2_mutexlock.html" title="Release 3.2: DB_ENV->set_mutexlocks" /> 13 </head> 14 <body> 15 <div class="navheader"> 16 <table width="100%" summary="Navigation header"> 17 <tr> 18 <th colspan="3" align="center">Release 3.2: DB_ENV->set_tx_recover</th> 19 </tr> 20 <tr> 21 <td width="20%" align="left"><a accesskey="p" href="upgrade_3_2_incomplete.html">Prev</a>��</td> 22 <th width="60%" align="center">Chapter��35.��Upgrading Berkeley DB 3.1 applications to Berkeley DB 3.2</th> 23 <td width="20%" align="right">��<a accesskey="n" href="upgrade_3_2_mutexlock.html">Next</a></td> 24 </tr> 25 </table> 26 <hr /> 27 </div> 28 <div class="sect1" lang="en" xml:lang="en"> 29 <div class="titlepage"> 30 <div> 31 <div> 32 <h2 class="title" style="clear: both"><a id="upgrade_3_2_tx_recover"></a>Release 3.2: DB_ENV->set_tx_recover</h2> 33 </div> 34 </div> 35 </div> 36 <p>The <span class="bold"><strong>info</strong></span> parameter of the function passed to 37DB_ENV->set_tx_recover is no longer needed. If your application 38calls DB_ENV->set_tx_recover, find the callback function referred 39to by that call and remove the <span class="bold"><strong>info</strong></span> parameter.</p> 40 <p>In addition, the called function no longer needs to handle Berkeley DB log 41records, Berkeley DB will handle them internally as well as call the 42application-specified function. Any handling of Berkeley DB log records in the 43application's callback function may be removed.</p> 44 <p>In addition, the callback function will no longer be called with the 45<a href="../api_reference/C/envset_app_dispatch.html#set_app_dispatch_DB_TXN_FORWARD_ROLL" class="olink">DB_TXN_FORWARD_ROLL</a> flag specified unless the transaction 46enclosing the operation successfully committed.</p> 47 </div> 48 <div class="navfooter"> 49 <hr /> 50 <table width="100%" summary="Navigation footer"> 51 <tr> 52 <td width="40%" align="left"><a accesskey="p" href="upgrade_3_2_incomplete.html">Prev</a>��</td> 53 <td width="20%" align="center"> 54 <a accesskey="u" href="upgrade_3_2_toc.html">Up</a> 55 </td> 56 <td width="40%" align="right">��<a accesskey="n" href="upgrade_3_2_mutexlock.html">Next</a></td> 57 </tr> 58 <tr> 59 <td width="40%" align="left" valign="top">Release 3.2: DB_INCOMPLETE��</td> 60 <td width="20%" align="center"> 61 <a accesskey="h" href="index.html">Home</a> 62 </td> 63 <td width="40%" align="right" valign="top">��Release 3.2: DB_ENV->set_mutexlocks</td> 64 </tr> 65 </table> 66 </div> 67 </body> 68</html> 69