A postgresql datalayer for the Ash Framework
Go to file
Zach Daniel cd9a38bf2a chore: release version v1.5.7 2024-02-22 07:31:57 -05:00
.github chore: format and fix matrix 2023-11-17 09:17:11 -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 chore: fix credo and update ash 2024-01-29 16:57:04 -05:00
lib fix: properly apply lateral join conditions to left lateral joins 2024-02-22 07:31:06 -05:00
logos feat: use the new DSL builder for config (#7) 2020-06-14 03:04:18 -04:00
priv test: add test that shows subquery error (#199) 2024-01-30 13:17:40 -05:00
test fix: ensure select is properly set on delete_all 2024-02-21 16:37:28 -05:00
test_snapshot_path improvement: support new bulk operations 2023-12-31 08:40:30 -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 docs: update formatter and cheat sheet 2024-01-29 10:52:34 -05:00
.gitignore feat: snapshot-based migration generator 2020-09-10 20:26:47 -04:00
.tool-versions improvement: support latest ash changes 2024-01-19 00:12:50 -05:00
CHANGELOG.md chore: release version v1.5.7 2024-02-22 07:31:57 -05:00
LICENSE Update LICENSE 2020-09-21 14:02:15 -04:00
README.md chore: update version in readme 2023-02-05 12:42:16 -05:00
mix.exs chore: release version v1.5.7 2024-02-22 07:31:57 -05:00
mix.lock improvement: update to latest ash 2024-02-16 16:12:23 -05:00

README.md

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