Laravel Unknown Column updated at

Question

I ve just started with Laravel and I get the following error       Unknown column  updated at  insert into gebruikers  naam  wachtwoord    updated at  created at    I know the error is from the timestamp column when you migrate a table but I m not using the updated at field  I used to use it when I followed the Laravel tutorial but now that I am making  or attempting to make  my own stuff  I get this error even though I don t use timestamps  I can t seem to find the place where it s being used  This is the code   Controller  public function created         if   User  isValidRegister Input  all               return Redirect  back  - gt withInput  - gt withErrors User   errors                 Register the new user or whatever       user   new User       user- gt naam   Input  get  naam         user- gt wachtwoord   Hash  make Input  get  password          user- gt save         return Redirect  to   users        Route  Route  get  created    UserController created      Model  public static  rules register          naam    gt   unique gebruikers naam      public static  errors  protected  table    gebruikers    public static function isValidRegister  data         validation   Validator  make  data  static   rules register        if   validation- gt passes              return true             static   errors    validation- gt messages         return false      I must be forgetting something    What am I doing wrong here

User · Answer

Nice answer by Alex and Sameer  but maybe just additional info on why is necessary to put  public  timestamps   false    Timestamps are nicely explained on official Laravel page      By default  Eloquent expects created at and updated at columns to exist on your  tables  If you do not wish to have these columns automatically managed by  Eloquent  set the   timestamps property on your model to false

User · Answer

In the model  write the below code   public  timestamps   false    This would work   Explanation   By default laravel will expect created at  amp  updated at column in your table  By making it to false it will override the default setting

User · Answer

Setting timestamps to false means you are going to lose both created at and updated at whereas you could set both of the keys in your model  Case 1  You have created at column but not update at you could simply set updated at to false in your model class ABC extends Model    const UPDATED AT   null   Case 2  You have both created at and updated at columns but with different column names You could simply do  class ABC extends Model    const CREATED AT    name of created at column   const UPDATED AT    name of updated at column    Finally ignoring timestamps completely  class ABC extends Model    public  timestamps   false

User · Answer

For those who are using laravel 5 or above must use public modifier other wise it will throw an exception   Access level to App yourModelName   timestamps must be public  as in class Illuminate Database Eloquent Model   public  timestamps   false

[php] Laravel Unknown Column 'updated_at'

Examples related to php

Examples related to mysql

Examples related to laravel

Examples related to laravel-migrations