MySQL offers one of the most complete selection of application programmer interface support. Some of these are in the form of a library (such as the MySQL C API library) while others are in the form of a driver (such as the ODBC driver). For most people/situations - the choice of which interface to use is obvious as it is often dictated by the programming language in use (JDBC for Java for example).

Here are some reasons for considering the ODBC interface. Note; some of these reasons can apply to more than one interface.

• Cross-database
• Cross-platform
• SQL Standard
• C/C++ Programming Language

Cross-database

The ODBC standard was created primarly to provide an application developer with a database vendor neutral way to work with a database. In other words the source code does not have to change just because one decides to switch from (for …

Earlier this week I released the revamped Connector/NET documentation. This is part of the wider Connectors chapter rework, which I’m currently finishing by doing the Connector/J and Connector/MXJ documentation.

Connector/NET provides a full ADO.NET compatible interface to MySQL and is compatible both the Windows .NET and Mono installations.

read more