File: byteorder.html

package info (click to toggle)
db 2%3A2.4.14-2.7.7.1.c
  • links: PTS
  • area: main
  • in suites: potato
  • size: 12,716 kB
  • ctags: 9,382
  • sloc: ansic: 35,556; tcl: 8,564; cpp: 4,890; sh: 2,075; makefile: 1,723; java: 1,632; sed: 419; awk: 153; asm: 41
file content (41 lines) | stat: -rw-r--r-- 1,996 bytes parent folder | download | duplicates (6)
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
<! "@(#)byteorder.so	10.5 (Sleepycat) 10/18/98">
<!Copyright 1997, 1998 by Sleepycat Software, Inc.  All rights reserved.>
<html>
<body bgcolor=white>
<head>
<title>Berkeley DB Reference Guide: Access Methods</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btr
ee,hash,hashing,transaction,transactions,locking,logging,access method,access me
thods,java,C,C++">
</head>
<h3>Berkeley DB Reference Guide: Access Methods</h3>
<p>
<h1 align=center>Selecting a byte order</h1>
<p>
The database files created by Berkeley DB can be created in either little or
big-endian formats.
<p>
The byte order used for the underlying database can be specified as part
of the <a href="../../api_c/Db/open.html">db_open</a> call to open the database, specifically by setting
the <a href="../../api_c/DbInfo/info.html#db_lorder">db_lorder</a> element of the DB_INFO structure.  If no
order is selected, the native format of the machine on which the database
is created will be used.
<p>
Berkeley DB databases are architecture independent, and any format database can
be used on a machine with a different native format.  In this case, as
each page that is read into or written from the cache must be converted
to/from the host format, it is possible that databases with non-native
formats will incur a performance penalty for the run-time conversion.
<p>
<b>It is important to note that the Berkeley DB access methods do no data
conversion for application specified data, i.e., key/data pairs written
on a little-endian format architecture will be returned to the application
exactly as they were written, on a big-endian format architecture.</b>
<p>
<a href="../../ref/am/cachesize.html"><img src="../../images/prev.gif"></a>
<a href="../../ref/toc.html"><img src="../../images/toc.gif"></a>
<a href="../../ref/am/compare.html"><img src="../../images/next.gif"></a>
</tt>
</body>
</html>