Timestamps (updated_at, created_at) are null in Laravel 5

Question

I have a problem with updated_at, created_at fields in Laravel 5.

Here is my migration:

Schema::create('lots', function (Blueprint $table) {
    $table->increments('id');
    $table->integer('lot');
    $table->integer('is_active');
    $table->timestamps();
});

But when I insert some data into this table, updated_at and created_at fields are null. How make them auto-complete with current timestamps?

I insert data like this:

\DB::table('admin_lots')->insert([
    'lot' => $request->cycle_lot,
    'is_active' => '1',
]);

Thanks.

Please show us how do you insert data. – Alexey Mezenin May 03 '16 at 07:33 — Alexey Mezenin, May 03 '16 at 07:33

score 14 · Answer 1 · edited Jan 06 '23 at 11:18

14

You have to use the create method instead of the insert method in Laravel.

The create method automatically adds timestamps for created_at and updated_at fields:

// GOOD:
User::create(array(
    'name' => 'John'
));

On the contrary, the insert method bypasses Eloquent, (it uses the query builder) and does not update updated_at/created_at columns!

// BAD:
User::insert([
    'name' => '[[ test name ]]',
]);

dd(
    User::where(['name' => '[[ test name ]]'])->first()->create_date
);

edited Jan 06 '23 at 11:18

raveren

17,799
12
70
83

answered Jan 22 '19 at 06:02

Rakesh Nandi

141
1
5

3

Perfect, i was using `insert` instead of `create` method. – Sukhchain Singh Oct 07 '19 at 06:01
In this case i am using insert() because multiple insert.. what i have to do? – void Mar 19 '20 at 11:54

score 12 · Answer 2 · edited May 23 '17 at 12:08

12

You probably do not use Eloquent when inserting data, in this case you should add timestamps manually.

If you do not want to do this, but you still need filled timestamps, use this hack:

$table->timestamp('created_at')->default(\DB::raw('CURRENT_TIMESTAMP'));
$table->timestamp('updated_at')->default(\DB::raw('CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP'));

Update

Based on your updated code, here's another solution:

\DB::table('admin_lots')->insert([
                'lot'   => $request->cycle_lot,
                'is_active'     => '1',
                'created_at' = \Carbon\Carbon::now()->toDateTimeString(),
                'updated_at' = \Carbon\Carbon::now()->toDateTimeString()
            ]);

edited May 23 '17 at 12:08

Community

1
1

answered May 03 '16 at 07:33

Alexey Mezenin

158,981
26
290
279

Updated post on how I insert data. Thanks for your answer, will try it now. – el valuta May 03 '16 at 07:45
Added another solution for manual timestamp creation based on your code. – Alexey Mezenin May 03 '16 at 07:48
1

It seems like the a use case for eloquent to be honest. The straight db insert is a bad practice in this case. – overburn May 03 '16 at 07:49
Thanks! Both solutions work for me, but 1st one is better. Thanks a lot! – el valuta May 03 '16 at 07:50
@overburn, I've posted first solution when OP didn't provide any code and I wrote it's a kind of **hack**. – Alexey Mezenin May 03 '16 at 07:51
1

True. But that hack is bound to give somebody else headaches down the road. – overburn May 03 '16 at 07:52

Yevgeniy Afanasyev · Answer 3 · 2017-11-26T21:20:39.663

8

Check if your model has this line.

public $timestamps = false;

If it has, delete it.

edited Nov 26 '17 at 21:20

answered Jun 21 '17 at 05:34

Yevgeniy Afanasyev

37,872
26
173
191

1

If the line is in a parent class, you have to add: public $timestamps = true; – Tama Jan 21 '20 at 21:24

score 5 · Answer 4 · answered May 03 '16 at 07:48

5

When you instert data directly, Laravel won't know about your timestamps. You can either set the timestamps manually in the insert statement, or switch to using Eloquent models , which handle many things out of the box for you, including timestamps. It's also way easier to maintain than straight queries, where applicable.

Eloquent ORM

answered May 03 '16 at 07:48

overburn

1,194
9
27

3

I really recommend using Eloquent in this case. Anything else will result in unnecessary difficult maintainable non-laravel way code. – Pᴇʜ May 03 '16 at 08:40

score 1 · Answer 5 · edited Jun 25 '20 at 09:07

You need to use Laravel's awesome Eloquent feature to make timestamps written to the Database automatically...

As by seeing your example the code for eloquent will go something like this:

$lot_inputs = array(
    'lot' => $request->cycle_lot,
    'is_active' => 1
);
$new_lot = Lot::create($lot_inputs);

Please note that you should have the Model for the table = 'lots' (and it must extend Eloquent) so that you can easily use Eloquent methods and its properties...

It would be great if you use Eloquent ORM as much as possible so that if in future you want to change your DB technology then you won't need to specify the written eloquent queries again (e.g: the conversion of query to different DB languages is automatically done by Eloquent)

Thanks I hope this will help you to resolve your issue..!!

Timestamps (updated_at, created_at) are null in Laravel 5

5 Answers5

Linked