Level 41
Just migrate your database, and add $dates property to your Model.
protected $dates = ['custom_created_at_field', 'custom_updated_at_field'];
Jun 17, 2015
3
Level 2
Why are CREATED_AT and UPDATED_AT Constants in the Eloquent Model class?
I'm in the process of migrating an existing application over to laravel and I ran into problems with the created_at and updated_at tables. The database that I'm currently using already has these fields, but they're named differently. I can override $primaryKey, but not the timestamp fields. Is there a purpose for this?
here's the code in Illuminate\Database\Eloquent\Model.php
/**
* The name of the "created at" column.
*
* @var string
*/
const CREATED_AT = 'created_at';
/**
* The name of the "updated at" column.
*
* @var string
*/
const UPDATED_AT = 'updated_at';
Level 4
Either migrate the columns to suit your needs or extend the Model class to override for instance the getCreatedAtColumn method, see http://laravel.com/api/5.1/Illuminate/Database/Eloquent/Model.html#method_getCreatedAtColumn
Level 3
Is this what you mean?
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:
<?php
namespace App;
use Illuminate\Database\Eloquent\Model;
class Flight extends Model
{
/**
* Indicates if the model should be timestamped.
*
* @var bool
*/
public $timestamps = false;
}
http://laravel.com/docs/5.1/eloquent#eloquent-model-conventions
1 like
Please or to participate in this conversation.