Bug #36441 SQLPrimaryKeys returns mangled strings

Description:
SQLPrimaryKeysW returns mangled strings for the table name, column name and primary key name (only the first letter been returned).

For a table that is defined as
    create table t1234567890123456789 ( 
	pk_for_table1	integer	    not null auto_increment, 
	c1_for_table1	varchar( 128 )  not null unique, 
	c2_for_table1	binary( 32 )    null, 
	primary key( pk_for_table1, c1_for_table1 ) ) 
SQLPrimaryKeysW would return
	Table Catalog: <NULL>
	Table Schema:  <NULL>
	Table Name:    t123456789012
	Column Name:   p
	keySeq:        1
	pk Name:       P

	Table Catalog: <NULL>
	Table Schema:  <NULL>
	Table Name:    t123456789012
	Column Name:   c
	keySeq:        2
	pk Name:       P

How to repeat:
The attached zip file contains odbcbug.c, odbcbug.exe fow Windows.

Here are the steps to reproduce this problem:

1) Detached the attached zip file and unzip it;
2) Run
        odbcbug "dsn=...;uid=...;pwd=..."
Then you'll see this problem.

Hi John and thanks for your report. Verified just as described using MySQL server 50.058PB on WinXP Pro SP2 localhost:

SQLPrimaryKeys:
	In:	StatementHandle = 0x00851FE0, CatalogName = "test", NameLength1 = 4, SchemaName = "test", NameLength2 = 4, TableName = "t1234567890123456789", NameLength3 = 20
	Return:	SQL_SUCCESS=0

Get Data All:
"TABLE_CAT", "TABLE_SCHEM", "TABLE_NAME", "COLUMN_NAME", "KEY_SEQ", "PK_NAME"
<Null>, <Null>, "t123456789012", "p", 1, "P"
<Null>, <Null>, "t123456789012", "c", 2, "P"
2 rows fetched from 6 columns.

hi,
do you fix the problem in a later release? i have a similar bug using OpenSchema(adSchemaPrimaryKeys, Array(Empty, Empty, "defcontrols")) with the ado-connection-object. if the table has more than one unique key, the returned recordset has not the correct pk-info about table, column and index-name:

TABLE_CATALOG Null
TABLE_SCHEMA  Null
TABLE_NAME    defc   --> correct string: "defcontrols"
COLUMN_NAME   i      --> correct string: "id"
COLUMN_GUID   Null
COLUMN_PROPID Null
ORDINAL        1 
PK_NAME       P      --> correct string: "Primary"

when using odbc v3.51.21 (or higher), it works...

i forgot to let you know: myodbc v5.1.5 is currently installed on win xp sp3...

Bug#39563 was marked as duplicate of this report.

Patch for the bug. diff against rev#867

Attachment: bug36441.patch (text/x-patch), 9.08 KiB.

please fix the instances of functions/variables with 'lengthes' or 'LENGTHES' in the name to just 'lengths' and 'LENGTHS'.

pushed to working_tree as rev#890

pushed to trunk

An entry has been added to the 5.1.7 changelog:

SQLPrimaryKeysW returned mangled strings for table name, column name and primary key name.