A stringified version of the base_filter, to be used in a where clause when generating unique indexes

The configured custom_indexes for a resource

The configured custom_statements for a resource

The configured exclusion_constraint_names

The configured foreign_key_names

A list of keys to always include in upserts.

The configured identity_index_names

Whether or not the resource should be included when generating migrations

A keyword list of customized migration defaults

A list of attributes to be ignored when generating migrations

A keyword list of customized migration types

The configured polymorphic? for a resource

The configured polymorphic_reference_name for a resource

The configured polymorphic_reference_on_delete for a resource

The configured polymorphic_reference_on_update for a resource

The configured reference for a given relationship of a resource

The configured references for a resource

The configured repo for a resource

Identities not to include in the migrations

Skip generating unique indexes when generating migrations

Whether the migration generator should create a strict table

The configured table for a resource

The configured unique_index_names

Whether Ash may wrap write actions on this resource in a transaction.

Declared on the repo, via AshSqlite.Repo.write_transactions?/0, because everything that makes a transaction safe on SQLite — the pool size, the busy timeout, whether the connection is read only — is repo configuration.