How Can I Set the Default Value of a Timestamp Column to the Current Timestamp with Laravel Migrations

Question

I would like to make a timestamp column with a default value of CURRENT TIMESTAMP ON UPDATE CURRENT TIMESTAMP using the Laravel Schema Builder Migrations  I have gone through the Laravel documentation several times  and I don t see how I can make that the default for a timestamp column   The timestamps   function makes the defaults 0000-00-00 00 00 for both columns that it makes

User · Answer

This doesn t work for a fact    table- gt timestamp  created at  - gt default  CURRENT TIMESTAMP      It doesn t remove the  default 0  that seems to come with selecting timestamp and it just appends the custom default   But we kind of need it without the quotes   Not everything that manipulates a DB is coming from Laravel4   That s his point   He wants custom defaults on certain columns like    table- gt timestamps  - gt default  CURRENT TIMESTAMP      I don t think it s possible with Laravel   I ve been searching for an hour now to see whether it s possible     Update  Paulos Freita s answer shows that it is possible  but the syntax isn t straightforward

User · Answer

Starting from Laravel 5 1 26  tagged on 2015-12-02  a useCurrent   modifier has been added   Schema  table  users   function   table         table- gt timestamp  created  - gt useCurrent          PR 10962  followed by commit 15c487fe  leaded to this addition   You may also want to read issues 3602 and 11518 which are of interest   Basically  MySQL 5 7  with default config  requires you to define either a default value or nullable for time fields

User · Answer

In laravel 7  to set current time use following   table- gt timestamp  column name  - gt useCurrent

User · Answer

I use the following customization in Laravel to   Default created at to the current timestamp Update the timestamp when the record is updated  First  I ll create a file  helpers php  in the root of Laravel and insert the following   lt  php  if   function exists  database driver          function database driver    string                connection   config  database default            return config  database connections      connection     driver             if   function exists  is database driver          function is database driver string  driver   bool               return  driver     database driver             In composer json  I ll insert the following into autoload  This allows composer to auto-discover helpers php       quot autoload quot              quot files quot                  quot app Services Uploads Processors processor functions php quot                quot app helpers php quot                    I use the following in my Laravel models          if  is database driver  sqlite                   table- gt timestamps              else                table- gt timestamp  created at  - gt default  DB  raw  CURRENT TIMESTAMP                  table- gt timestamp  updated at                   - gt default DB  raw  CURRENT TIMESTAMP ON UPDATE CURRENT TIMESTAMP                This allows my team to continue using sqlite for unit tests  ON UPDATE CURRENT TIMESTAMP is a MySQL shortcut and is not available in sqlite

User · Answer

This is how you do it  I have checked it and it works on my Laravel 4 2    table- gt timestamp  created at  - gt default DB  raw  CURRENT TIMESTAMP       Hope this helps

User · Answer

If your re looking to set the current datetime for a dateTime column  like i was when I googled   use this way  table- gt dateTime  signed when  - gt useCurrent

User · Answer

Given it s a raw expression  you should use DB  raw   to set CURRENT TIMESTAMP as a default value for a column    table- gt timestamp  created at  - gt default DB  raw  CURRENT TIMESTAMP       This works flawlessly on every database driver   New shortcut  As of Laravel 5 1 25  see PR 10962 and commit 15c487fe  you can use the new useCurrent   column modifier method to set the CURRENT TIMESTAMP as a default value for a column    table- gt timestamp  created at  - gt useCurrent      Back to the question  on MySQL you could also use the ON UPDATE clause through DB  raw      table- gt timestamp  updated at  - gt default DB  raw  CURRENT TIMESTAMP ON UPDATE CURRENT TIMESTAMP       Gotchas   MySQL Starting with MySQL 5 7  0000-00-00 00 00 00 is no longer considered a valid date  As documented at the Laravel 5 2 upgrade guide  all timestamp columns should receive a valid default value when you insert records into your database  You may use the useCurrent   column modifier  from Laravel 5 1 25 and above   in your migrations to default the timestamp columns to the current timestamps  or you may make the timestamps nullable   to allow null values  PostgreSQL  amp  Laravel 4 x In Laravel 4 x versions  the PostgreSQL driver was using the default database precision to store timestamp values  When using the CURRENT TIMESTAMP function on a column with a default precision  PostgreSQL generates a timestamp with the higher precision available  thus generating a timestamp with a fractional second part - see this SQL fiddle   This will led Carbon to fail parsing a timestamp since it won t be expecting microseconds being stored  To avoid this unexpected behavior breaking your application you have to explicitly give a zero precision to the CURRENT TIMESTAMP function as below    table- gt timestamp  created at  - gt default DB  raw  CURRENT TIMESTAMP 0        Since Laravel 5 0  timestamp   columns has been changed to use a default precision of zero which avoids this   Thanks to  andrewhl for pointing out this issue in the comments

User · Answer

As additional possibility for future googlers  I find it more useful to have null in the updated at column when the record is been created but has never been modified  It reduces the db size  ok  just a little  and its possible to see it at the first sight that the data has never been modified   As of this I use    table- gt timestamp  created at  - gt useCurrent     table- gt timestamp  updated at  - gt default DB  raw  NULL ON UPDATE CURRENT TIMESTAMP   - gt nullable       In Laravel 7 with mysql 8

User · Answer

Use Paulo Freitas suggestion instead     Until Laravel fixes this  you can run a standard database query after the Schema  create have been run       Schema  create  users   function  table            table- gt increments  id             table- gt string  email   255            table- gt string  given name   100            table- gt string  family name   100            table- gt timestamp  joined             table- gt enum  gender     male    female    unisex   - gt default  unisex             table- gt string  timezone   30 - gt default  UTC             table- gt text  about                DB  statement  ALTER TABLE   DB  getTablePrefix    users CHANGE joined joined TIMESTAMP DEFAULT CURRENT TIMESTAMP NOT NULL      It worked wonders for me

User · Answer

In Laravel 5 simply    table- gt timestamps      Adds created at and updated at columns    Documentation  http   laravel com docs 5 1 migrations creating-columns

User · Answer

To create both of the created at and updated at columns    t- gt timestamp  created at  - gt default DB  raw  CURRENT TIMESTAMP      t- gt timestamp  updated at  - gt default DB  raw  CURRENT TIMESTAMP on update CURRENT TIMESTAMP       You will need MySQL version    5 6 5 to have multiple columns with CURRENT TIMESTAMP

[php] How Can I Set the Default Value of a Timestamp Column to the Current Timestamp with Laravel Migrations?

Examples related to php

Examples related to mysql

Examples related to laravel

Examples related to laravel-4

Examples related to laravel-5