tursodatabase / tursodatabase/libsql
Multi-DB Schemas Deprecation, How to update the schema for multiple DBs?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
We've been researching various database technologies for a new project and came across Turso; it has everything we need.
However, with the deprecation of Multi-DB Schemas, what is the procedure for creating a "parent" schema that can propagate updates to the child databases?
Is this no longer possible until the transition to the new "Limbo" db is complete, or is there another way to update the schema for multiple databases?
Contributor guide
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.
Research direction
Start with the linked Multi-DB Schemas deprecation documentation and the current libSQL guidance for schema management. Trace whether a supported workflow exists for propagating updates from a parent schema to child databases, including the Limbo transition mentioned in the issue. Done means the procedure or its current unavailability is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100