Chapters

29 Chapters | 1:34:37 |

01

Introduction

1:00
02

ManyToOne Doctrine Relationships

4:40
03

Sharing Data between Fixture Classes

1:49
04

Restricting Edit Access to Owners

1:53
05

Using a shortcut Base Controller Class

2:30
06

Using PHPDoc for Auto-Completion

1:26
07

OneToMany: The Inverse Side of a Relationship

5:37
08

Doctrine Extensions: Sluggable and Timestampable

4:30
09

Using the slug in the Event URL

2:04
10

Adding createdAt and updatedAt Timestampable Fields

1:41
11

Creating a Custom orderBy Query

2:11
12

ManyToMany Relationship

2:37
13

Using the ManyToMany so Users can Attend an Event

4:53
14

More with ManyToMany: Avoiding Duplicates

2:51
15

JSON up in your Response

2:50
16

Come on, Set the Content-Type Header!

3:19
17

Adding the AJAX Touch: JavaScript

2:16
18

Customizing Error Pages and How Errors are Handled

6:01
19

Render another Controller in Twig

4:28
20

Creating a Pretty CSV Download

4:19
21

Your Very First Service

4:42
22

Symfony Overlord: The Service Container

4:58
23

Configuration Loading and Type-Hinting

2:01
24

Dependency Inject All the Things

3:14
25

Twig Extensions and Dependency Injection Tags

4:33
26

Doctrine is in your Lifecycle (with Callbacks)

2:08
27

Doctrine Event Listeners

5:59
28

Doctrine Listeners on Update

2:48
29

Keep Going!

1:19

This tutorial has a new version, check it out!

> Symfony 2 > Starting in Symfony2: Course 3 (2.4+)

Buy Access to Course

10.

Adding createdAt and updatedAt Timestampable Fields

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

Login or register to check out the script

10 Comments

Sort By

Login or Register to join the conversation

Himanshu 1 year ago edited

namespace App\Entity;

use App\Repository\UserRepository;
use Doctrine\DBAL\Types\Types;
use Doctrine\ORM\Mapping as ORM;
use Symfony\Bridge\Doctrine\Validator\Constraints\UniqueEntity;
use Symfony\Component\Security\Core\User\PasswordAuthenticatedUserInterface;
use Symfony\Component\Security\Core\User\UserInterface;

#[ORM\Entity(repositoryClass: UserRepository::class)]
#[ORM\Table(name: '`user`')]
#[ORM\UniqueConstraint(name: 'UNIQ_IDENTIFIER_EMAIL', fields: ['email'])]
#[UniqueEntity(fields: ['email'], message: 'There is already an account with this email')]
class User implements UserInterface, PasswordAuthenticatedUserInterface
{
    #[ORM\Column(type: Types::DATETIME_MUTABLE)]
    private ?\DateTimeInterface $createdAt = null;

    #[ORM\Column(type: Types::DATETIME_MUTABLE)]
    private ?\DateTimeInterface $updateAt = null;

    public function getCreatedAt(): ?\DateTimeInterface
    {
        return $this->createdAt;
    }

    public function setCreatedAt(\DateTimeInterface $createdAt): static
    {
        $this->createdAt = $createdAt;

        return $this;
    }

    public function getUpdateAt(): ?\DateTimeInterface
    {
        return $this->updateAt;
    }
    
    public function setUpdateAt(\DateTimeInterface $updateAt): static
    {
        $this->updateAt = $updateAt;
    
        return $this;
    }
}

Error An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'created_at' cannot be null

I will use this @ORM\Column(name="updated_at", type="datetime", options={"default"="1970-01-01 00:00:00"}) same error version latest symfony

|

Victor SFCASTS Himanshu 1 year ago

Hey Himanshu,

That error means that when you create a User entity - you do not set the createdAt properly. You should either do this manually somewhere where you do new User(). Or you can leverage the Timestampable feature from the bundle we're talking about in this video. If it does not work for you automatically, then it means the bundle isn't installed or configured properly.

Cheers!

|

guest 8 years ago

there is a typo in header:
updatdAt

|

weaverryan SFCASTS guest 8 years ago

Thanks! Fixed at https://github.com/knpunive...

|

Dimitry K 8 years ago edited

If you try to add createdAt and updatedAt fields to an existing database table which already has data (thus you don't want to purge and recreate schema), you will run into those errors:


[PDOException]                                                                                                                   
  SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '0000-00-00 00:00:00' for column 'created_at' at row 1

and this:


 [Doctrine\DBAL\DBALException]                                                                                                     
  An exception occurred while executing 'ALTER TABLE building ADD created_at DATETIME NOT NULL, ADD updated_at DATETIME NOT NULL':  
  SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '0000-00-00 00:00:00' for column 'created_at' at row 1

To avoid this problem you can communicate to MySQL default value of those columns by declaring fields like this:


@ORM\Column(name="updated_at", type="datetime", options={"default"="1970-01-01 00:00:00"})

|

Victor SFCASTS Dimitry K 8 years ago

Hey Dimitry,

You're right, thank you for sharing this! There's also another solution: use "nullable=true" for those fields.

Cheers!

|

Dimitry K Victor 8 years ago

Hey Victor,

settings `nullable=true` is a good option as well (and shorter thus lazier). However I chose _not_ to use it and use "default" approach, because then I don't have to add to my codebase any special cases for when `createdAt` or `updatedAt` is null.

|

Victor SFCASTS Dimitry K 8 years ago

Hey Dimitry,

Agree! And there's another approach: if you use migrations, you can do some extra queries there and do not use `options={"default"="1970-01-01 00:00:00"} ` or `nullable=true` at all ;)

Cheers!

|

Pascal Q (pascal.) 8 years ago

The bundle introduced here is not available for Symfony 3.x, is it?

|

MolloKhan SFCASTS Pascal Q (pascal.) 8 years ago edited

Hey Pascal Q (pascal.)

Yes, it still works, you can use it safely. You can find more information here: https://symfony.com/doc/cur...

Cheers!

|

Symfony 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.3.3",
        "symfony/symfony": "~2.4", // v2.4.2
        "doctrine/orm": "~2.2,>=2.2.3", // v2.4.2
        "doctrine/doctrine-bundle": "~1.2", // v1.2.0
        "twig/extensions": "~1.0", // v1.0.1
        "symfony/assetic-bundle": "~2.3", // v2.3.0
        "symfony/swiftmailer-bundle": "~2.3", // v2.3.5
        "symfony/monolog-bundle": "~2.4", // v2.5.0
        "sensio/distribution-bundle": "~2.3", // v2.3.4
        "sensio/framework-extra-bundle": "~3.0", // v3.0.0
        "sensio/generator-bundle": "~2.3", // v2.3.4
        "incenteev/composer-parameter-handler": "~2.0", // v2.1.0
        "doctrine/doctrine-fixtures-bundle": "~2.2.0", // v2.2.0
        "ircmaxell/password-compat": "~1.0.3", // 1.0.3
        "phpunit/phpunit": "~4.1", // 4.1.0
        "stof/doctrine-extensions-bundle": "~1.1.0" // v1.1.0
    }
}

Previous Chapter

Next Chapter