db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1964) Update the documentation of SYSCS_UTIL.SYSCS_COMPRESS_TABLE for the changes that went in as part of DERBY-737
Date Tue, 29 May 2007 18:47:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-1964:
----------------------------------


how about just changing backing indexes to newly created indexes.  

The concept is that for the operations mentioned Derby may create "internal" indexes to support
the operation.  
For instance when you add a unique constraint, Derby will first check if there are any existing
indexes that already guarantee that
unique constraint, if so no index is added (and no update of statistics), but if no index
exists then a new internal index is 
generated with a system generated name that enforces uniqueness when a row is inserted.  

> Update the documentation of SYSCS_UTIL.SYSCS_COMPRESS_TABLE for the changes that went
in as part of DERBY-737
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1964
>                 URL: https://issues.apache.org/jira/browse/DERBY-1964
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Laura Stewart
>            Priority: Minor
>         Attachments: cadminspace21579.html, ctunstats57373.html, ctunstats57373.html,
derby1964_1.diff, derby1964_2.diff, rrefaltertablecompress.html, rrefaltertablecompress.html,
rrefproceduresinplacecompress.html
>
>
> As part of DERBY-737 "SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they
do not exist", SYSCS_UTIL.SYSCS_COMPRESS_TABLE now will create statistics for indexes if they
do not already exist. This needs to be documented. The changes went into 10.3 codeline when
I created this documentation jira entry. The changes may get ported to prior releases. Please
check DERBY-737 to see what all releases will need the documentation changes. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message