Hujjatlardan qidirish

Sahifa yoki bo‘lim nomini kiriting

Reference14 migrations

Database migratsiyalari

14 ta schema bosqichi va ularning domen maqsadi.

Migratsiya katalogi

#MavzuAsosiy o‘zgarish
001Initial schemaIdentity, provider/model, chat, files, inference, usage, audit, jobs va pgvector bazasi
002Provider endpointEndpoint normalization va provider konfiguratsiyasi
003Runtime limitsLimit siyosati, reservations va usage constraints
004IdempotencyReplay record, fingerprint va ownership
005Chat persistenceConversation/message/parts izchilligi
006Reliable jobsLease, fencing, heartbeat, retry va dead-letter
007Upload integritySHA-256, size, MIME va multipart metadata
008CLI scopesAPI key scope/model/IP siyosati
009Production invariantsConstraintlar va o‘zbekcha platforma defaults
010Projects & searchProject ownership va message search
011Empty conversationsBo‘sh chatlarni katalogdan chiqarish
012PaginationStable cursor va message ordering
013Soft-delete catalogConversation/model lifecycle va active indekslar
014Conversation sharesPublic snapshot token va revoke

Migratsiyani qo‘llash

Command
go run ./backend/cmd/migrate
# yoki Compose release’da
docker compose run --rm migrate

Migration command versiyalangan SQL fayllarni tartibda qo‘llaydi. API/worker yangi schema talab qilsa, migration ular ishga tushishidan oldin muvaffaqiyatli yakunlanishi kerak.

Yangi migratsiya qoidalari

  • Amaldagi faylni tahrirlamang; yangi ketma-ket migration qo‘shing.
  • Katta table rewrite va lock muddatini hisoblang.
  • Expand → migrate data → contract usulini afzal ko‘ring.
  • Old/new binary birgalikda ishlaydigan deploy oynasini test qiling.
  • Constraint va indeksni production data hajmida baholang.