[ http://issues.apache.org/jira/browse/DERBY-1739?page=comments#action_12430577 ] Rick Hillegas commented on DERBY-1739: --------------------------------------
Original submission DERBY-1739 (433491, 433487) merged to 10.2 branch at subversion revision 436898. > Index column names in CatalogRowFactory implementations are not required > ------------------------------------------------------------------------ > > Key: DERBY-1739 > URL: http://issues.apache.org/jira/browse/DERBY-1739 > Project: Derby > Issue Type: Sub-task > Components: SQL > Reporter: Daniel John Debrunner > Assigned To: Daniel John Debrunner > Priority: Minor > Fix For: 10.3.0.0 > > > The initInfo method of CatalogRowFactory takes a set of index column > positions and index names. I was going to remove the passing of column names > and instead get the names from the SystemColumn array returned by > buildColumnList. > Prior to that I added some code to check the existing index names passed in > matched the names in the SystemColumn array and found there were mismatches, > e.g. > checking SYSCONGLOMERATES > MISMATCH SYSCONGLOMERATES > CONGLOMERATEID > CONGLOMERATE_ID > MISMATCH SYSCONGLOMERATES > CONGLOMERATENAME > CONGLOMERATE_NAME > checking SYSSCHEMAS > checking SYSCONSTRAINTS > checking SYSKEYS > checking SYSDEPENDS > checking SYSALIASES > checking SYSVIEWS > checking SYSCHECKS > checking SYSFOREIGNKEYS > checking SYSSTATEMENTS > MISMATCH SYSSTATEMENTS > STMTID > STATEMENTID > checking SYSFILES > checking SYSTRIGGERS > MISMATCH SYSTRIGGERS > TABLEID > CREATIONTIMESTAMP > Looking further to see why these mismatches did not cause problems or what > hdden problems they might be causing I found they are stored in an > IndexInfoImpl class but never used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
