Download the PHP package zimzat/db-changeset-manager without Composer
On this page you can find all versions of the php package zimzat/db-changeset-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download zimzat/db-changeset-manager
More information about zimzat/db-changeset-manager
Files in zimzat/db-changeset-manager
Package db-changeset-manager
Short Description Automate the process of applying SQL files (changesets) to databases of different environments or users.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package db-changeset-manager
Db Changeset Manager
Automate the process of applying SQL files (changesets) to databases of different environments or users.
Create versioned directories where developers can drop SQL files to be applied to other environments through the release process and back to other developers to ensure that everyone stays synced with database changes. This project doesn't try to force specific syntax, verbose declarations, or provide automated conflict resolution or detection; just a simple process of applying changes between environments.
A typical changeset directory would look something like this:
Changes are applied to the database in order of version number and then sorted numerically by file name, thus upgrading from 1.0 to 1.3 would apply 'track-user-actions' before 'track-user-action-date' even though they're the same date prefix.
By default directories should be prefixed with 'v' however this can be changed or eliminated by specifying the versionPrefix in the db.ini. The versioning scheme should otherwise follow the standard set out by version_compare().
Files must be suffixed with .sql and must be uniquely named between all versions but otherwise can be named anything. A natural sort (2 before 10) is done to the list of files before being applied to the database.
Restrictions
- No SELECT statements.
- No CREATE DATABASE, DROP DATABASE, or USE DATABASE statements.
Requirements
- PDO
- MySQL
Install
The supported method to install the utility is through Composer.
Command Line Usage
Once installed a php shell file can be used to apply changes from the command line.
The command line tool expects a configuration file to be defined specifying the access name and permissions.
The available commands, which can also be seen by running the command without any options, are:
PHP Usage
The utility can also be invoked directly from a PHP script by instantiating the \DbVcs\ChangeManager object with its dependencies.
Note: The \DbVcs\Output class should be extended to send results where and how desired (log file, browser, database, etc).
All versions of db-changeset-manager with dependencies
ext-pdo Version *