A postgresql datalayer for the Ash Framework
Find a file
2020-12-23 15:29:03 -05:00
.github chore: update build 2020-12-23 15:23:11 -05:00
config feat: multitenancy (#25) 2020-10-28 22:26:45 -04:00
documentation chore: uppdate docs/add guide 2020-10-28 23:53:28 -04:00
lib feat: support refs on both sides of operators 2020-12-23 14:46:49 -05:00
logos feat: use the new DSL builder for config (#7) 2020-06-14 03:04:18 -04:00
priv feat: multitenancy (#25) 2020-10-28 22:26:45 -04:00
test feat: support refs on both sides of operators 2020-12-23 14:46:49 -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: multitenancy (#25) 2020-10-28 22:26:45 -04:00
.gitignore feat: snapshot-based migration generator 2020-09-10 20:26:47 -04:00
CHANGELOG.md chore: release version v0.27.0 2020-12-23 15:29:03 -05:00
LICENSE Update LICENSE 2020-09-21 14:02:15 -04:00
mix.exs chore: release version v0.27.0 2020-12-23 15:29:03 -05:00
mix.lock fix: bump ash version 2020-12-23 15:22:40 -05:00
README.md docs: update docs 2020-10-28 23:56:59 -04: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

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