CherryHQ-cherry-studio

mirror of https://github.com/CherryHQ/cherry-studio.git synced 2026-07-03 12:27:41 +08:00

Files

fullex 12e4e60005 feat(data-api): add group and pin resources with polymorphic pin table

Two sibling resources land together because their migration SQL is
generated as one unit and their API-schema / handler wiring has to go
in the same commit to keep the repo compiling.

group: upgrade the existing group table from `sort_order INT` to
`order_key TEXT` (`scopedOrderKeyIndex('group', 'entityType')`) and
expose it as a first-class resource under /groups. Each entityType
owns an independent orderKey sequence. Reorder delegates to the new
applyScopedMoves helper.

pin: brand-new polymorphic table `(id, entityType, entityId, orderKey,
timestamps)` with UNIQUE(entityType, entityId) enforcing idempotency
at the DB layer. One table serves arbitrarily many consumers — same
precedent as entity_tag. No FK to consumer tables; every consumer
service's delete path must call `pinService.purgeForEntity(tx,
entityType, entityId)` to keep the two tables in sync (signature is
tx-first, the mainstream ORM convention; tagService.removeEntityTags
is the project's historical tx-last outlier and is left as-is).

PinService.pin is idempotent and concurrent-safe: a fast-path SELECT
returns existing rows, and a UNIQUE collision under concurrent INSERT
is caught, classified, and re-SELECTed so the caller never sees a
constraint error.

Handler layer is a thin Zod-parse shell — all scope inference, row
lookup, and orderKey computation live in the services.

2026-04-21 23:28:14 -07:00

sqlite-drizzle

feat(data-api): add group and pin resources with polymorphic pin table

2026-04-21 23:28:14 -07:00

README.md

feat(database): message.stats and related message type definitions

2025-12-25 21:52:07 +08:00

sqlite-drizzle.config.ts

fix(drizzle-config): exclude test files from schema glob

2026-04-21 23:11:25 -07:00

README.md

THIS DIRECTORY IS NOT FOR RUNTIME USE

v2 Data Refactoring Notice Before the official release of the alpha version, the database structure may change at any time. To maintain simplicity, the database migration files will be periodically reinitialized, which may cause the application to fail. If this occurs, please delete the cherrystudio.sqlite file located in the user data directory.

Using libsql as the sqlite3 driver, and drizzle as the ORM and database migration tool
Table schemas are defined in src\main\data\db\schemas
migrations/sqlite-drizzle contains auto-generated migration data. Please DO NOT modify it.
If table structure changes, we should run migrations.
To generate migrations, use the command yarn run db:migrations:generate