Home
Extending HCL OneDB™Beyond standard relational database objects, HCL OneDB™ can be extended to handle specialized data types, access methods, routines, and other objects. HCL OneDB™ includes many built-in extensions that are fully integrated in the database server. HCL OneDB™ also provides DataBlade® modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for HCL OneDB™.
Creating extensionsYou can create user-defined data types, routines, access methods, and other database objects to suit your needs. You can use application programming interfaces to write user-defined routines and applications that access data in HCL OneDB™ databases.
DataBlade® API Function ReferenceThe HCL OneDB™ DataBlade® API Function Reference describes the DataBlade® API functions and the subset of functions that the DataBlade® API supports.
Function descriptionsThis section gives comprehensive reference information about the functions that are valid within DataBlade® API modules. It lists the function descriptions in alphabetical order, with syntax, usage information, and return values for the functions.
The mi_dbdrop() functionThe mi_dbdrop() function drops a database from the given connection.

The mi_dbdrop() function

The mi_dbdrop() function drops a database from the given connection.

Syntax

mi_integer mi_dbdrop(conn, db_info)
   MI_CONNECTION *conn;
   const MI_DATABASE_INFO *db_info;

conn: A pointer to a connection descriptor established by a previous call to mi_open(), mi_server_connect(), or mi_server_reconnect().
db_info: A pointer to a database-information descriptor that identifies the database to drop.


Valid in client LIBMI application?	Valid in user-defined routine?
Yes	No

Usage

The mi_dbdrop() function is equivalent to the SQL DROP DATABASE statement. A field in the database-information structure that dbinfo references contains the database name.

For additional information about the MI_DATABASE_INFO structure, see the description of the mi_get_database_info() function.

Return values

MI_OK: The function was successful; the database was dropped.
MI_ERROR: The function was not successful. An exception was raised, and the database was not created.