Library Version 12.1.6.0

Android Configuration Options
Prev | Chapter 4. Building Berkeley DB for Android | Next

## Android Configuration Options

There are several configuration options you can specify in `LOCAL_CFLAGS` located in the `Android.mk` file.

- BDBSQL_CONVERT_SQLITE

  This option enables to convert SQLite database to BDB SQL database format. See Migrating from SQLite to Berkeley DB for more information.

- BDBSQL_SHARE_PRIVATE

  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.

- SQLITE_DEFAULT_CACHE_SIZE

  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 Changing Compile Options.

- SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT

  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 the maximum size for a log file. Default value is 10 MB for Berkeley DB SQL interface.

- SQLITE_HAS_CODEC

  Causes the Berkeley DB SQL interface to be built with encryption support. See SQL Encryption in the Berkeley DB Getting Started with the SQL APIs guide for usage details.

Hard-coded numbers in the build can be adjusted using the following SQLite PRAGMA commands:

- PRAGMA cache_size
- PRAGMA journal_size_limit

You can configure most aspects of your Berkeley DB environment by using the DB_CONFIG file.

Prev | Up | Next
Building the Android JDBC Driver | Home | Chapter 5. Building Berkeley DB for Windows