2
<!--Copyright 1997-2002 by Sleepycat Software, Inc.-->
3
<!--All rights reserved.-->
4
<!--See the file LICENSE for redistribution information.-->
7
<title>Berkeley DB Reference Guide: Release 2.0: system integration</title>
8
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
9
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
12
<table width="100%"><tr valign=top>
13
<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></h3></td>
14
<td align=right><a href="../../ref/upgrade.2.0/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/upgrade.2.0/convert.html"><img src="../../images/next.gif" alt="Next"></a>
17
<h1 align=center>Release 2.0: system integration</h1>
19
<p><li>It is possible to maintain both the Berkeley DB 1.85 and Berkeley DB version 2
20
libraries on your system. However, the <b>db.h</b> include file that
21
was distributed with Berkeley DB 1.85 is not compatible with the <b>db.h</b>
22
file distributed with Berkeley DB version 2, so you will have to install them
23
in different locations. In addition, both the Berkeley DB 1.85 and Berkeley DB
24
version 2 libraries are named <b>libdb.a</b>.
25
<p>As the Berkeley DB 1.85 library did not have an installation target in the
26
Makefile, there's no way to know exactly where it was installed on the
27
system. In addition, many vendors included it in the C library instead
28
of as a separate library, and so it may actually be part of libc and the
29
<b>db.h</b> include file may be installed in <b>/usr/include</b>.
30
<p>For these reasons, the simplest way to maintain both libraries is to
31
install Berkeley DB version 2 in a completely separate area of your system.
32
The Berkeley DB version 2 installation process allows you to install into a
33
standalone directory hierarchy on your system. See the
34
<a href="../../ref/build_unix/intro.html">Building for UNIX systems</a>
35
documentation for more information and instructions on how to install the
36
Berkeley DB version 2 library, include files and documentation into specific
38
<p><li>Alternatively, you can replace Berkeley DB 1.85 on your system with Berkeley DB
39
version 2. In this case, you'll probably want to install Berkeley DB version
40
2 in the normal place on your system, wherever that may be, and delete
41
the Berkeley DB 1.85 include files, manual pages and libraries.
42
<p>To replace 1.85 with version 2, you must either convert your 1.85
43
applications to use the version 2 API or build the Berkeley DB version 2 library
44
to include Berkeley DB 1.85 interface compatibility code. Whether converting
45
your applications to use the version 2 interface or using the version 1.85
46
compatibility API, you will need to recompile or relink your 1.85
47
applications, and you must convert any persistent application databases
48
to the Berkeley DB version 2 database formats.
49
<p>If you want to recompile your Berkeley DB 1.85 applications, you will have to
50
change them to include the file <b>db_185.h</b> instead of
51
<b>db.h</b>. (The <b>db_185.h</b> file is automatically installed
52
during the Berkeley DB version 2 installation process.) You can then recompile
53
the applications, linking them against the Berkeley DB version 2 library.
54
<p>For more information on compiling the Berkeley DB 1.85 compatibility code into
55
the Berkeley DB version 2 library, see <a href="../../ref/build_unix/intro.html">Building for UNIX platforms</a>.
56
<p>For more information on converting databases from the Berkeley DB 1.85 formats
57
to the Berkeley DB version 2 formats, see the <a href="../../utility/db_dump.html">db_dump185</a> and
58
<a href="../../utility/db_load.html">db_load</a> documentation.
59
<p><li>Finally, although we certainly do not recommend it, it is possible to
60
load both Berkeley DB 1.85 and Berkeley DB version 2 into the same library.
61
Similarly, it is possible to use both Berkeley DB 1.85 and Berkeley DB version 2
62
within a single application, although it is not possible to use them from
64
<p>The name space in Berkeley DB version 2 has been changed from that of previous
65
Berkeley DB versions, notably version 1.85, for portability and consistency
66
reasons. The only name collisions in the two libraries are the names used
67
by the historic <a href="../../api_c/dbm.html">dbm</a>, <a href="../../api_c/dbm.html">ndbm</a> and <a href="../../api_c/hsearch.html">hsearch</a> interfaces,
68
and the Berkeley DB 1.85 compatibility interfaces in the Berkeley DB version 2
70
<p>If you are loading both Berkeley DB 1.85 and Berkeley DB version 2 into a single
71
library, remove the historic interfaces from one of the two library
72
builds, and configure the Berkeley DB version 2 build to not include the Berkeley DB
73
1.85 compatibility API, otherwise you could have collisions and undefined
74
behavior. This can be done by editing the library Makefiles and
75
reconfiguring and rebuilding the Berkeley DB version 2 library. Obviously, if
76
you use the historic interfaces, you will get the version in the library
77
from which you did not remove them. Similarly, you will not be able to
78
access Berkeley DB version 2 files using the Berkeley DB 1.85 compatibility interface,
79
since you have removed that from the library as well.
81
<table width="100%"><tr><td><br></td><td align=right><a href="../../ref/upgrade.2.0/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/upgrade.2.0/convert.html"><img src="../../images/next.gif" alt="Next"></a>
83
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>