ID: 8811
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: ODBC related
Description: DB2 SQLColumns() doens't work by default.

The workaround posted is incorrect as it'll change
the action of the cat/schema/table/etc values and
not the SIZE of the values.

Please ignore the workaround - the SQLColumns()
bugreport is still correct otherwise.

Previous Comments:

[2001-01-19 15:42:51] [EMAIL PROTECTED]
In ext/php_odbc.c function odbc_columns() has 
an incorrect SQLColumns() set of parameters for
DB2 databases.

rc = SQLColumns(result->stmt,
            cat, SAFE_SQL_NTS(cat),
            schema, SAFE_SQL_NTS(schema),
            table, SAFE_SQL_NTS(table),
            column, SAFE_SQL_NTS(column));

it should be something more along the lines of 
rc = SQLColumns(result->stmt,
            cat, 0,
            schema, strnlen(schema),
            table, strnlen(table),
            column, strnlen(column));

DB2 Documentation link

Currently it follows the SQLColumns as described by the
MSDN, which says:

"If the SQL_ATTR_METADATA_ID statement attribute is set to SQL_TRUE, ColumnName is 
treated as an identifier, and its case is not significant. If it is SQL_FALSE, 
ColumnName is a pattern value argument; it is treated literally, and its case is 

By default, DB2 has SQL_ATTR_METADATA_ID set to SQL_FALSE
and doesn't work with the current code.  Can we get at least a check and warning 
message for SQL_FALSE?  I don't know about Oracle.




Full Bug description available at:

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to