Packages

arke_postgres

0.6.0
0.8.0-rc.0 0.7.0 0.6.0 0.5.0 0.4.1 0.4.0 0.4.0-bulk.0 0.3.7 0.3.6 0.3.5 0.3.4 0.3.3 0.3.2 0.3.1 0.3.0 0.2.14 0.2.13 0.2.12 0.2.11 0.2.10 0.2.9 0.2.8 0.2.7 0.2.6 0.2.5 0.2.4 0.2.3 0.2.2 0.2.1 0.2.0 0.1.9 0.1.8 0.1.7 0.1.6 0.1.5 0.1.4 0.1.2 0.1.1 0.1.0

Arke postgres

HexDocs Report package

Current section

Files

Jump to
Readme
39 Versions
4 Dependencies
Dependants
Files
Activity
arke_postgres usage-rules.md
Raw

usage-rules.md 

# Rules for working with ArkePostgres



## Understanding ArkePostgres



ArkePostgres is the PostgreSQL persistence adapter for the Arke framework. Arke

core is a runtime-defined schema engine that performs no I/O; it calls plain

function references injected through `config :arke, persistence: %{...}`.

ArkePostgres is the production implementation of that seam: it persists Arke

Units as JSONB rows in a universal `arke_unit` table (or as rows in dedicated

relational tables), translates Arke's query DSL into Ecto queries with

JSONB-aware fragments and recursive-CTE link traversal, provisions one

PostgreSQL schema per Arke project (multi-tenancy via Ecto `prefix:`), and at

boot loads every project's parameters, arkes and groups into Arke's ETS

managers.



It is not an ORM, not a query builder and not a validation layer — those live

in `arke` core. It is PostgreSQL-only by design (JSONB, recursive CTEs,

`CREATE SCHEMA`). Read the topic rules in `usage-rules/` before using it.