-
Notifications
You must be signed in to change notification settings - Fork 969
Open
Labels
Description
What do you want to change?
Basically, in any language backend, the SQL would be essentially the same, so why don't we just reuse the same logic that is used to create queries to generate the SQL to run the migrations?
Then we can have essentially a language-agnostic migration runner that works with all the languages that already have the codegen plugin. Even Java! (I am using SQLc with Java on Firebird 2.5 without issues, had to make minor changes to the schema to work with the MySQL backend because of minor syntax issues though).
Something like a Migrate query that get's automatically created when the schema is generated from migration files.
What database engines need to be changed?
PostgreSQL, MySQL, SQLite
What programming language backends need to be changed?
No response