| Bug #32253 | ODBC driver returns no info for SQLGetInfo SQL_UNION | ||
|---|---|---|---|
| Submitted: | 10 Nov 2007 2:02 | Modified: | 15 Nov 2007 6:14 |
| Reporter: | Farid Zidan (Candidate Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S2 (Serious) |
| Version: | 3.51.21 | OS: | Windows (XP SP2) |
| Assigned to: | Jim Winstead | CPU Architecture: | Any |
[12 Nov 2007 23:44]
Jim Winstead
This already works correctly in the 5.1 alpha, but should get fixed in 3.51, too.
[13 Nov 2007 0:16]
Jim Winstead
Report UNION as supported, it has been since MySQL 4.0
Attachment: bug32253.diff (text/plain), 1.11 KiB.
[13 Nov 2007 17:05]
Jim Winstead
The fix for this bug has been committed, and will be in 3.51.22.
[15 Nov 2007 6:14]
MC Brown
A note has been added to the 3.51.22 changelog: When accessing information about supported operations, the driver would return incorrect information about the support for UNION.

Description: ODBC connector says that server 5.0.45 does not support unions. m_nSQLUnion = 0; SQLRETURN rc = SQLGetInfo( m_hdbc, SQL_UNION, &m_nSQLUnion, NULL, NULL ); ASSERT( m_nSQLUnion != 0 ); // fails How to repeat: Connect to MySQL using ODBC connector 3.51.21 and execute the above code fragment where m_hdbc is the established database connection