Small comment on the release notes:
> "During query compilation, Derby now checks if the index cardinality statistics for the tables involved in the query are out of date. If > the statistics are outdated, the query compiler will schedule a job that updates them in a separate thread. "
Strictly speaking, "out-of-date" is an elusive goal, we can't really claim more than a best shot using heuristics. So maybe we should
qualify this statement to say something like "deemed out of date", and add a sentence to say that one can always force an update using SYSCS_UTIL.SYSCS_UPDATE_STATISTICS if the automation doesn't work well enough for an application?