[
https://issues.apache.org/jira/browse/DERBY-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697325#action_12697325
]
Kathey Marsden commented on DERBY-4121:
---------------------------------------
Thanks Kim for picking up this issue. I think you are right about the types
being missing and the types as you describe them seem correct to me.
The changes look good, but if you are making another round anyway, I think it
would be good to preface the following statement:
It is a good idea to call the SYSCS_UTIL.SYSCS_UPDATE_STATISTICS procedure when
the number of distinct values in an index is likely to have changed
significantly.
with:
Once statistics have been created, they cannot be dropped and should be
maintained.
> Documentation: more UPDATE_STATISTICS fixes needed for Reference Manual and
> Tuning Derby
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-4121
> URL: https://issues.apache.org/jira/browse/DERBY-4121
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.5.0.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-4121.diff, DERBY-4121.stat, DERBY-4121.zip
>
>
> Kathey Marsden comments on DERBY-3787:
> Not a show stopper for the release, but in beginning my buddy testing,
> I noticed the examples should use CALL e.g.
> CALL SYSCS_UTIL.SYSCS_UPDATE_STATISTICS('SAMP','EMPLOYEE','PAY_DESC');
> CALL SYSCS_UTIL.SYSCS_UPDATE_STATISTICS('SAMP', 'EMPLOYEE', null);
> Also in the Tuning Guide under Working with Cardinality Statistics -> When
> Cardinality Statistics Go Stale we should refer users to the
> SYSCS_UTIL.SYSCS_UPDATE_STATISTICS stored procedure to update their
> statistics and cross reference the reference guide.
> Myrna van Lunteren suggests a new issue for this, so I'm filing it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
