Download the PHP package ravage84/cakephp-multi-column-uniqueness without Composer

MultiColumnUniqueness

A CakePHP 2.x behavior plugin to validate the uniqueness of multiple columns of a model.

Requirements

The plugin has been tested with the following setup(s)

• CakePHP 2.4.1 - 2.5.4
• PHP 5.4.7
• MySQL

But it should work with

• CakePHP 2.4.1 or greater.
• PHP 5.2.8 or greater.
• Other data sources

Installation

• Clone/Copy the files in this directory into app/Plugin/MultiColumnUniqueness
• Ensure the plugin is loaded in app/Config/bootstrap.php by calling CakePlugin::load('MultiColumnUniqueness'); or CakePlugin::loadAll();

Using Composer

See the CakePHP plugin installation guide in the CakePHP Cookbook.

Reporting issues

If you have an problem with this plugin please open an issue. But check if the problem has already been reported.

Contributing

If you'd like to contribute to this project, check out the open issues for any planned features or open bugs. You can fork the project, add features, documentation, and send pull requests; or open issues.

Versioning

This plugin adheres to SemVer (Semantic Versioning). Since the API is still in development, the plugin hasn't reached 1.0 yet.

CakePHP Version Support

There are no plans to backport this to CakePHP 1.x. The plugin should be updated to support future 2.x releases. For CakePHP 3.0 it will need a total rewrite most probably...

How To Use

Let's say you have a model Product which has many fields but two of them need to be unique in conjunction with each other. Those fields are name and manufacturer_id.

As you may know you could use the CakePHP built-in data validation rule named isUnique. This rule even takes multiple columns, which you could implement like this:

``

So why bother using this plugin? Because the solution above has a few downsides. First either you setup the same rule for both/all fields that need to be unique or you just set it for one of the fields.

If you set it for all fields the rule will be executed for each field resulting in multiple (and redundant) SQL queries. If you set it for only one field on the other hand, you have to include that field in the data array every time you want to save one of the fields that need to be unique. This plugins circumvents this by adding the rule dynamically.

To enable the MultiColumnUniquenessBehavior for these fields you need to set the $actsAs property in the Product model.

``

This is the simplest form of setup. It would output a The fields mane and manufacturer_id must be unique. error message when the validation fails.

Additionally you could also choose a custom validation error message like this:

``

Now let's say you also have three other fields named field1, field2, field13 which need to be unique in conjunction with each other in the same model. If you don't need custom error messages, you can set it up like this:

``

For the same situation but with custom error messages, do it like this:

``

By default the data validation rule will be added only to the first field which needs to be unique found in the data array. If you want to enforce the data validation on each unique field, set the onlyOnce option to false. This way the validation error message will be shown on each unique field.

`` This option can only be set per model, not per unique field group.

TODOs

• Running the tests with other databases in Travis, as CakePHP does
• See the open issues

Background Story

I needed to validate the uniqueness of two fields of a model. Not separately as CakePHP supports built-in by the isUnique data validation rule but in conjunction with each other. After I didn't found any built-in solution for my problem I turned to Google and found some articles about this. Also I asked dereuromark if he knew if there was an existing solution. He pointed me to his extended model called MyModel in his Tools project.

Those solutions seemed to work but all of them either weren't up to date, weren't clean enough in their approach or forced me to add way too much code for my narrow needs. So I decided to write a behavior for it (my first by the way).

After I got that to work I thought other people could benefit from it, so I created this project and implemented it as a plugin.