A postgresql datalayer for the Ash Framework
Find a file
2023-08-08 12:18:41 -07:00
.github chore: fix hex_api_key secret ref 2023-02-21 10:28:39 -05:00
.vscode improvement: support latest ash 2022-09-20 23:00:29 -04:00
config improvement: support new distinct_sort option 2023-07-19 12:50:05 -04:00
documentation docs: Add explicit command to tutorial to create the local database. (#160) 2023-08-01 15:56:36 -04:00
lib improvement: custom-extension implementation (#162) 2023-08-08 10:20:26 -07:00
logos feat: use the new DSL builder for config (#7) 2020-06-14 03:04:18 -04:00
priv improvement: custom-extension implementation (#162) 2023-08-08 10:20:26 -07:00
test improvement: custom-extension implementation (#162) 2023-08-08 10:20:26 -07:00
test_snapshot_path improvement: custom-extension implementation (#162) 2023-08-08 10:20:26 -07:00
.check.exs improvement: update to the latest ash 2022-10-07 15:50:20 -04:00
.credo.exs fix: convert Ash.Resource.Aggregate to Ash.Query.Aggregate when adding 2023-07-13 23:27:08 -04:00
.formatter.exs improvement: support deferrable option in migration generator 2023-07-14 16:24:57 -04:00
.gitignore feat: snapshot-based migration generator 2020-09-10 20:26:47 -04:00
.tool-versions improvement: support new distinct features from ash core 2023-07-18 14:48:35 -04:00
CHANGELOG.md chore: release version v1.3.41 2023-08-08 12:18:41 -07:00
LICENSE Update LICENSE 2020-09-21 14:02:15 -04:00
mix.exs chore: release version v1.3.41 2023-08-08 12:18:41 -07:00
mix.lock improvement: update ash 2023-07-31 23:37:53 -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