UnQLite C/C++ API Reference - Database Engine Handle.

const char **pzPtr,

int *pLen;

When something goes wrong during compilation of the target Jx9 script due to an erroneous Jx9 code, the compiler error log is redirected to an internal buffer. This option can be used to point to that buffer. The first argument is a pointer address to a const char *.

The second argument is an optional pointer to an integer. When set (i.e. not null), the integer value will hold the length of the error log in bytes.

Example:

const char *zErrLog;

int nLen;

/* Extract the compiler error log */

unqlite_config(

   pDb,

   UNQLITE_CONFIG_JX9_ERR_LOG,

   &zErrLog, /* First arg */

   &nLen     /* Second arg */

);

if( nLen > 0 ){

   puts(zErrLog); /* Output*/

int nMaxPage;

Maximum raw pages to cache in memory. This is a simple hint, UnQLite is not forced to honor it.

const char **pzPtr,

int *pLen;

The database error log is stored in an internal buffer. When something goes wrong during a commit, rollback, store, append operation, a human-readable error message is generated to help clients diagnostic the problem. This option can be used to point to that buffer.

The first argument is a pointer address to a const char *.

The second argument is an optional pointer to an integer. When set (i.e. not null), the integer value will hold the length of the error log in bytes.

Example:

if( rc != UNQLITE_OK ){

  const char *zBuf;

  int iLen;

  /* Something goes wrong, extract database error log */

 unqlite_config(

  pDb,

  UNQLITE_CONFIG_ERR_LOG,

  &zBuf,

  &iLen

);

  if( iLen > 0 ){

    puts(zBuf);

  }

}

const char *zKvName

Switch to another Key/Value storage engine. This option is reserved for future usage.

Normally, If unqlite_close() is invoked while a transaction is open, the transaction is automatically committed. But, if this option is set, then the transaction is automatically rolled back and you should call unqlite_commit() manually to commit all database changes.

const char **pzName;

Extract the name of the underlying Key/Value storage engine (i.e. Hash, Mem, R+Tree, LSM, etc.).

A pointer to a unQLite Database Handle.

An integer configuration option that determines what property of the database is to be configured.