Databases — Data Model


    Description — Working with Couchbase Lite on Android databases
    Related Content — Blobs | Documents | Indexing


    Your first step in using the API must be to call its initializer. An exception is raised if any other API method is invoked before the initializer.

    Example 1. Initializer code
    // Initialize the Couchbase Lite system

    Create or Open Database

    You can create a new database and-or open and existing database, using the Database class. Just pass in a database name and optionally a DatabaseConfiguration — see Example 2.

    Things to watch for include:

    • Opening/Creating a database is an asynchronous process

    • If the named database does not exist in the specified, or default, location then a new one is created

    • The database is created in a default location unless you specify a directory for it — see: DatabaseConfiguration and DatabaseConfiguration.setDirectory()

      Best Practice is to always specify the path to the database explicitly.

      Typically, the default location for Android is the application sandbox.

    Example 2. Open or create a database
    final DatabaseConfiguration config = new DatabaseConfiguration();
    config.setDirectory(context.getFilesDir().getAbsolutePath()); (1)
    Database database = new Database("my-database", config);
    1 Here we are specifying the database directory path.

    Close Database

    You are advised to incorporate the closing of all open databases into your application workflow.

    Closing a database is a simple, just use Database.close() — see: Example 3.
    However, there are a number of things to be aware of:

    • Closing a database is a synchronous operation, it is effective immediately

    • You cannot close a database that is not open.
      Remember that opening (or creating) a database is asynchronous. So issuing a close immediately after initiating an open/create, may result in an error if that process has not completed.

    • Closing a database [1] also closes any active replications, listeners and-or live queries attached to the database.
      Closing a database immediately after kicking-off a replication could cause the sync to generate an exception.
      For example:
      IllegalStateException: Attempt to perform an operation on a closed database

    Example 3. Close a Database

    Database Encryption

    This is an Enterprise Edition feature.

    Couchbase Lite on Android includes the ability to encrypt Couchbase Lite databases. This allows mobile applications to secure the data at rest, when it is being stored on the device. The algorithm used to encrypt the database is 256-bit AES.

    To enable encryption, you must set the DatabaseConfiguration.encryptionKey property to the encryption key of your choice. Provide this encryption key every time the database is opened.

    DatabaseConfiguration config = new DatabaseConfiguration();
    config.setEncryptionKey(new EncryptionKey("PASSWORD"));
    Database database = new Database("mydb", config);

    Couchbase Lite does not persist the key. It is the application’s responsibility to manage the key and store it in a platform specific secure store such as Apple’s Keychain or Android’s Keystore.

    An encrypted database can only be opened with the same language SDK that was used to encrypt it in the first place (Swift, C#, Java, Java (Android) or Objective-C). For example, if a database is encrypted with the Swift SDK and then exported, it will only be readable with the Swift SDK.

    Upgrading from 1.x when Encryption is Enabled

    If you’re migrating an application from Couchbase Lite 1.x to 2.x, note that the automatic database upgrade functionality is not supported for encrypted databases. Thus, to upgrade an encrypted 1.x database, you should do the following:

    1. Disable encryption using the Couchbase Lite 1.x framework (see 1.x encryption guide)

    2. Open the database file with encryption enabled using the Couchbase Lite 2.x framework.

    Since it is not possible to package Couchbase Lite 1.x and Couchbase Lite 2.x in the same application this upgrade path would require two successive upgrades. If you are using Sync Gateway to synchronize the database content, it may be preferable to run a pull replication from a new 2.x database with encryption enabled and delete the 1.x local database.

    Finding a Database File

    When the application is running on the Android emulator, you can locate the application’s data folder and access the database file by using the adb CLI tools. For example, to list the different databases on the emulator, you can run the following commands.

    $ adb shell
    $ su
    $ cd /data/data/{APPLICATION_ID}/files
    $ ls

    The adb pull command can be used to pull a specific database to your host machine.

    Example 4. Pull using adb command
    $ adb root
    $ adb pull /data/data/{APPLICATION_ID}/files/{DATABASE_NAME}.cblite2 .

    Command Line Tool

    cblite is a command-line tool for inspecting and querying Couchbase Lite 2.x databases.

    You can download and build it from the couchbaselabs GitHub repository. Note that the cblite tool is not supported by the Couchbase Support Policy.


    You should use Couchbase’s console logs as your first source of diagnostic information. If the information in the default logging level is insufficient you can focus it on database errors and generate more verbose messages — see: Example 5.

    For more on using Couchbase logs — see: Using Logs.

    Example 5. Increase Level of Database Log Messages

    1. Commencing with Release 2.8