A postgresql datalayer for the Ash Framework
Find a file
2021-01-22 16:48:31 -05:00
.github fix: update CI versions 2021-01-22 16:47:24 -05:00
config feat: multitenancy (#25) 2020-10-28 22:26:45 -04:00
documentation docs: update docs 2021-01-05 12:51:22 -05:00
lib docs: update --apis docs 2021-01-22 16:47:24 -05:00
logos
priv feat: multitenancy (#25) 2020-10-28 22:26:45 -04:00
test feat: support fragments 2021-01-22 16:47:24 -05:00
.check.exs chore: only run coverage once (#14) 2020-08-27 23:00:57 -04:00
.credo.exs feat: multitenancy (#25) 2020-10-28 22:26:45 -04:00
.formatter.exs feat: support fragments 2021-01-22 16:47:24 -05:00
.gitignore feat: snapshot-based migration generator 2020-09-10 20:26:47 -04:00
CHANGELOG.md chore: release version v0.31.0 2021-01-22 16:48:31 -05:00
LICENSE Update LICENSE 2020-09-21 14:02:15 -04:00
mix.exs chore: release version v0.31.0 2021-01-22 16:48:31 -05:00
mix.lock fix: update CI versions 2021-01-22 16:47:24 -05:00
README.md chore: update to latest ash 2020-12-27 01:20:12 -05:00

AshPostgres

Elixir CI License: MIT Coverage Status Hex version badge

AshPostgres supports all capabilities of an Ash data layer, and it will most likely stay that way, as postgres is the primary target/most maintained data layer.

Custom Predicates:

  • AshPostgres.Predicates.Trigram

DSL

See the DSL documentation in AshPostgres.DataLayer for DSL documentation

Usage

First, ensure you've added ash_postgres to your mix.exs file.

{:ash_postgres, "~> x.y.z"}

To use this data layer, you need to define an Ecto.Repo. AshPostgres adds some functionality on top of ecto repos, so you'll want to use AshPostgres.Repo

Then, configure your resource like so:

postgres do
  repo MyApp.Repo
  table "table_name"
end

Generating Migrations

See the documentation for Mix.Tasks.AshPostgres.GenerateMigrations for how to generate migrations from your resources