PhoenixKitCatalogue.Schemas.ItemAttributeGroup (PhoenixKitCatalogue v0.19.1)

Item ↔ attribute-group assignment row.

A join table from day one: the current one-group-per-item business rule is carried by the DB's UNIQUE (item_uuid) index (surfaced here as a unique_constraint), so the planned multi-group future is one index swap, not a data migration. The row's own UUID is the durable parent future per-item narrowing state will hang off.

Summary

Types

t()

Functions

changeset(assignment, attrs)

Types

t()

@type t() :: %PhoenixKitCatalogue.Schemas.ItemAttributeGroup{
  __meta__: term(),
  attribute_group: term(),
  attribute_group_uuid: term(),
  inserted_at: term(),
  item: term(),
  item_uuid: term(),
  position: term(),
  updated_at: term(),
  uuid: term()
}

Functions

changeset(assignment, attrs)