Support golang library to use migration inside code

[HoangNguyen689]

What do you want to change?

go-migrate support migration by calling inside code directly.
Why doesn't sqlc support the same feature?
It is much more convenient to use migration inside code.
(We don't have to install the sqlc command at all in the Dockerfile or dev environment)
For example:

engine := sqlc.NewEngine(...)

engine.Migrate()
-> the generated code is updated inside the folder the same as using sqlc command

What database engines need to be changed?

PostgreSQL

What programming language backends need to be changed?

Go

[HoangNguyen689]

@kyleconroy
I would like to hear your word about this problem.

[kyleconroy]

sqlc is not a migration runner. It understands your migrations to do query analysis, but that's all. sqlc works great with go-migrate or goose.

[HoangNguyen689]

@kyleconroy
Maybe you misunderstood what I mean.
(I don't want to migrate with sqlc. the golang-migrate is an example.)
If I want to work with slqc generated code, I have to run this command, right?

sqlc ...

And instead of installing the command tool, and migrate it through the terminal,
why don't we generate the code through the snippet golang code?

[benjaco]

@HoangNguyen689

Go needs the code sqlc generates in order to compile

e.g. take the starting tutorial, in order to compile tutorial.go, the function ListAuthors has to be defined, which sqlc generate does. Therefore, it has to be seperat step