Laravel. Migrations. Adding a field

Question

I insert the field like this:

$table->timestamp('added_on')->default('CURRENT_TIMESTAMP'),

but in SQLite the default value is 'CURRENT_TIMESTAMP' and it does not work (does not replace with the current date). It is necessary that the field had the value CURRENT_TIMESTAMP, then it will work. Can this be done in Laravel?

Why not use $table->timestamps()? then you will have 2 fields: created_at and updated_at that laravel will handle automatically. And then if you absolutely want the field to be named added_on add an accesor. — Indra, Feb 05 '19 at 09:54

score 3 · Accepted Answer · edited Feb 05 '19 at 10:05

3

Try wrapping it in DB::raw so it's executed as a SQL function:

$table->timestamp('added_on')->default(\DB::raw('CURRENT_TIMESTAMP'));

Or you can use ->useCurrent(); Laravel helper like this :

$table->timestamp('added_on')->useCurrent();

edited Feb 05 '19 at 10:05

Maraboc

10,550
3
37
48

answered Feb 05 '19 at 09:36

Marcin

1,488
1
13
27

Thank you very much, I will try it – MyNick Feb 05 '19 at 11:32
Using useCurrent() solved the problem. You helped me a lot - I choose your answer as the best – MyNick Feb 05 '19 at 11:54

Laravel. Migrations. Adding a field

1 Answers1