Goose vs sqldef
Goose
pressly.github.iosqldef
sqldef.github.ioSide by side
| Figure | Goose | sqldef |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Database Migration Tools | 8.3 (#8) | 7.2 (#26) |
| License | The GitHub repository states that Goose is licensed under the MIT License. | The sqldef source files are distributed under the MIT License, while the parser is distributed under Apache License 2.0. |
| Platforms | The installation guide documents prebuilt or source installation for macOS, Linux, and Windows. | The releases page lists downloadable binaries for Windows, macOS (Darwin), and Linux. |
| Purpose | Goose is a database migration tool for managing database schemas with incremental SQL changes and/or Go functions. | sqldef is a CLI tool for diffing SQL schemas and managing RDBMS migrations with regular SQL DDLs. |
Plans
In their own words
Goose
Goose is a free, open-source database migration tool for managing schema changes through incremental SQL files and Go functions. It is available as both a command-line utility and a library. The CLI can apply, roll back, redo, reset, inspect, and version migrations, with documented drivers for ClickHouse, Microsoft SQL Server, MySQL, PostgreSQL, SQLite, Turso, Vertica, and YDB. SQL migration files use an up annotation and may include a down annotation; filenames can use timestamps or sequential numbers. Statements in a migration file run in one transaction by default, with an annotation for running them outside one. Go migration functions can use a transaction when given a transaction argument. Other listed capabilities include embedded and out-of-order migrations, data seeding, and environment variable substitution in SQL migrations. For library use, a provider accepts a database dialect, connection, migration filesystem, and optional configuration. The provider does not lock the database by default, so callers must arrange safe concurrent migrations or configure a session locker.