Ruben Vermeersch

> It seems that ogen calls `io.ReadAll` on the response body This doesn't seem to be the case anymore?

BTW, I think this can be implemented in a backwards compatible way (not break user code). ```go func encodeSomethingResponse(response SomethingOK, w http.ResponseWriter) error { w.Header().Set("Content-Type", "application/octet-stream") w.WriteHeader(200) writer := w...

I can't possibly merge this without a migration path, otherwise it'll break everyone's code. Plus it'd be a break in compatibility/behavior. Finally: how do you recover from the migration error...

> It will not break existing installations, as if your db doesn't have checksum column, it will not populate data for it (will double check) Fairly certain gorp will throw...

Hi @ljluestc, thanks for making this. Was this created with the help of an LLM? If so: please manually review both the code and description, I don't accept LLM code...

@koleo Any reason in particular why you're automating things from bash, as opposed to using sql-migrate as a library in your application?