You are browsing a version that is no longer maintained. |
Validation of Documents
Validation of Documents - Application Side
Doctrine does not ship with any internal validators, the reason being that we think all the frameworks out there already ship with quite decent ones that can be integrated into your Domain easily. What we offer are hooks to execute any kind of validation.
|
You don't need to validate your documents in the lifecycle events. Its only one of many options. Of course you can also perform validations in value setters or any other method of your documents that are used in your code. |
Documents can register lifecycle event methods with Doctrine that are called on different occasions. For validation we would need to hook into the events called before persisting and updating. Even though we don't support validation out of the box, the implementation is even simpler than in Doctrine 1 and you will get the additional benefit of being able to re-use your validation in any other part of your domain.
Say we have an Order with several OrderLine instances. We
never want to allow any customer to order for a larger sum than he
is allowed to:
1 <?php
class Order
{
public function assertCustomerAllowedBuying(): void
{
$orderLimit = $this->customer->getOrderLimit();
$amount = 0;
foreach ($this->orderLines AS $line) {
$amount += $line->getAmount();
}
if ($amount > $orderLimit) {
throw new CustomerOrderLimitExceededException();
}
}
} 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Now this is some pretty important piece of business logic in your code, enforcing it at any time is important so that customers with a unknown reputation don't owe your business too much money.
We can enforce this constraint in any of the metadata drivers. First Annotations:
Now validation is performed whenever you call
DocumentManager#persist($order) or when you call
DocumentManager#flush() and an order is about to be updated. Any
Exception that happens in the lifecycle callbacks will be cached by
the DocumentManager.
Of course you can do any type of primitive checks, not null, email-validation, string size, integer and date ranges in your validation callbacks.
1 <?php
/** @Document @HasLifecycleCallbacks */
class Order
{
/** @PrePersist @PreUpdate */
public function validate(): void
{
if (!($this->plannedShipDate instanceof DateTime)) {
throw new ValidateException();
}
if ($this->plannedShipDate->format('U') < time()) {
throw new ValidateException();
}
if ($this->customer === null) {
throw new OrderRequiresCustomerException();
}
}
} 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
What is nice about lifecycle events is, you can also re-use the methods at other places in your domain, for example in combination with your form library. Additionally there is no limitation in the number of methods you register on one particular event, i.e. you can register multiple methods for validation in "PrePersist" or "PreUpdate" or mix and share them in any combinations between those two events.
There is no limit to what you can and can't validate in "PrePersist" and "PreUpdate" as long as you don't create new document instances. This was already discussed in the previous blog post on the Versionable extension, which requires another type of event called "onFlush".
Further readings: Lifecycle Events
Validation of Documents - Database Side
|
This feature has been introduced in version 2.3.0 |
MongoDB ≥ 3.6 offers the capability to validate documents during insertions and updates through a schema associated to the collection (cf. MongoDB documentation).
Doctrine MongoDB ODM now provides a way to take advantage of this functionality thanks to the new @Validation annotation and its properties (also available with XML mapping):
validator- The schema that will be used to validate documents. It is a string representing a BSON document under the Extended JSON specification.action- The behavior followed by MongoDB to handle documents that violate the validation rules.level- The threshold used by MongoDB to filter operations that will get validated.
Once defined, those options will be added to the collection after running
the odm:schema:create or odm:schema:update command.
1 <?php
namespace Documents;
use Doctrine\ODM\MongoDB\Mapping\Annotations as ODM;
use Doctrine\ODM\MongoDB\Mapping\ClassMetadata;
/**
* @ODM\Document
* @ODM\Validation(
* validator=SchemaValidated::VALIDATOR,
* action=ClassMetadata::SCHEMA_VALIDATION_ACTION_WARN,
* level=ClassMetadata::SCHEMA_VALIDATION_LEVEL_MODERATE,
* )
*/
class SchemaValidated
{
public const VALIDATOR = <<<'EOT'
{
"$jsonSchema": {
"required": ["name"],
"properties": {
"name": {
"bsonType": "string",
"description": "must be a string and is required"
}
}
},
"$or": [
{ "phone": { "$type": "string" } },
{ "email": { "$regularExpression" : { "pattern": "@mongodb\\.com$", "options": "" } } },
{ "status": { "$in": [ "Unknown", "Incomplete" ] } }
]
}
EOT;
/** @ODM\Id */
private $id;
/** @ODM\Field(type="string") */
private $name;
/** @ODM\Field(type="string") */
private $phone;
/** @ODM\Field(type="string") */
private $email;
/** @ODM\Field(type="string") */
private $status;
} 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51
Please refer to the @Validation annotation reference for more details on how to use this feature.