CONNECT (DRIVER-NAME &REST PARAMS &KEY DATABASE-NAME &ALLOW-OTHER-KEYS)
Open a connection to the database which corresponds to `driver-name`.
Find a driver class named as `driver-name`. `driver-name` is a string designer. Driver should be named like '<DBD-SOMETHING>' for a database 'something'.
Return a list of direct subclasses for `<dbi-driver>`.
WITH-TRANSACTION (CONN &BODY BODY)
Start a transaction and commit at the end of this block. If the evaluation `body` is interrupted, the transaction is rolled back automatically.
WITH-CONNECTION ((CONN-SYM &REST REST) &BODY BODY)
DO-SQL (CONN SQL &REST PARAMS)
EXECUTE (QUERY &REST PARAMS)
PREPARE (CONN SQL &KEY (QUERY-CLASS '<DBI-QUERY>))
Exception for errors due to problems with the processed data such as division for zero, numeric value out of range, etc.
Exception for errors related to the database.
Base class of all other error exceptions. Use this to catch all DBI errors.
Exception raised when the relational integrity of the database is affected, e.g. a foreign key check fails.
Exception for errors related to the DBI interface rather than the database itself.
Exception raised when the database encounters an internal error, e.g. the cursor is not valid anymore, the transaction is out of sync.
Exception raised if e.g. commit() is called for a database which do not support transactions.
Exception for errors related to the database's operation which are not necessarily under the control of the programmer. This includes such things as unexpected disconnect, datasource name not found, transaction could not be processed, a memory allocation error occured during processing, etc.
Exception raised for programming errors, e.g. table not found or already exists, syntax error in SQL statement, wrong number of parameters specified, etc.
Exception raised if the DBD driver has not specified a mandatory method.
For important warnings like data truncation, etc.