[Bug 205943] [NEW PORT] databases/p5-App-Sqitch: Sane database management

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205943

            Bug ID: 205943
           Summary: [NEW PORT] databases/p5-App-Sqitch: Sane database
                    management
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: henrik at hodne.io

Created attachment 165134
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165134&action=edit
p5-App-Sqitch-0.9993.shar

Note: This depends on p5-URI-db, which isn't in the ports tree yet (and that
again depends on p5-URI-Nested, which also isn't in the ports tree). I'll
submit ports for those in the next few minutes as well, and link them here.

>From pkg-descr:

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.