odbx_init (3)

\*(T<#include <opendbx/api.h>\*(T>

\*(T<int odbx_init\*(T> \kx \*(T<(odbx_t** handle, const char* backend, const char* host, const char* port);\*(T>

\*(T<odbx_init\*(T>() allocates and initializes an opaque object required for all further operations within the OpenDBX library which is used to identify the connection and to maintain per connection information. Depending on the backend it can open a connection to the database server but often this is done not until performing authentication through \*(T<odbx_bind\*(T>().

The pointer of the newly allocated connection object is stored in \*(T<handle\*(T> if \*(T<odbx_init\*(T>() completes successfully. Otherwise, the value of the \*(T<handle\*(T> variable will be undefined and must not be used as input for other functions of the library. The returned connection object must be freed by \*(T<odbx_finish\*(T>() to avoid memory leaks if it will be no longer used by the application.

The OpenDBX library provides access to several different database implementations through a single interface and therefore has to know which one of the available backend modules it should use for the operations. The \*(T<backend\*(T> parameter will be used to perform the lookup of the requested module. It has to be a zero-terminated ASCII string with all characters in in lower case. Currently, these backend modules are available:

•

firebird (Firebird/Interbase)

•

mssql (MS SQL Server via FreeTDS)

•

mysql (MySQL)

•

oracle (Oracle 8i/9i/10g)

•

pgsql (PostgreSQL)

•

sqlite (SQLite v2)

•

sqlite3 (SQLite v3)

•

sybase (Sybase ASE)

Connecting to a database server requires at least an identifier to know where the database is located. There are several kinds of identifiers like host names, IP addresses, named pipes, etc. which could be used. One of them can be provided via the \*(T<host\*(T> parameter and it is up to the native database library what it will accept. Most native libraries accept at least host names and IP addresses and also use the provided \*(T<port\*(T> in this case. The available methods for \*(T<host\*(T> are:

host name string

supported by Firebird/Interbase, MySQL, Oracle and PostgreSQL backends

IP address string

supported by Firebird/Interbase, MySQL, Oracle and PostgreSQL backends

absolute path to Unix domain socket

currently supported by the PostgreSQL backend only

(relative) directory path with trailing slash/backslash

required by SQLite and SQLite3 backends

section name in configuration file

required by MS SQL Server and Sybase ASE backends

Depending on the native database library, it's also possible to use database specific default values for the \*(T<host\*(T> and \*(T<port\*(T> parameters by supplying empty, zero-terminated strings or a NULL value.

\*(T<odbx_init\*(T>() returns \*(T<ODBX_ERR_SUCCESS\*(T>, or an error code whose value is less than zero if one of the operations couldn't be completed successfully. Possible error codes are listed in the error section and they can be feed to \*(T<odbx_error\*(T>() and \*(T<odbx_error_type\*(T>() to get further details.

-\*(T<ODBX_ERR_BACKEND\*(T>

The backend module returned an error because it couldn't setup the necessary structures

-\*(T<ODBX_ERR_PARAM\*(T>

\*(T<handle\*(T> is NULL and the allocated connection object can't be stored

-\*(T<ODBX_ERR_NOMEM\*(T>

Allocating new memory for the connection object failed

-\*(T<ODBX_ERR_SIZE\*(T>

The length of a string exceeded the available buffer size

-\*(T<ODBX_ERR_NOTEXIST\*(T>

A backend module with this name wasn't found. Either the module isn't installed, the given name was wrong or not in the correct character case

-\*(T<ODBX_ERR_NOOP\*(T>

The backend module doesn't provide the required function

\*(T<odbx_bind\*(T>(), \*(T<odbx_capabilities\*(T>(), \*(T<odbx_error\*(T>(), \*(T<odbx_finish\*(T>(), \*(T<odbx_get_option\*(T>(), \*(T<odbx_set_option\*(T>()