| |||||
Sqitch works just like any other version control system, tracking changes between files, but unlike normal VCS systems, Sqitch tracks only changes made to a database.
If something went wrong at one point or another during the development stage, Sqitch allows developers to simply go back in time and track the error, or more simply just revert the entire database.
Here are some key features of "Sqitch":
· Platform agnostic
· ORM agnostic
· Framework agnostic
· VCS integrated (Git) -> no version numbers
· Avoids duplicate data as much as possible
Limitations:
· Still under development.
· For now only PostgreSQL, SQLite and MySQL are supported.
What's New in This Release: [ read full changelog ]
· The `rebase` command no longer fails if the database is already reverted, but just makes a note of it and goes on to the deploy.
· Added the `plan` command. It's like `log`, but shows a list of changes in the plan, rather than events recorded in the database.
· Added `search_changes()` to Plan. Used by the `plan` command.
· Added the `--oneline` option to the `log` command.
· Allow tagging of an arbitrary change, not just the last change in the plan, by passing a change specification (name, ID, or tag) as the second argument to the `tag` command.
· Updated error messages to note that blank characters are not allowed in project, change, or tag names.
Via: Sqitch 0.963






0 Comment:
Post a Comment