-
This looks like it was fixed in 3.52.6.
2007-11-30 20:21:39 UTC in iODBC
-
The Unicode to ANSI conversions probably have the same problem, but I've not tested that.
2007-08-25 01:06:57 UTC in iODBC
-
When "" is passed to the non-W version of functions and a Unicode driver is in use, the driver manager passes NULL to the underlying driver.
One example of a place this would cause trouble is the catalog functions, where NULL is sometimes not acceptable when "" is, such as for the catalog or schema when SQL_ATTR_METADATA_ID is SQL_TRUE, and the user wants to get objects that do not belong to...
2007-08-25 01:06:15 UTC in iODBC
-
Calls to SQLDescribeCol() with a Unicode driver fail if NULL is passed in for the column name buffer (or probably if 0 is given as the length of the buffer).
It's trying to allocate a new buffer (to do the SQLWCHAR -> SQLCHAR conversion), but returning an error when the newly-allocated buffer is NULL because it ends up basically doing a malloc(0).
2007-08-25 01:02:22 UTC in iODBC
-
SQLGetCursorName() should always return a cursor name, even on an unopened cursor, according to the ODBC documentation from Microsoft. See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsqlbindparameter.asp
The current behavior is correct for ODBC 2.x, but not ODBC 3.x.
2007-05-02 17:03:44 UTC in iODBC
-
If you try to use both SQLFetchScroll and SQLFetch to process the results of a statement, a function sequence error is thrown (S1010). According to the Microsoft ODBC documentation, "Calls to SQLFetchScroll can be mixed with calls to SQLFetch but cannot be mixed with calls to SQLExtendedFetch." (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsqlfetchscroll.asp)
2007-02-22 02:49:59 UTC in iODBC
