Database/model field-name convention in Laravel?

php laravel naming-conventions datamodel
preyz picture preyz · Jan 28, 2014 · Viewed 8.5k times · Source

I understand that camel case is the usual convention, as per http://forums.laravel.io/viewtopic.php?id=8857

However, Laravel is using created_at and updated_at for timestamp fields.

I'm confused as what would be the best naming convention for field-names in the database? If camel cased, can I then switch created_at to createdAt, or should I use camel case for own fields and snake case for the timestamps?

It doesn't seem clear to me. Maybe Laravel wants me to use snake case all the way, like first_name in the database and $first_name in the PHP code, rather than firstName in the database, and $firstName in the code?

I hope someone can clarify...

Answer

Alexandre Butynski picture Alexandre Butynski · Jan 28, 2014

Snake case is the convention for database fields and model attributes.

You can see it in the getter and setter (http://laravel.com/docs/eloquent#accessors-and-mutators) or relationships sections (http://laravel.com/docs/eloquent#relationships) in the documentation.

Related questions

Laravel Migrations Naming Convention

Is there a naming convention or guide that one should follow while naming Laravel migrations or should the name only be descriptive enough ? Also, suppose you are adding 12 columns to modify a table then in such a case the migration …

Read More
How Do I Get the Query Builder to Output Its Raw SQL Query as a String?

Given the following code: DB::table('users')->get(); I want to get the raw SQL query string that the database query builder above will generate. In this example, it would be SELECT * FROM users. How do I do …

Read More
How to Create Multiple Where Clause Query Using Laravel Eloquent?

I'm using the Laravel Eloquent query builder and I have a query where I want a WHERE clause on multiple conditions. It works, but it's not elegant. Example: $results = User::where('this', '=', 1) ->where('that', '=', 1) …

Read More