Array of field names that together form the unique constraint.
Can be single field (e.g., ["email"]) or composite (e.g., ["channel_id", "code"]). All field names must exist in the model. Order matters for composite indexes. Examples: ["code"], ["shopping_channel_id", "nickname"], ["email"]
Explicit marker indicating this is a unique index.
Always true to distinguish from regular indexes. Used by code generator to emit "@@unique" directive in Prisma schema instead of "@@index".
Interface representing a unique index constraint on one or more fields.
Unique indexes enforce data integrity by ensuring no duplicate values exist for the specified field combination. Essential for business rules that require uniqueness like email addresses, codes, or composite keys.