Michael Fridman
Michael Fridman
It's possible this is beyond the scope of what `goose` is intended. Feedback welcome. Consider adding the ability to create / drop a database either directly with psql/pg_* and friends...
The proposal is to enable `goose` to drop the current database schema. This is usually done with tools like `pg_dump`. Now, this would require the user to have this executable...
The current goose table stores the following pieces of information: ``` id version_id is_applied tstamp ``` To improve `goose`, we could record a few additional items, such as: ``` filename...
More details to come.. But it'd be neat to print (or save to a single file) the migrations `goose` will apply, but do not actually apply the migrations. TBD on...
`goose` currently supports `-dir`, which reads migration files either from disk or from an embedded filesystem. We should consider adding support for multiple inputs, such as: - remote git repository...
Currently the implementation of the `status` command is to loop over all the migrations and get the db metadata one-by-one. I think we can do better by retrieving all migrations...
Hey there, interesting project. Just a heads up the `buf protoc` command has moved to `buf alpha protoc` and may in the future be deprecated entirely. More details here: https://github.com/bufbuild/buf/pull/915...
In the examples, `GreetRequest` is a simple struct with a single `Name` field. I was expecting to send the request as an object ```json { "name": "mike" } ``` But...
(Really excited about this project!) The idea of being able to use your own templates is neat, however, when starting out it may be easier (and more manageable) to use...