# Exasol Virtual Schema 8.0.3 Released: Smarter Aggregates, Cleaner Results

**URL:** https://community.exasol.com/t/exasol-virtual-schema-8-0-3-released-smarter-aggregates-cleaner-results/254
**Category:** Product News
**Created:** [November 25, 2025, 3:48pm UTC](https://community.exasol.com/t/exasol-virtual-schema-8-0-3-released-smarter-aggregates-cleaner-results/254 "2025-11-25T15:48:24Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![bhagyakanwar](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@bhagyakanwar](https://community.exasol.com/u/bhagyakanwar)
#### Post date: [November 25, 2025, 3:48pm UTC](https://community.exasol.com/t/exasol-virtual-schema-8-0-3-released-smarter-aggregates-cleaner-results/254/1 "2025-11-25T15:48:24Z")

</div>

Good news for query purists and performance hawks. [Exasol Virtual Schema 8.0.3](https://github.com/exasol/exasol-virtual-schema/releases/tag/8.0.3) release tightens up aggregate behavior in edge cases so your results are consistent and predictable. When a GROUP BY produces no rows, two things now behave correctly:

- Nested `COUNT()` returns `0` (not `NULL`), preserving the usual COUNT semantics.

- `HAVING` conditions are evaluated properly, even when the grouped result is empty.

These fixes were made in the shared low‑level library that underpins all virtual schemas. That means the foundation is solid—but each individual virtual schema still needs to pick up the update. We’re rolling the changes out, and some schemas may take a bit longer to receive the patched version.  
What you might notice:

- Reports or checks that relied on nested counts over empty groups will no longer produce unexpected NULLs.

- Filtering with `HAVING` should behave consistently, avoiding false positives/negatives in edge cases.

If you need help sequencing updates across your virtual schemas, drop us a note with your environment and timelines—we’ll coordinate to keep your pipelines stable while you adopt 8.0.3.