A postgresql datalayer for the Ash Framework
Find a file
2024-07-12 19:12:55 -04:00
.github ci: don't fail fast on the matrix 2024-02-29 01:14:00 -05:00
.vscode improvement: support latest ash 2022-09-20 23:00:29 -04:00
benchmarks chore: update benchmark 2023-10-18 16:56:09 -04:00
config improvement: fix upsert_fields behavior for upserts 2023-09-25 15:32:20 -04:00
documentation fix: properly format migrations 2024-03-20 16:18:27 -04:00
lib chore: skip splitting nil filter expr 2024-07-12 19:12:55 -04:00
logos feat: use the new DSL builder for config (#7) 2020-06-14 03:04:18 -04:00
priv fix: ensure that from_many? joins are properly limited 2024-02-29 09:22:37 -05:00
test fix: don't use fragment("1") because ecto requires a proper source 2024-05-07 20:01:29 -04:00
test_snapshot_path chore: fix dialyzer issue 2024-02-29 00:07:56 -05:00
.check.exs improvement: update to the latest ash 2022-10-07 15:50:20 -04:00
.credo.exs chore: credo 2024-02-20 22:27:25 -05:00
.formatter.exs improvement: Add nulls_distinct option to CustomIndex (#221) 2024-03-12 20:22:34 -04:00
.gitignore feat: snapshot-based migration generator 2020-09-10 20:26:47 -04:00
.tool-versions fix: properly format migrations 2024-03-20 16:18:27 -04:00
CHANGELOG.md chore: release version v1.5.30 2024-07-12 10:17:33 -04:00
LICENSE Update LICENSE 2020-09-21 14:02:15 -04:00
mix.exs chore: release version v1.5.30 2024-07-12 10:17:33 -04:00
mix.lock fix: properly format migrations 2024-03-20 16:18:27 -04:00
README.md chore: update version in readme 2023-02-05 12:42:16 -05:00

AshPostgres

Elixir CI License: MIT Coverage Status Hex version badge

AshPostgres supports all the capabilities of an Ash data layer. AshPostgres is the primary Ash data layer.

Custom Predicates:

  • AshPostgres.Predicates.Trigram

DSL

See the DSL documentation in AshPostgres.DataLayer for DSL documentation

Usage

Add ash_postgres to your mix.exs file.

{:ash_postgres, "~> 1.3.6"}

To use this data layer, you need to chage your Ecto Repo's from use Ecto.Repo, to use AshPostgres.Repo. because AshPostgres adds functionality to Ecto Repos.

Then, configure each of your Ash.Resource resources by adding use Ash.Resource, data_layer: AshPostgres.DataLayer like so:

defmodule MyApp.SomeResource do
  use Ash.Resource, data_layer: AshPostgres.DataLayer

  postgres do
    repo MyApp.Repo
    table "table_name"
  end

  attributes do
    # ... Attribute definitions
  end
end

Generating Migrations

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

Contributors

Ash is made possible by its excellent community!

Become a contributor