[ http://issues.apache.org/jira/browse/DERBY-737?page=all ]
Mike Matrigali updated DERBY-737: --------------------------------- I believe your interpretation is correct. The request is to always "update" statistics when running the compress table command. Internally this may mean updating a row or creating a new row - the difference need not be documented to the user. Since the entire index is getting rebuilt, I can think of no reason not to gather the statistics and record them at this time. > SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they do not exist > ----------------------------------------------------------------------------- > > Key: DERBY-737 > URL: http://issues.apache.org/jira/browse/DERBY-737 > Project: Derby > Issue Type: Improvement > Components: SQL > Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.1.1, 10.1.1.2, > 10.1.2.0, 10.1.2.1, 10.2.1.6, 10.1.3.0, 10.1.2.2, 10.0.2.2 > Reporter: Kathey Marsden > Priority: Minor > > There must be an entry in the SYSSTATISTICS table in order for the > cardinality statistics in SYSSTATISTICS to be created with > SYSCS_UTIL.SYSCS_COMPRESS_TABLE > SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they don't > exist. The only way to create them if the index was created on an empty > table, seems to be to drop and recreate the index after the table has been > loaded. > The documentation will also need updating if this change is made. > http://db.apache.org/derby/docs/10.1/tuning/ctunstats57373.html -- 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
