README

In Doctrine DBAL 2.6 immutable DateTime types were added, so if you are using that version or newer, you no longer need this package. If you cannot use that version (it requires PHP 7.1), keep using this package (you can find even PHP 5.6 version in the older versions).

Why would I want to use immutable types?

All Doctrine date/time based types are using DateTime instances, which are mutable. This can lead to breaking encapsulation and therefore bugs. For two reasons:

1. You accidentally modify a date when you are doing some computation on it:

<?php use Doctrine\ORM\Mapping as ORM; /**  * @ORM\Entity()  */ class LogRow { // ... /**  * @ORM/Column(type="datetime")  * @var \DateTime  */ private $createdDate; public function getCreatedDate(): DateTime { return $this->createdDate; } }

<?php // created date might be modified // even if this was not intended by the creator // (there is no "setter" method for this on the entity) var_dump($logRow->getCreatedDate()); // 2015-01-01 00:00:00 $logRow->getCreatedDate()->modify('+14 days'); var_dump($logRow->getCreatedDate()); // 2015-01-15 00:00:00

1. Or you do intentionally try to update it, which fails because Doctrine will not see this:

<?php $product->getRenewDate()->modify('+1 year'); $entityManager->persist($product); // no updates will be fired because Doctrine could not detect change // (objects are compared by identity) $entityManager->flush();

You can prevent this behaviour by returning a new instance (cloning) or using DateTimeImmutable (which returns a new instance when modified).

Installation

If you are using Symfony, you can use vasek-purchart/doctrine-date-time-immutable-types-bundle, which will take care of the integration.

Install package vasek-purchart/doctrine-date-time-immutable-types with Composer:

composer require vasek-purchart/doctrine-date-time-immutable-types 

Then you just need to register the types you want:

<?php use Doctrine\DBAL\Types\Type; use VasekPurchart\Doctrine\Type\DateTimeImmutable\DateImmutableType; use VasekPurchart\Doctrine\Type\DateTimeImmutable\DateTimeImmutableType; use VasekPurchart\Doctrine\Type\DateTimeImmutable\DateTimeTzImmutableType; use VasekPurchart\Doctrine\Type\DateTimeImmutable\TimeImmutableType; // use as date_immutable in mapping Type::addType(DateImmutableType::NAME, DateImmutableType::class); // use as datetime_immutable in mapping Type::addType(DateTimeImmutableType::NAME, DateTimeImmutableType::class); // use as datetimetz_immutable in mapping Type::addType(DateTimeTzImmutableType::NAME, DateTimeTzImmutableType::class); // use as time_immutable in mapping Type::addType(TimeImmutableType::NAME, TimeImmutableType::class);

Or you might want to override some of the default types to work with DateTimeImmutable instead of DateTime:

<?php use Doctrine\DBAL\Types\Type; use VasekPurchart\Doctrine\Type\DateTimeImmutable\DateTimeTzImmutableType; // use as datetimetz in mapping Type::overrideType(Type::DATETIMETZ, DateTimeTzImmutableType::class);

Usage

If you have overridden the default types you don't need to change any mappings.

If you have added the types you only have to suffix your fields with _immutable:

<?php use Doctrine\ORM\Mapping as ORM; /**  * @ORM\Entity()  */ class LogRow { // ... /**  * @ORM/Column(type="datetime_immutable")  * @var \DateTimeImmutable  */ private $createdDate; public function getCreatedDate(): DateTimeImmutable { return $this->createdDate; } }

<?php // created date can no longer be modified from outside var_dump($logRow->getCreatedDate()); // 2015-01-01 00:00:00 $logRow->getCreatedDate()->modify('+14 days'); var_dump($logRow->getCreatedDate()); // 2015-01-01 00:00:00