Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 5 Nov 2026. What's built · Install 0.3.0
jadpo
ReferenceErrors

ErrorsReads and writes · rule

query.group_key

Records cannot be grouped by this.

Area 6, Reads and writes; not declinable; the next step is usually the agent's.

example
type Title = Text {    max_length: 80}entity Loan {    id: Uuid    title: Title    lent_at: Instant}type LoansByYear = Output {    lent_year: Int    loans_made: Int}query loans_by_year() -> List<LoansByYear> {    from: Loan    group: {        lent_year: temporal.year(Loan.lent_at)    }    aggregate: {        loans_made: count()    }    order: [lent_year desc]    limit: 20}
jadpo checkcheck failed: 1 error, 1 file

error temporal.year groups by a date, and Loan.lent_at is Instant

--> main.jadpo:19:34

   |19 |         lent_year: temporal.year(Loan.lent_at)   |                                  ^^^^^^^^^^^^ not a date
reason
A time bucket is worked out by the database, which gives exactly what code gives only for a date: an instant has a day only in a zone, and PostgreSQL's time zone database can differ from the one built into Jadpo.
next
Keep the day as a CalendarDate field, and group by a time bucket of it (agent)
rule
query.group_key
help
https://jadpo.dev/docs/errors/query.group_key

Markdown for agents: /docs/errors/query.group_key.md.Built from Jadpo main at aee2e8f.