Query implemented capabilities
\*(T<#include <opendbx/api.h>\*(T>
\*(T<int odbx_capabilities\*(T> \kx \*(T<(odbx_t* handle, unsigned int cap);\*(T>
\*(T<odbx_capabilities\*(T>() ask the backend associated to the connection object returned by \*(T<odbx_init\*(T>() if a certain capability set is implemented by this backend. All backends have to implement the basic capability set and may implement further predefined functional sets if they are supported by the native database client library. This function can be called at any stage after \*(T<odbx_init\*(T>() returned successfully.
The first parameter \*(T<handle\*(T> has to be the connection object created and returned by \*(T<odbx_init\*(T>(). It becomes invalid as soon as it was supplied to \*(T<odbx_finish\*(T>() and \*(T<odbx_capabilities\*(T>() will return an error in this case.
\*(T<cap\*(T> is the number of the capability set as defined by macro constants in odbx.h. Valid constant names which can be supplied as second parameter to \*(T<odbx_capabilities\*(T>() are listed below:
-\*(T<ODBX_CAP_BASIC\*(T>
The core function set which have to be implemented by all backends. It consists of all functions necessary to connect to, send textual queries to and process simple results returned from the database server as well as error handling functions.
\*(T<odbx_capabilities\*(T>() returns \*(T<ODBX_ENABLE\*(T> if the requested capability is supported, \*(T<ODBX_DISABLE\*(T> if the capability is not supported or an error code whose value is less than zero if one of the supplied parameters is invalid. 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_PARAM\*(T>
\*(T<handle\*(T> is NULL or the supplied connection object is invalid
\*(T<odbx_error\*(T>(), \*(T<odbx_error_type\*(T>(), \*(T<odbx_init\*(T>()