<p>There are several configuration options you can specify in <codeclass="literal">LOCAL_CFLAGS</code> located in the <codeclass="literal">Android.mk</code> file. </p>
<divclass="itemizedlist">
<ultype="disc">
<li>
<p>
BDBSQL_CONVERT_SQLITE
</p>
<p>
This option enables to convert SQLite database to BDB SQL database format. See <aclass="xref"href="build_android_intro.html#build_android_migrate"title="Migrating from SQLite to Berkeley DB">Migrating from SQLite to Berkeley DB</a>
for more information.
</p>
</li>
<li>
<p>
BDBSQL_SHARE_PRIVATE
</p>
<p>
This flag is enabled by default and keeps all the region files in
memory instead of the disk.
This flag also implements database-level locking.
</p>
</li>
<li>
<p>
SQLITE_DEFAULT_CACHE_SIZE
</p>
<p>
SQLite provides an in-memory cache which you size according to the maximum number of
database pages that you want to hold in memory at any given time.
See <aclass="xref"href="build_unix_sql.html#config_sql"title="Changing Compile Options">Changing Compile Options</a>.
</p>
</li>
<li>
<p>
SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT
</p>
<p>
For SQLite, this pragma identifies the maximum size that the journal file is allowed
to be. Berkeley DB does not have a journal file, but it writes and uses log files. A new log file is
created when the current log file has reached the defined maximum size.
This flag defines this maximum size for a log file. Default value is 10 MB for Berkeley DB SQL interface.
</p>
</li>
</ul>
</div>
<p>
Hard-coded numbers in the build can be adjusted using the following SQLite PRAGMA commands: </p>
<divclass="itemizedlist">
<ultype="disc">
<li>PRAGMA cache_size</li>
<li>PRAGMA journal_size_limit</li>
</ul>
</div>
<p>
You can configure most aspects of your Berkeley DB environment by using the <ahref="../api_reference/C/configuration_reference.html"class="olink">DB_CONFIG</a> file.
