Files
Enterprise-Knowledge-Base/migrations/versioned/000050_user_kb_pins.down.sql
T
wizardchen 7528175a74 feat(knowledge-base): implement per-user pinning for knowledge bases
Refactored the pinning mechanism for knowledge bases to be user-specific, allowing any user with read access to pin knowledge bases independently. This change includes the introduction of a new `user_kb_pins` table to manage pin states, replacing the previous tenant-wide pinning system. Updated relevant API endpoints and service logic to support this new functionality, ensuring that the UI reflects the user's personal pin status.

Additionally, adjusted the knowledge base listing to sort by user-specific pin status, enhancing the user experience by prioritizing pinned items.

Refs: #1303
2026-05-18 17:28:58 +08:00

9 lines
412 B
SQL

-- Rollback: drop per-user KB pin mapping. The tenant-wide is_pinned /
-- pinned_at columns on knowledge_bases were not modified by the up
-- migration and continue to drive the legacy pin behaviour after this
-- rollback runs.
DO $$ BEGIN RAISE NOTICE '[Migration 000050] Rollback: dropping user_kb_pins'; END $$;
DROP INDEX IF EXISTS idx_user_kb_pins_user_tenant_pinned_at;
DROP TABLE IF EXISTS user_kb_pins;