Skip to content

IDs and row identity

Every row in Minyu has a stable identity. This identity is independent of how the row is displayed, filtered, or referenced in forms.

Understanding row identity is essential when working with classifications, permissions, bulk import, integrations, and set operations. Identity determines whether two references point to the same row.

Row identity

A row represents a single, distinct entity within a table.

Row identity means that each row can be uniquely distinguished from all other rows in the same table. This identity does not depend on descriptive values such as names, labels, or timestamps. Those values may change. Identity does not.

Identity remains stable for the lifetime of the row.

Internal id vs external identifiers

Minyu assigns an internal identifier (id) to each row. This identifier:

  • Is unique within the table.
  • Does not change.
  • Is generated and managed by the system.

In addition to the internal id, a row may have one or more external identifiers (for example, codes or reference numbers defined by the organization).

External identifiers:

  • Are stored as normal column values.
  • May be editable.
  • May not be globally unique unless explicitly constrained.

The internal id guarantees identity. External identifiers provide domain meaning but do not replace the system identifier.

Where identity is used

Row identity is used in several parts of the system:

  • Relation definitions link rows using their internal identity.
  • Set operations compare rows based on identity, not display values.
  • Classifications evaluate membership and relationships based on identity.
  • Bulk import and API operations resolve target rows using identifiers.
  • Permissions and write rules determine which specific row is affected by a change.

Because identity is stable, behavior remains consistent even if descriptive values change.

Related concepts