ash_postgres v0.25.2 AshPostgres.Repo behaviour View Source

Resources that use the AshPostgres data layer use a Repo to access the database.

This repo is a slightly modified version of an Ecto.Repo.

You can use Ecto.Repo's init/2 to configure your repo like normal, but instead of returning {:ok, config}, use super(config) to pass the configuration to the AshPostgres.Repo implementation.

Currently the only additional configuration supported is installed_extensions, and the only extension that ash_postgres reacts to is "pg_trgm". If this extension is installed, then the AshPostgres.Predicates.Trigram custom predicate will be available.

def installed_extensions() do
  ["pg_trgm"]
end

Link to this section Summary

Callbacks

Return a list of all schema names (only relevant for a multitenant implementation)

Use this to inform the data layer about what extensions are installed

The path where your tenant migrations are stored (only relevant for a multitenant implementation)

Link to this section Callbacks

Specs

all_tenants() :: [String.t()]

Return a list of all schema names (only relevant for a multitenant implementation)

Specs

installed_extensions() :: [String.t()]

Use this to inform the data layer about what extensions are installed

Link to this callback

tenant_migrations_path()

View Source

Specs

tenant_migrations_path() :: String.t()

The path where your tenant migrations are stored (only relevant for a multitenant implementation)