Permalink
Browse files

Note ID changes.

  • Loading branch information...
1 parent 4eb1096 commit 7330192effd02b42d49b73413813b8b90f42217d @theory committed Nov 21, 2012
Showing with 8 additions and 1 deletion.
  1. +8 −1 Changes
View
@@ -14,7 +14,7 @@ Revision history for Perl extension App::Sqitch
supported commands (`sqitchcommands`), rather than the list of core
options. Thanks to BryLo for the suggestion.
- Changed the plan parser so that it no longer changes the order of
- changes based on the depenency change. Unfortunately, this meant that
+ changes based on the depenency graph. Unfortunately, this meant that
the order could change from one run to another, especially if new
changes were added since the last deploy. The planner now throws an
exception if the order in the plan is wrong, and suggests that the user
@@ -25,6 +25,13 @@ Revision history for Perl extension App::Sqitch
database failed, there was just a rollback message. Sqitch will now
emit the underlying error *and* run the revert script for the
just-deployed change.
+ - Modified the text hashed for change and tag IDs. Both now include the
+ note, if present, and changes include the ID of the preceding change
+ and the list of dependencies. The result is that, when a change is
+ modified, it gets a new ID, and if it's moved in the plan, it gets a
+ new ID. The upshot is that things must be in order for a deploy to
+ succeed. Existing deployments will automatically have their IDs
+ updated.
- Symbolic refererences `^` and `~` on the deployed change symbolic tags
`@LAST` and `@FIRST` now correctly calculate the offset according to
the changes deployed to the database, rather than relative to the

0 comments on commit 7330192

Please sign in to comment.