Standardize adjustment reason categories and descriptions

This commit is contained in:
2026-05-21 10:37:11 +07:00
parent d015cb0dda
commit f0ceebbbc8
13 changed files with 177 additions and 47 deletions

View File

@ -0,0 +1,8 @@
CREATE TYPE "AdjustmentReasonCategory" AS ENUM ('SHRINKAGE', 'DAMAGE', 'REGRADE', 'ADJUSTMENT');
ALTER TABLE "adjustment_reasons"
ADD COLUMN "description" VARCHAR(255);
ALTER TABLE "adjustment_reasons"
ALTER COLUMN "category" TYPE "AdjustmentReasonCategory"
USING ("category"::"AdjustmentReasonCategory");

View File

@ -8,6 +8,13 @@ datasource db {
url = env("DATABASE_URL")
}
enum AdjustmentReasonCategory {
SHRINKAGE
DAMAGE
REGRADE
ADJUSTMENT
}
model Role {
id BigInt @id @default(autoincrement())
code String @unique @db.VarChar(50)
@ -486,7 +493,8 @@ model AdjustmentReason {
id BigInt @id @default(autoincrement())
code String @unique @db.VarChar(50)
name String @db.VarChar(100)
category String @db.VarChar(50)
description String? @db.VarChar(255)
category AdjustmentReasonCategory
status String @default("ACTIVE") @db.VarChar(20)
createdAt DateTime @default(now()) @map("created_at")
updatedAt DateTime @updatedAt @map("updated_at")