InformixIDS9.4 ODBC driver query

Hi I am running Informix IDS 9.4 on a Win2K box with the v3.82 ODBC driver. I have a simple table with a primary (unique) key on it. When I look at the index information in dbaccess the index name is 100_1. When I look at the index information in WinSQL the index name is 100_1. When my application calls SQLPrimaryKeys the index name is u100_1. But when my application calls SQLStatistics it is 100_1. When I use an ODBC test tool and call SQLPrimaryKeys the index name is u100_1. I have looked in the Informix ODBC manual but can't find anything enlightening. Is this an undocumented Informix ODBC driver feature, that the names of unique indices are prefixed with a 'u'? Should my code be stripping off the 'u', or am I just then leaving the way open for problems as soon as a user creates an index legitimately beginning with 'u'? Any ideas appreciated! TIA Alex

On 18 Aug 2003 07:58:59 -0700, azp74@hotmail.com (Alex) wrote: >Hi > >I am running Informix IDS 9.4 on a Win2K box with the v3.82 ODBC >driver. > >I have a simple table with a primary (unique) key on it. > >When I look at the index information in dbaccess the index name is >100_1. >When I look at the index information in WinSQL the index name is >100_1. > >When my application calls SQLPrimaryKeys the index name is u100_1. >But when my application calls SQLStatistics it is 100_1. >When I use an ODBC test tool and call SQLPrimaryKeys the index name is >u100_1. > >I have looked in the Informix ODBC manual but can't find anything >enlightening. > >Is this an undocumented Informix ODBC driver feature, that the names >of unique indices are prefixed with a 'u'? Should my code be >stripping off the 'u', or am I just then leaving the way open for >problems as soon as a user creates an index legitimately beginning >with 'u'? > When a constraint is created on a table, Informix will create an underlying index whose first character is a space. The constraint name will be prefaced with a 'u'.