mirror of
https://github.com/MariaDB/server.git
synced 2025-01-24 07:44:22 +01:00
38 lines
2.4 KiB
HTML
38 lines
2.4 KiB
HTML
<!--$Id: byteorder.so,v 10.16 2000/03/18 21:43:08 bostic Exp $-->
|
|
<!--Copyright 1997, 1998, 1999, 2000 by Sleepycat Software, Inc.-->
|
|
<!--All rights reserved.-->
|
|
<html>
|
|
<head>
|
|
<title>Berkeley DB Reference Guide: Selecting a byte order</title>
|
|
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
|
|
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
|
|
</head>
|
|
<body bgcolor=white>
|
|
<a name="2"><!--meow--></a>
|
|
<table><tr valign=top>
|
|
<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Access Methods</dl></h3></td>
|
|
<td width="1%"><a href="../../ref/am_conf/cachesize.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/am_conf/dup.html"><img src="../../images/next.gif" alt="Next"></a>
|
|
</td></tr></table>
|
|
<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 by
|
|
calling the <a href="../../api_c/db_set_lorder.html">DB->set_lorder</a> function. 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 or from the host format, and 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. Key/data pairs written on a
|
|
little-endian format architecture will be returned to the application
|
|
exactly as they were written when retrieved on a big-endian format
|
|
architecture.</b>
|
|
<table><tr><td><br></td><td width="1%"><a href="../../ref/am_conf/cachesize.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../ref/toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/am_conf/dup.html"><img src="../../images/next.gif" alt="Next"></a>
|
|
</td></tr></table>
|
|
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>
|
|
</body>
|
|
</html>
|