Drizzle multi project schema #92
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DRAFT
I implemented a setup for Drizzle's "multi-project schema" on my happy path:
Basically, creates
mysqlTablefunction in thesrc/lib/db/indexfile using the syntax for multi-project schema. Then, depending on the user's choice from the cli, will either importmysqlTablefrom drizzle directly or import it from our specifically created function.Not sure if this is the best way to implement this in this repo, as im not too familiar. But after playing around in here for the first time today, this was the first modification i made so figured i'd put this up as a draft. If its something others are interested in, i can look into implementing for pg + sqlite.