duckdb-jev
Ask Jev questions over DuckDB rows and keep typed SQL results.
What Jev decides
Which label fits, where a row falls on a rubric, or the probability of a yes answer.
duckdb-jev adds SQL functions for per-row Jev Choice, Score, and Noul decisions, including a struct function for batched questions.
- Jev role
- Make typed judgments about each queried row.
- Input
- Row text and SQL-literal answer criteria.
- Output
- Typed SQL ENUM, DOUBLE, or STRUCT values with probabilities and confidence where applicable.
- Decision frequency
- When a query evaluates a Jev function for a row.
- Fallback
- Invalid criteria fail at planning; an optional setting turns call errors into NULL results.
How it works
Overview
The extension accepts a row’s text and constant answer criteria, calls Jev, and returns DuckDB types such as ENUM, DOUBLE, or STRUCT. Multiple questions can share one request through jev_ask. It exposes request and cache usage, sends rows concurrently in bounded chunks, and retries selected transport failures. Each evaluated row can incur a paid model call; query planning rejects invalid criteria before processing rows.
- Language
- C++
- License
- MIT
- Author
- colliber
Sources
Related projects
pg-jev
Use Jev decisions directly inside PostgreSQL filters, rankings, and classifications.
What Jev decides
Whether a row matches, how strongly it matches, or which supplied label best describes it.
Jev Review
A code-review pipeline assembled from small typed judgments instead of one long reviewer prompt.
What Jev decides
What is risky, which files and evidence matter, what could fail, how severe it is, and who should review it.
blink
Multiple Jev walkers navigate a repository tree one directory choice at a time.
What Jev decides
Which visible file or subdirectory should a walker inspect next.