1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
|
<?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>Chapter 1. Introduction</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="index.html" title="Berkeley DB Upgrade Guide" />
<link rel="prev" href="moreinfo.html" title="For More Information" />
<link rel="next" href="upgrade_process.html" title="Chapter 2. Upgrading from previous versions of Berkeley DB" />
</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">Chapter 1. Introduction</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="moreinfo.html">Prev</a> </td>
<th width="60%" align="center"> </th>
<td width="20%" align="right"> <a accesskey="n" href="upgrade_process.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a id="introduction"></a>Chapter 1. Introduction</h2>
</div>
</div>
</div>
<div class="toc">
<p>
<b>Table of Contents</b>
</p>
<dl>
<dt>
<span class="sect1">
<a href="introduction.html#upgrade_version">Library version information</a>
</span>
</dt>
</dl>
</div>
<p>
This manual describes how to upgrade from historical versions
of Berkeley DB (Berkeley DB 4.7 and older).
For information on upgrading newer releases
of the product (anything newer than DB 4.7), and on
building and installing Berkeley DB on all of the platforms it
officially supports, see the
<a class="ulink" href="http://download.oracle.com/docs/cd/E17076_02/html/installation/index.html" target="_top">
Berkeley DB Installation and Build Guide.
</a>
</p>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="upgrade_version"></a>Library version information</h2>
</div>
</div>
</div>
<p>Each release of the Berkeley DB library has a major version number, a minor
version number, and a patch number.</p>
<p>The major version number changes only when major portions of the Berkeley DB
functionality have been changed. In this case, it may be necessary to
significantly modify applications in order to upgrade them to use the new
version of the library.</p>
<p>The minor version number changes when Berkeley DB interfaces have changed,
and the new release is not entirely backward-compatible with previous
releases. To upgrade applications to the new version, they must be
recompiled and potentially, minor modifications made (for example, the
order of arguments to a function might have changed).</p>
<p>The patch number changes on each release. If only the patch number has
changed in a release, applications do not need to be recompiled, and
they can be upgraded to the new version by installing the new version
of a shared library or by relinking the application to the new version
of a static library.</p>
<p>Internal Berkeley DB interfaces may change at any time and during any release,
without warning. This means that the library must be entirely recompiled
and reinstalled when upgrading to new releases of the library because
there is no guarantee that modules from the current version of the
library will interact correctly with modules from a previous release.</p>
<p>To retrieve the Berkeley DB version information, applications should use the
<a href="../api_reference/C/envversion.html" class="olink">DB_ENV->version()</a> function. In addition to the previous
information, the <a href="../api_reference/C/envversion.html" class="olink">DB_ENV->version()</a> function returns a string
encapsulating the version information, suitable for display to a user.</p>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="moreinfo.html">Prev</a> </td>
<td width="20%" align="center"> </td>
<td width="40%" align="right"> <a accesskey="n" href="upgrade_process.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">For More Information </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Chapter 2.
Upgrading from previous versions of Berkeley DB
</td>
</tr>
</table>
</div>
</body>
</html>
|
