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 Wed, 23 May 2007 22:31:16 GMT

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

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


Instead of:
When cardinality statistics are automatically updated
For the following operations that you perform on a table, Derby automatically creates statistics.
Those operations are: 
(new index only) When you create a new index on an existing non-empty table. 
(new backing indexes only) When you add a primary key, unique, or foreign key constraint to
an existing non-empty table. 
(all indexes) When you run the SYSCS_UTIL.SYSCS_COMPRESS_TABLE system procedure. Statistics
are created if they do not already exist. 
For other operations, Derby automatically updates statistics for the table and all indexes
on the table if they are already exist. Those operations are: 
(all indexes) When you run the SYSCS_UTIL.SYSCS_COMPRESS_TABLE system procedure. 
(index only) When you drop a column that is part of a table's index; the statistics for the
affected index are dropped, and statistics for the other indexes on the table are updated.


Something like:
When cardinality statistics are automatically updated
For the following operations that you perform on a table, Derby automatically either creates
new statistics or updates existing statistics. Those operations are: 
(new index only) When you create a new index on an existing non-empty table. 
(new backing indexes only) When you add a primary key, unique, or foreign key constraint to
an existing non-empty table. 
(all indexes) When you run the SYSCS_UTIL.SYSCS_COMPRESS_TABLE system procedure. Statistics
are created if they do not already exist. 
(index only) When you drop a column that is part of a table's index; the statistics for the
affected index are dropped, and statistics for the other indexes on the table are updated.





> 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
>         Assigned To: Laura Stewart
>            Priority: Minor
>         Attachments: cadminspace21579.html, ctunstats57373.html, derby1964_1.diff, 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