UniqueEntity

Validates that a particular field (or fields) in a Doctrine entityare unique.

This is commonly used, for example, to prevent a new user to register using

an email address that already exists in the system.

Validates that a particular field (or fields) in a Doctrine entityis (are)

unique.This is commonly used, for example, to prevent a new user to register

usingan email address that already exists in the system.

| Applies to|:ref:`class<validation-class-target>`|

Basic Usage

Suppose you have an ``AcmeUserBundle`` with a ``User`` entity that has an

``email`` field. You can use the ``Unique`` constraint to guarantee that the

``email`` field remains unique between all of the constrains in your user table:

Suppose you have an ``AcmeUserBundle`` bundle with a ``User`` entity that has an

``email`` field. You can use the ``UniqueEntity`` constraint to guarantee that

the ``email`` field remains unique between all of the constraints in your user

table:

..configuration-block::

This required option is the field (or list of fields) on which this entity

should be unique. For example, you could specify that both the email and

name fields in the User example above should be unique.

name fields in the``User`` example above should be unique.

message

**type**: ``string`` **default**: ``This value is already used.``

The message that's displayedwith this constraint fails.

The message that's displayedwhen this constraint fails.

em

~~

**type**: ``string``

The name of the entity manager to use for making the query to determine the

uniqueness. If left blank, the correct entity manager will determined for

uniqueness. Ifit'sleft blank, the correct entity manager will determined for

this class. For that reason, this option should probably not need to be

used.