Date: Wed, 06 Jan 2016 02:40:57 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 205943] [NEW PORT] databases/p5-App-Sqitch: Sane database management Message-ID: <bug-205943-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205943 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@FreeBSD.org Reporter: henrik@hodne.io Created attachment 165134 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D165134&action= =3Dedit 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 i= s 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=E2=80=94even on = changes from other Sqitch projects. This ensures proper order of execution, even when yo= u=E2=80=99ve 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=E2= =80=99t 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=E2=80=99re not locked in just= because they=E2=80=99ve been committed to your VCS. This allows you to take an iter= ative approach to developing your database schema. Or, better, you can do test-dr= iven database development. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205943-13>