Geert-Johan Riemer

I'd like to add a possible use-case/example for this. I'm using the generated messages directly when scanning values from `database/sql`. Sometimes via [sqlx's StructScan](https://godoc.org/github.com/jmoiron/sqlx#Rows.StructScan). This allows for extremely simple code,...

@ivanovaleksey In this scenario I use a separate struct for proto and sql, and copy over the values.

Ahter the db scan, you do still have to copy from obj.Tags to Whatever.Tags, right?

Changing the API to not return an error will break people's code where they actually *expect* to get an error if there are no new migrations. I believe the current...

@magicalbanana seems to be correct. https://github.com/mattes/migrate/blob/master/database/postgres/postgres.go#L164 edit: nvm, `Exec(..)` doesn't keep the stream open, I was confused with `Query(..)`

Could it maybe be that psql interprets the SQL and sends statements seperately, whereas migrate executes all the statements as a single statement?

This implements the changes as described in #11 Existing usage of `Gododir/Godofile.go` should not break, unless `Gododir/Godofile.go` is a `package main`, in which case the user get's an error. Fixing...

Sure no problem!

Right now when a Godofile is not a package main you generate a Godofile_main.go file that imports the Godofile.go as a package and runs godo.Godo(pkg.Tasks). https://github.com/go-godo/godo/blob/master/cmd/godo/main.go#L91:L98 I propose that this...

I've created a gist explaining some of the ideas, please start with reading the README https://gist.github.com/GeertJohan/ffb378b6e6522e2b4661