Many problem with the MariaDB ODBC Driver

Connection crash:
This driver cannot be tested with the Microsoft ODBC test programme ODBCTE32.EXE.
Trying to connect crashes the program.

ODBC V2 compliance:
Some SQLGetInfo info types are not supported:

• SQL_ODBC_API_CONFORMANCE
• SQL_ODBC_SQL_CONFORMANCE

These types are deprecated for ODBC V3 but it is recommended to implement them to be complying with ODBC V2 applications.

Not zero terminated result string:
When using the function SQLColumns the type name is returned as a not zero terminated string.
Of course these functions do not guaranty that result strings are zero terminated but this was the case for almost all drivers including the MySQL ODBC Driver. Besides, this driver returns zero terminated strings for all items except the type name. Not friendly for application writers.

Catalog functions ignore the passed schema parameter:
When calling functions SQLColumns, if a database (schema) is defined in the data source or the connection string, it is used whatever schema name is passed as the function schema argument.

This is also true for SQLTables but in addition, if no default database is defined, the function always returns zero lines.

Misplaced information:
In the result set returned by catalog functions, the schema name is returned in the catalog name column.