Michael Fridman

Results 82 issues of Michael Fridman

This issue aims to document how the out-of-order (`-allow-missing`) migrations feature currently works (`v3.11.2`), its limitations, and a proposal to improve. Much of this is based on excellent feedback from...

discussion
up next

This issue aims to track improvements to the goose CLI command. I have a version of the CLI (built with https://github.com/mfridman/cli) that I quite enjoyed iterating on. ![Image](https://github.com/user-attachments/assets/6c88876d-621a-45fa-ab43-f90fe154a969)

up next

There are currently 7 goose annotations that may be found in a .SQL file. These annotations define how goose behaves when it reads a .SQL file ([outdated post](https://pressly.github.io/goose/blog/2022/overview-sql-file/), but should...

For historic reasons, adding a `GetLatestVersion` query was challenging because goose did not hard-delete rows and instead marked them with `is_applied = false`. Which means you'd end up with something...

More of a thought at the moment, but wanted to jot this down. Currently, the goose package and the CLI are tracked as a single Go module and versioned together...

discussion
up next

First pass at #653 - [x] How to explicitly bind to a port. Effectively, `-p :5432` - [x] How to reduce verbose logging from the package itself. For example, I...

Although there are established patterns in the code base for adding/modifying existing dialects, it'd benefit if we had a blurb or two on how to go about this. Kind of...

docs

Picking up an action item from https://github.com/pressly/goose/pull/520 > Addes testcontainers-go and google-cmp as dependencies for end to end tests. Testcontainers offers much better API for providing disk mounts and ensuring...

Picking up from https://github.com/pressly/goose/pull/507#discussion_r1266498077. This might be a good idea, although need to think carefully about how to implement this.

needs discussion

This meta-issue captures upcoming improvements planned for the `/v3` module of goose. There are no plans to make backwards-incompatible changes. The goal is to add new functionality while keeping the...

up next