Databases

    +

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

    Initializer

    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
    • Kotlin

    • Java

    // Initialize the Couchbase Lite system
    CouchbaseLite.init(context)
    // Initialize the Couchbase Lite system
    CouchbaseLite.init(context);

    Create or Open Database

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

    Things to watch for include:

    • 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
    • Kotlin

    • Java

    val database = Database(
        "my-db",
        DatabaseConfigurationFactory.create(
            context.filesDir.absolutePath
        )
    ) (1)
    final DatabaseConfiguration config = new DatabaseConfiguration();
    config.setDirectory(context.getFilesDir().getAbsolutePath()); (1)
    
    Database database = new Database("my-database", config);

    Close Database

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

    Closing a database is simple, just use Database.close() — see: Example 3. This also closes [1] active replications, listeners and-or live queries connected to the database.

    Closing a database soon after starting a replication involving it can cause an exception as the asynchronous replicator (start) may not yet be connected.
    Safely Closing a Database pre 2.8
    Before closing, check that any attached listeners (query/replication/change) indicate they are at least at connected status before closing — see for example: Monitor Status.
    Example 3. Close a Database
    • Kotlin

    • Java

    database.close()
    database.close();

    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.

    Enabling

    To enable encryption, use DatabaseConfiguration.setEncryptionKey() to set the encryption key of your choice. Provide this encryption key every time the database is opened — see Example 4.

    Example 4. Configure Database Encryption
    • Kotlin

    • Java

    val db = Database(
        "my-db",
        DatabaseConfigurationFactory.create(
            encryptionKey = EncryptionKey("PASSWORD")
        )
    )
    DatabaseConfiguration config = new DatabaseConfiguration();
    config.setEncryptionKey(new EncryptionKey("PASSWORD"));
    Database database = new Database("mydb", config);

    Persisting

    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.

    Opening

    An encrypted database can only be opened with the same language SDK that was used to encrypt it in the first place. So a database encrypted using the Android SDK, and then exported, is readable only by the Android SDK.

    Changing

    To change an existing encryption key, open the database using its existing encryption-key and use Database.changeEncryptionKey() to set the required new encryption-key value.

    Removing

    To remove encryption, open the database using its existing encryption-key and use Database.changeEncryptionKey() with a null value as the encryption key.

    Upgrading

    To upgrade an encrypted database see: Upgrade 1.x databases

    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.

    List
    $ 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 5. Pull using adb command
    $ adb root
    $ adb pull /data/data/{APPLICATION_ID}/files/{DATABASE_NAME}.cblite2 .

    Database Maintenance

    From time to time it may be necessary to perform certain maintenance activities on your database, for example to compact the database file, removing unused documents and blobs no longer referenced by any documents.

    Couchbase Lite’s API provides the Database.performMaintenance() method. The available maintenance operations, including compact are as shown in the enum MaintenanceType to accomplish this.

    This is a resource intensive operation and is not performed automatically. It should be run on-demand using the API. If in doubt, consult Couchbase support.

    Command Line Tool

    cblite is a command-line tool for inspecting and querying Couchbase Lite 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.

    Troubleshooting

    You should use 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 6.

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

    Example 6. Increase Level of Database Log Messages
    • Kotlin

    • Java

    Database.log.console.domains = EnumSet.of(LogDomain.DATABASE) (1)
    Database.log.getConsole().setDomain(LogDomain.DATABASE);

    1. Commencing with Release 2.8