Doctrine fails to apply DEFAULT CURRENT_TIMESTAMP for DateTime field #7436

New Issue

admin · 2026-01-22T15:51:39+01:00

admin commented

2026-01-22 15:51:39 +01:00

Originally created by @Legend999 on GitHub (Oct 27, 2024).

Bug Report

Q	A
doctrine/orm	3.3.0
doctrine/dbal	4.2.1
database	10.4.28-MariaDB

Summary

Doctrine fails to apply the default timestamp for a field defined with DEFAULT CURRENT_TIMESTAMP. When persisting an entity without manually setting the date, it raises a "column cannot be null" error, despite the database schema having a default value set.

Current behavior

Uncaught PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'sent_at' cannot be null in vendor/doctrine/dbal/src/Driver/PDO/Statement.php:55

Expected behavior

Doctrine should use the default timestamp set in the schema (DEFAULT CURRENT_TIMESTAMP), allowing to create new entities without explicitly setting the value.

How to reproduce

Define a Doctrine entity with a datetime column that has a default value of CURRENT_TIMESTAMP, as shown below:

#[Entity]
#[Table(name: 'messages')]
class Message
{
    #[Column(name: 'sent_at', type: Types::DATETIME_IMMUTABLE, updatable: false, options: ['default' => 'CURRENT_TIMESTAMP'])]
    private readonly DateTimeImmutable $sent_at;
    // ...
}

Generate the schema using orm:schema-tool:create --dump-sql, resulting in SQL similar to:

CREATE TABLE messages (
  id int unsigned AUTO_INCREMENT NOT NULL,
  sent_at datetime DEFAULT CURRENT_TIMESTAMP NOT NULL,
  message text NOT NULL,
  PRIMARY KEY (id)
);

Attempt to create a new Message entity without setting the sent_at property:

$message = new Message($message);
$this->entity_manager->persist($message);
$this->entity_manager->flush();

Additional information

The issue seems to be specific to PHP/Doctrine, as running a raw SQL INSERT INTO messages (message) VALUES ('message') correctly assigns the sent_at field to the current timestamp.

Originally created by @Legend999 on GitHub (Oct 27, 2024). ### Bug Report  | Q | A |-------------------------------------------- | ------ | doctrine/orm | 3.3.0 | doctrine/dbal | 4.2.1 | database |10.4.28-MariaDB #### Summary  Doctrine fails to apply the default timestamp for a field defined with `DEFAULT CURRENT_TIMESTAMP`. When persisting an entity without manually setting the date, it raises a "column cannot be null" error, despite the database schema having a default value set. #### Current behavior  ``` Uncaught PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'sent_at' cannot be null in vendor/doctrine/dbal/src/Driver/PDO/Statement.php:55 ``` #### Expected behavior  Doctrine should use the default timestamp set in the schema (`DEFAULT CURRENT_TIMESTAMP`), allowing to create new entities without explicitly setting the value. #### How to reproduce  1. Define a Doctrine entity with a datetime column that has a default value of `CURRENT_TIMESTAMP`, as shown below: ``` #[Entity] #[Table(name: 'messages')] class Message { #[Column(name: 'sent_at', type: Types::DATETIME_IMMUTABLE, updatable: false, options: ['default' => 'CURRENT_TIMESTAMP'])] private readonly DateTimeImmutable $sent_at; // ... } ``` 2. Generate the schema using orm:schema-tool:create --dump-sql, resulting in SQL similar to: ``` CREATE TABLE messages ( id int unsigned AUTO_INCREMENT NOT NULL, sent_at datetime DEFAULT CURRENT_TIMESTAMP NOT NULL, message text NOT NULL, PRIMARY KEY (id) ); ``` 3. Attempt to create a new Message entity without setting the sent_at property: ``` $message = new Message($message); $this->entity_manager->persist($message); $this->entity_manager->flush(); ``` # Additional information The issue seems to be specific to PHP/Doctrine, as running a raw SQL `INSERT INTO messages (message) VALUES ('message')` correctly assigns the sent_at field to the current timestamp.

admin commented

2026-01-22 15:51:40 +01:00

@goforthanddie commented on GitHub (Dec 9, 2024):

I am experiencing the same problem with ORM 3.3.0.0. However, it helped when I added 'insertable: false' as additional parameter for the column :).

@goforthanddie commented on GitHub (Dec 9, 2024): I am experiencing the same problem with ORM 3.3.0.0. However, it helped when I added 'insertable: false' as additional parameter for the column :).

admin commented

2026-01-22 15:51:41 +01:00

@greg0ire commented on GitHub (Nov 20, 2025):

I think this is just a documentation issue, what you've done makes sense @goforthanddie .

@greg0ire commented on GitHub (Nov 20, 2025): I think this is just a documentation issue, what you've done makes sense @goforthanddie .

admin referenced this issue

2026-01-22 16:07:43 +01:00

[PR #7436] Сheck platform supports foreign key constraints #10486

Sign in to join this conversation.