c290c54d73
* Documentation in .CHM and .HLP format has been removed from the distribution. * For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied. * Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. * The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. * In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. * SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound. * Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. * When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. * After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”. * In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. * When used after a call to SQLTables(), SQLRowCount() did not return the correct value.
9 lines
336 B
Text
9 lines
336 B
Text
@comment $NetBSD: PLIST,v 1.8 2011/08/19 07:59:58 adam Exp $
|
|
bin/myodbc-installer
|
|
${PLIST.gui}lib/libmyodbc3S.la
|
|
lib/libmyodbc5.la
|
|
share/doc/mysql-connector-odbc/ChangeLog
|
|
share/doc/mysql-connector-odbc/INSTALL
|
|
share/doc/mysql-connector-odbc/LICENSE.gpl
|
|
share/doc/mysql-connector-odbc/README
|
|
share/doc/mysql-connector-odbc/README.debug
|