Laravel accessors and mutators are custom, user defined methods that allow you to format Eloquent attributes. Accessors are used to format attributes when you retrieve them from the database, while mutators format the attributes before saving them to the database.
Tag: eloquent
Using Repository Pattern In Laravel 5 – Eloquent Relations And Eager Loading
Preface
Before we go to the main topic of the article, I’ll give you a short heads up for some design problems you may face. Recently one of my clients complained that some pages open very slowly. When I say very, I mean incredibly slow. So I’ve decided to debug that page and what I saw shocked me. Query section was showing that on that page was executed an staggering 16500+ queries !!
Continue reading Using Repository Pattern In Laravel 5 – Eloquent Relations And Eager Loading
Laravel: Model Observers
In the last tutorial I showed you how you can speed up a web application by caching database queries that are executed very often. However, there is a problem. Application will cache the resulted dataset, and in the future this dataset will be served. You need to tell your application to flush the cache every time when certain Model is updated. That way every time you edit, delete or add new Model item, old cache will be flushed, and query will be executed again. Afterwards, resulting new dataset will be cached and served until Model is updated once again. Continue reading Laravel: Model Observers
Laravel: Caching Database Queries
If your application runs a large number of queries very often, with time it will become very, very sluggish. Here Laravel caching comes handy. Laravel provides a simple mechanism for caching these queries using a very simple chained method call. Here is an example using Laravel’s Fluent Query Builder:
|
1 2 3 4 5 |
$users = DB::table('users') ->orderBy('latest_activity', 'desc') ->take(10) ->remember(60) ->get(); |
Of course, we can do the same thing using Eloquent:
|
1 2 3 4 |
$users = User::orderBy('latest_activity', 'desc') ->take(10) ->remember(60) ->get(); |
Behind the scene Laravel executes the query and then stores it along with the query result using the cache adapter, with an expiration time of 60 minutes. Running the same query again will result that cached query will be found, which means it will not be executed again, instead the results will be taken from the cache. Continue reading Laravel: Caching Database Queries