Level 1
Well, that's quite late to answer, I believe.
Anyways, just in case anyone gets this error, you have to write timestamp instead of timestamps.
11 likes
Aug 27, 2016
4
Level 13
nullable() > Call to a member function useCurrent() on null
I get error when try a migration on Laravel 5.3 (on 5.2 work this code)
local.ERROR: Symfony\Component\Debug\Exception\FatalThrowableError: Call to a member function useCurrent() on null in /home/vagrant/setdart/database/migrations/2016_07_02_081018_create_migration_corrections_table.php:26
On code
$table->timestamps('created_at')->useCurrent();
Also try
$table->timestamps('created_at')->nullable(true)->useCurrent();
It's a bug? A mistake?
Level 1
@o_voloshin Thank you very much your answer help me solve the error.
Level 6
Hello abkrim
Use this :
$table->timestamps();
this create two fields creared_at and updated_at and its add time automatically while create or update you dont need to give it manually. Thanks.
Level 13
@ankitparmar372 5 years ago.
Also is already answered.
Please or to participate in this conversation.