Skip to content

feat(query): preserve exact numeric filter operands - #38

Merged
meaningforger merged 1 commit into
mainfrom
codex/exact-filter-numbers
Oct 10, 2026
Merged

meaningforger merged 1 commit into
mainfrom
codex/exact-filter-numbers

Conversation

@meaningforger

Copy link
Copy Markdown
Contributor

Summary

  • preserve bounded JSON/YAML numeric filter tokens as json.Number until semantic resolution
  • validate and normalize operands against Integer, Decimal, Float, Boolean, String, and temporal datatypes without echoing values
  • bind exact parameters safely across DuckDB, Doris, and ClickHouse and add a shared precision-boundary execution fixture
  • update REST, MCP, offline CLI, online validation, semantic regression suites, README, and query contract docs

Validation

  • make check
  • make fmt-check
  • make test-duckdb-backend
  • make test-conformance docs-check fmt-check vet

Doris and ClickHouse real-engine execution is covered by the explicit matrix requested after opening this PR.

@meaningforger
meaningforger merged commit 2f39551 into main Oct 10, 2026
5 checks passed
@meaningforger
meaningforger deleted the codex/exact-filter-numbers branch October 10, 2026 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant