How does goose track version?

[winston0410]

During development, I notice I cannot run a migration that I have run already. I have come across this article and found the -no-versioning flag, but how does goose really track changes? I couldn't find any meta table generated by goose in the DB, and I don't notice it is use filesystem as well?

[winston0410]

I figured out there is a goose_db_version table for tracking things.

[mfridman]

Sorry this was challenging to find, we'll make sure to update the docs with a dedicated page on what goose is actually doing under the hood.

Indeed the migration changes are tracked in a goose_db_version (the name is configurable), a row is inserted whenever a migration is applied (goose up), and removed whenever a migration is deleted (goose down)