A postgresql datalayer for the Ash Framework
Find a file
2023-02-05 12:46:44 -05:00
.github ci: use new postgres flag in CI 2023-01-31 22:47:08 -05:00
.vscode improvement: support latest ash 2022-09-20 23:00:29 -04:00
config chore: update version in readme 2023-02-05 12:42:16 -05:00
documentation chore: update version in readme 2023-02-05 12:42:16 -05:00
lib fix: Actually use AshPostgres.Repo behaviour (#129) 2023-02-05 12:46:44 -05:00
logos feat: use the new DSL builder for config (#7) 2020-06-14 03:04:18 -04:00
priv Add failing test for policy + aggregate issue 2023-01-29 16:15:16 +10:00
test test: demonstrate issue loading aggregate 2023-01-31 10:35:33 +10:00
test_snapshot_path improvement: fix typecasting for calculations & embed access 2022-08-05 15:27:22 -04:00
.check.exs improvement: update to the latest ash 2022-10-07 15:50:20 -04:00
.credo.exs improvement: support manual relationships with joins 2022-09-13 16:40:12 -04:00
.formatter.exs improvement: add migration_ignore_attributes 2023-02-01 02:05:04 -05:00
.gitignore feat: snapshot-based migration generator 2020-09-10 20:26:47 -04:00
.tool-versions chore: add tool-versions 2023-01-31 22:35:24 -05:00
CHANGELOG.md chore: release version v1.3.6 2023-02-03 11:44:49 -05:00
LICENSE Update LICENSE 2020-09-21 14:02:15 -04:00
mix.exs chore: release version v1.3.6 2023-02-03 11:44:49 -05:00
mix.lock improvement: add migration_ignore_attributes 2023-02-01 02:05:04 -05: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