Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
databases/p5-App-Sqitch: Update to 1.3.0
PR: 265620 Reported by: bokutin@bokut.in Approved by: maintainer(timeout, >40 days)
- Loading branch information
Showing
4 changed files
with
69 additions
and
49 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,3 @@ | ||
SHA256 (App-Sqitch-0.9994.tar.gz) = 24de7770884419f199d24fa2ce81f5e7a27583028f685e6973a06840be00c646 | ||
SIZE (App-Sqitch-0.9994.tar.gz) = 490681 | ||
TIMESTAMP = 1663422690 | ||
SHA256 (App-Sqitch-v1.3.0.tar.gz) = 7d07635ec77a7faf3c50281c76ec833c68702f14470996cb2203a8bc6abc5bf2 | ||
SIZE (App-Sqitch-v1.3.0.tar.gz) = 632394 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,36 +1,8 @@ | ||
Sqitch is a database change management application. What makes it | ||
different from your typical migration-style approaches? A few things: | ||
|
||
## No opinions | ||
|
||
Sqitch is not integrated with any framework, ORM, or platform. | ||
Rather, it is a standalone change management system with no opinions | ||
about your database engine, application framework, or development | ||
environment. | ||
|
||
## Native scripting | ||
|
||
Changes are implemented as scripts native to your selected database | ||
engine. Writing a PostgreSQL application? Write SQL scripts for | ||
psql. Writing a MySQL-backed app? Write SQL scripts for mysql. | ||
|
||
## Dependency resolution | ||
|
||
Database changes may declare dependencies on other changes -- even | ||
on changes from other Sqitch projects. This ensures proper order | ||
of execution, even when you've committed changes to your VCS | ||
out-of-order. | ||
|
||
## No numbering | ||
|
||
Change deployment is managed by maintaining a plan file. As such, | ||
there is no need to number your changes, although you can if you | ||
want. Sqitch doesn't much care how you name your changes. | ||
|
||
## Iterative development | ||
|
||
Up until you tag and release your application, you can modify your | ||
change deployment scripts as often as you like. They're not locked | ||
in just because they've been committed to your VCS. This allows you | ||
to take an iterative approach to developing your database schema. | ||
Or, better, you can do test-driven database development. | ||
* No opinions | ||
* Native scripting | ||
* Dependency resolution | ||
* Deployment integrity | ||
* Iterative development |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters