[
https://issues.apache.org/jira/browse/DERBY-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan closed DERBY-4938.
----------------------------------
Resolution: Fixed
Fix Version/s: 10.8.0.0
Closing issue.
The functionality seems to work in general, and any issues should be dealt with
in separate JIRAs.
> Implement istat scheduling/triggering
> -------------------------------------
>
> Key: DERBY-4938
> URL: https://issues.apache.org/jira/browse/DERBY-4938
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.8.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.8.0.0
>
> Attachments: derby-4938-1a-istat_scheduling.diff,
> derby-4938-1a-istat_scheduling.stat
>
>
> The istat daemon has to get its orders from somewhere (it is not operating
> purely on its own), and this issue tracks the addition of code that will
> schedule units of works with with the daemon.
> The current approach is based on statement compilation, i.e. prepared
> statements, triggering the addition of units of work.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira