Bug #27591 SQLProcedureColumns ]Driver doesn't support this yet
Submitted: 2 Apr 2007 17:20 Modified: 20 May 2007 8:30
Reporter: Farid Zidan (Candidate Quality Contributor)
Status: Closed
Category:Connector/ODBC Severity:S3 (Non-critical)
Version:3.51.14 OS:Microsoft Windows (Windows XP)
Assigned to: Jim Winstead Target Version:

[2 Apr 2007 17:20] Farid Zidan 
Description:
Driver returns SQL_TRUE for SQL_API_SQLPROCEDURECOLUMNS for SQLGetFunctions

    SQLUSMALLINT nSupported = SQL_FALSE;
    SQLRETURN rc = SQLGetFunctions( m_hdbc, nFunctionID, &nSupported );

indicating that is supports SQLProcedureColumns but you you call this api you get an error
saying that driver does not support this yet
SQLProcedureColumns ]Driver doesn't support this yet

How to repeat:
1 Call SQLGetFunctions with SQLPROCEDURECOLUMNS 
2 you get SQL_TRUE indicating driver supports calling SQLProcedureColumns
3 call SQLProcedureColumns, you get an error saying driver does not support this yet

Suggested fix:
Return SQL_FALSE for SQLGetFunctions with SQLPROCEDURECOLUMNS
[2 Apr 2007 20:19] Jim Winstead 
Yes, we shouldn't claim to support SQLProcedureColumns(). It's unlikely we'll support it
in 3.51 due to the difficulty of getting this information from the server. It will
probably be added to 5.0 or a later release.
[3 Apr 2007 1:02] Jim Winstead 
Patch to fix report of whether SQLProcedureColumns is supported

Attachment: bug27591.patch (application/octet-stream, text), 4.99 KiB.
[3 May 2007 21:58] Jim Winstead 
The fix was committed to the source repository, and will be in the next release
(3.51.15).

Thanks for the bug report.
[20 May 2007 8:30] MC Brown 
A note has been added to the 3.51.15 changelog.
[13 Mar 2008 22:46] Jim Winstead 
This behavior is changing again in 3.51.24 because it causes problems for ADO
applications. See Bug #33298.

SQLProcedureColumns() now returns an empty result set and SQL_SUCCESS_WITH_INFO, with an
explanation of why there is no data.