[
https://issues.apache.org/jira/browse/DERBY-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase resolved DERBY-4121.
------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
10.5.1.1
Derby Info: (was: [Patch Available])
Thanks very much, Kathey.
Committed patch DERBY-4121-2.diff to documentation trunk at revision 763965.
Merged to 10.5 branch at revision 763968.
> 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
> Fix For: 10.5.1.1, 10.6.0.0
>
> Attachments: DERBY-4121-2.diff, DERBY-4121-2.zip, 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.
