This is an alternative way to run your migrations on PlanetScale without using any migration files and tracking table in your database.
[x] Changes were tested locally and schema changes were applied successfully
Drizzle Kit itself should be used only locally and not pushed to a bundle to be deployed. It means you can exclude drizzle.config.ts from being bundled and can use any dependencies you need (even those that are not edge-compatible).
Changes
In this PR, you can see 2 changes:
Add a script to package.json.
Import .env variables to drizzle.config.ts. As long as it's a separate process of creating and pushing the migrations, it has nothing to do with other project setups like Next or any other library.
Usage explanation
Anytime you change your schema in ts code and are ready to push it to your dev/feature branches on PlanetScale, run the db:push script from package.json. It will sync your schema with the database and warn if any data-loss actions will be applied.
When you are ready with a feature, deploy your code and invoke branch merging on the PlanetScale side so the database will be in sync with your code.
This is an alternative way to run your migrations on PlanetScale without using any migration files and tracking table in your database.
Drizzle Kit itself should be used only locally and not pushed to a bundle to be deployed. It means you can exclude
drizzle.config.tsfrom being bundled and can use any dependencies you need (even those that are not edge-compatible).Changes
In this PR, you can see 2 changes:
.envvariables todrizzle.config.ts. As long as it's a separate process of creating and pushing the migrations, it has nothing to do with other project setups like Next or any other library.Usage explanation
db:pushscript frompackage.json. It will sync your schema with the database and warn if any data-loss actions will be applied.Useful tips
If you want to exclude some tables from syncing with your database, you can use the filters option in the Drizzle Kit config. Refer to this link for more information: https://orm.drizzle.team/kit-docs/conf#multi-project-schema
In this case, you can exclude some tables from being deleted while syncing the schema with your code.