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

ErrorsEntities, stores and migrations · rule

data.name_too_long

Name is too long for a table or column.

Area 5, Entities, stores and migrations; not declinable; the next step is usually the agent's.

example
entity Note {    id: Uuid    the_date_this_note_was_last_shown_to_its_owner_in_the_weekly_digest: Instant?}
jadpo checkcheck failed: 1 error, 1 file

error Note.the_date_this_note_was_last_shown_to_its_owner_in_the_weekly_digest is too long a name for a column

--> main.jadpo:3:5

  |3 |     the_date_this_note_was_last_shown_to_its_owner_in_the_weekly_digest: Instant?  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 67 characters
reason
Its column would be called the_date_this_note_was_last_shown_to_its_owner_in_the_weekly_digest, and PostgreSQL keeps names of at most 63 bytes, so a longer one would be cut and could clash with another.
next
Choose a shorter name (agent)
rule
data.name_too_long
help
https://jadpo.dev/docs/errors/data.name_too_long

Markdown for agents: /docs/errors/data.name_too_long.md.Built from Jadpo main at aee2e8f.