-
When running `status`, if the database has not been initialized, you get an unexpected error:
```
> sqitch -d try status
# On database try
ERROR: relation "changes" does not exist
LINE 13: …
-
The change description is part of the change id. It would be great to trim it before hashing it.
For example, if someone leaves a trailing space at the end of the change description, and someone else …
-
If a change is reworked, and a change after that (perhaps in another project?) requires it, Sqitch will hurl an error:
> Key "foo" matches multiple changes
This is because `change_id_for()` chokes i…
-
Migrated from [rt.perl.org#116132](https://rt-archive.perl.org/perl5/Ticket/Display.html?id=116132) (status was 'rejected')
Searchable as RT116132$
p5pRT updated
11 years ago
-
Example:
```
> sqitch verify
Verifying flipr_test
* appschema .................. ok
* users ...................... ok
* insert_user ................ ok
* change_pass @@v1.0.0-dev1 .. ok
``…
-
Currently during `sqitch deploy`, Sqitch checks the dependencies (`requires` and `conflicts`) for each change before it is deployed. The downside is that one could get halfway through a deploy before …
-
Rather than relying on the most recently-applied change, consider storing the current change name (and ID) in the `projects` table. This will remove ambiguity. Also consider modifying the ID stored in…
-
The new `core.uri` setting should only be on a per-project basis. And I think I am going to want a project name config, too. So add a new config section, "project", and change the `config` command to …
-
I've added App::Sqitch::X; we should use that for all exceptions in non-command code. Some commands might still fail or bail, but really only if they need to exit with no message (such as for a comman…
-
So far, untracked steps can be found and deployed under the tag "HEAD+". But there are some things that still need figuring out:
- How to update the tag in the DB once the changes have a real tag.
- H…