AXIS Documentation / Integration / ORM & Extended Query

ORM & Extended Query

psycopg3 · asyncpg · Prisma · pgJDBC single-statementExtended Query planned

The HTTP path is the production integration today. Native wire protocol and Extended Query (parameterized statements) are separate roadmaps; this page states what is verified with real drivers and what remains planned.

SQLAlchemy adapter (v1)

AxisRoutingSession is a routing session adapter for the HTTP path: writes route through AXIS, reads go direct. It is a v1 adapter, not a universal ORM solution — not every ORM query shape is guaranteed to map cleanly, and raw writes must be policy-visible.

Real driver verification matrix

Driver	Mode	Result
psycopg3	single-statement via AXIS	37 passed (2026-07-05)
asyncpg	single-statement via AXIS	37 passed (2026-07-05)
Prisma	single-statement via AXIS	37 passed (2026-07-05)
pgJDBC	single-statement via AXIS	37 passed (2026-07-05)
pgJDBC	batch (extended protocol)	Not supported — `PIPELINING_SUPPORT=false`, fail-closed
COPY (any driver)	copy mode	Fail-closed — blocked unless explicitly approved; `COPY PROGRAM` always blocked

These tests are lab results from the integration test suite; they prove single-statement enforcement through AXIS with real drivers, not universal ORM compatibility.

Extended Query (EQ) roadmap

Parameterized statements (Extended Query protocol) are planned, not shipped. The lab POC implements Simple Query (Q messages) with direct text and is documented as experimental.

Item	Status
`Q` (Simple Query) intercept & enforce	Experimental lab POC
`P`/`B`/`E` (Parse/Bind/Execute) interception	Planned (EQ0–EQ5)
Bind-value inspection for fail-closed classification	Planned
EQ required before OLTP pilot	Documented requirement (RFC-032 context)

Fail-closed behavior for unsupported shapes

Prepared statements in HTTP mode: AXIS-side PREPARE/EXECUTE session store; EXECUTE without a resolvable session fails safe as unresolved.
Extended-protocol parameter bypass attempts → PARSE_REJECTED_UNTRUSTED_INPUT.
COPY, batch and multi-statement payloads → blocked by default.
Unsupported SQL shapes → classified Unknown → Write/Block defaults.

Do not build production data paths on the wire-protocol POC. Extended Query, COPY and batch support are not complete; current OLTP pilots must use the HTTP path with single statements.