void db: adopt a database already migrated by Drizzle
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- postgresql, typescript
- Domain
- database
Research direction
Read the migration history handling in packages/void/src/migrations/runner-pg.ts, especially the lines linked in the issue, and compare it with the existing hand-written migrations guide at void.cloud/guide/database#hand-written-migrations. Document a step for marking Drizzle-applied migrations as applied in Void; done means the first void deploy applies only migrations that are new.
Written by the indexing model from the issue text.
Description
What
No page explains how to bring an existing PostgreSQL database, already migrated by Drizzle's migrate(), under Void's migration history.
Void records applied migrations in its own _void_migrations table and reads only that table (runner-pg.ts). Drizzle's migrator keeps its history in a different table, so Void's first deploy treats none of those migrations as applied.
Hand-written migrations covers attaching Drizzle metadata to SQL files, not marking them as applied.
Our production database on Neon has a Drizzle migration history. Without a way to keep that history, the move to Void can't start.
Done when
A documented step marks an existing database's migrations as applied, so the first void deploy applies only new ones.
- Dominant language
- TypeScript
- Stars
- 580
- Forks
- 56
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 110
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from voidzero-dev/void
-
Static Cloudflare deploy ignores `cloudflare.assets.html_handling`Possibly taken @0froq claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
voidzero-dev/void#580 ·
Maintainers usually reply within 1 day
-
`void/log` serializes `Error` fields as `{}`, losing message and stackPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voidzero-dev/void#577 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
voidzero-dev/void#576 ·
Maintainers usually reply within 1 day
-
Dev: `better-auth/client/plugins` fails to resolve when auth is enabled (the `better-auth/client` alias matches it as a prefix)Possibly taken @MaxtuneLee claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
voidzero-dev/void#565 ·
Maintainers usually reply within 1 day
-
prepareDeployArtifact omits worker.vars that the CLI managed deploy includesPossibly taken @dvkam claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voidzero-dev/void#529 ·
Maintainers usually reply within 1 day
All issues in voidzero-dev/void
Similar issues
-
freshness freshness:observed-only
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thoroc/context-radar#282 ·
-
bug P2 rust
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area: web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gabe-santana/arkdraw#25 ·
-
bug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
codercops/discord-bot#101 · 1 comment ·
Maintainers usually reply within 1 day