db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1739) Index column names in CatalogRowFactory implementations are not required
Date Tue, 22 Aug 2006 16:51:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1739?page=all ]

Daniel John Debrunner updated DERBY-1739:
-----------------------------------------

    Fix Version/s: 10.3.0.0

Fixed in trunk (10.3), may still merge changes over to 10.2 to reduce differences between
branches for future merges.

> 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

        

Mime
View raw message