Bug #15713 null pointer when use the table qualifier in SQLColumns()
Submitted: 13 Dec 2005 15:10 Modified: 12 Jun 2007 1:05
Reporter: Bogdan Degtyariov Email Updates:
Status: Can't repeat Impact on me:
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.12 OS:Any
Assigned to: Jim Winstead CPU Architecture:Any

[13 Dec 2005 15:10] Bogdan Degtyariov
An application that uses MySQL Connector/ODBC displays an error :
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
Error caused by SQLColumns() function with a connection string that doesn't contain a Database=.. value.

How to repeat:
The connection string should not contain "Database=mybase" parameter.
Use SQLColumns(hStmt, "mybase",....
Below is the test program and the table structure:

CREATE TABLE `tbl_test` (
  `test_id` int(10) unsigned NOT NULL auto_increment,
  `test_string` varchar(45) character set latin1 NOT NULL default '',
  PRIMARY KEY  (`test_id`),
  UNIQUE KEY `Index_unique` (`test_string`)
[13 Dec 2005 15:11] Bogdan Degtyariov
test case that illustrates the bug

Attachment: test.c (text/plain), 6.54 KiB.

[12 Jun 2007 1:05] Jim Winstead
i was unable to reproduce this. i've added a test case to the test suite.