Pimcore\Model\Notification::setModificationDate(): Argument #1 ($modificationDate) must be of type string, null given

[quayle]

Following does not happen on demo, yet I have such issue locally. Are there any migrations or other magic, that additionaly handles following case?

Table: notifications has defined: modificationDate as nullable

modificationDate TIMESTAMP NULL

pimcore/bundles/InstallBundle/dump/install.sql

Line 801 in 23dc5b5

`modificationDate` TIMESTAMP NULL,

Pimcore\Model\Notification::setModificationDate, is not aware of such case and will throw an error when modificationDate in database will be null.

Example:

1. Pimcore\Model\Notification\Dao::getById
   

   pimcore/models/Notification/Dao.php

   Line 39 in 23dc5b5

   public function getById(int $id): void

2. then is called: Pimcore\Model\Notification\Dao::assignVariablesToModel
$data['notificationDate'], fetched from database is null here.

   pimcore/models/Notification/Dao.php

   Line 50 in 23dc5b5

   $this->assignVariablesToModel($data);

3. then is called: Pimcore\Model\Notification::setModificationDate
   

   pimcore/models/Notification/Dao.php

   Line 123 in 23dc5b5

   $model->setModificationDate($data['modificationDate']);

4. Pimcore\Model\Notification::setModificationDate(): Argument #1 ($modificationDate) must be of type string, null given, called in (...)pimcore/pimcore/models/Notification/Dao.php on line 123