Writing conditions
State the condition literally. Leave arithmetic, dates, and exact matches in SQL.
Jev answers the question you wrote, not the question you meant. Concrete wording beats labels.
sql
-- Weak: a tag, not a test
WHERE jev(tickets, 'churn risk')
-- Stronger: the behavior you care about
WHERE jev(tickets, 'the customer threatens to leave, dispute a charge, or take legal action')Keep counting, dates, and equality in SQL. Let the model judge meaning.
sql
SELECT * FROM people
WHERE jev(people, 'the name is European')
AND age > 40;Look at jev_prob() before you pick a threshold. Ambiguous rows really do land near 0.5. That pattern is in Filter and rank.
Send only the columns the judgment needs. A view is the straightforward way; see Combining with SQL.
More on how Jev reads questions: the TypeSafe notes on jev-1.13.