


Detailed explanation of preloading optimization Laravel Model query related issues
Aug 12, 2017 am 11:44 AMThis article mainly introduces you to the relevant information on how to use preloading to optimize Laravel Model queries. The article introduces it in great detail through sample code. It has certain reference learning value for everyone's study or work. Friends who need it Let’s learn with the editor below.
Preface
This article mainly introduces the relevant content about using preloading to optimize Laravel Model query, and shares it for your reference and study. Not much to say, let’s take a look at the detailed introduction:
Introduction
Object-relational mapping (ORM) makes the database work becomes very simple. When database relationships are defined in an object-oriented manner, related model data can be easily queried and developers may not notice the underlying database calls.
The following will use some examples to further help you understand how to optimize queries.
Suppose you receive 100 objects from the database and each record has 1 associated model (i.e. belongsTo). Using the ORM by default will generate 101 queries; as follows:
1 2 3 4 5 6 7 |
|
We did not tell the Post model when querying that we also need all authors, so each time from a single A separate query occurs every time the Post model instance gets the author's name.
array_maps 100 queries occurred, plus the previous query, a total of 101 queries were generated.
Preloading
Next, if we plan to use associated model data, we can use preloading to The total number of 101 queries is reduced to 2 queries. Just tell the model what you need to load. As follows:
1 2 3 4 5 6 7 |
|
If you enable sql logs, you will see that the above preloading will only generate two queries:
1 2 |
|
If you have multiple related models, you can load them using an array:
1 |
|
Next we redefine the relationship as follows
1 2 3 |
|
Consider the following scenario: Get the profile of the author of a published article.
1 2 3 4 5 6 7 8 9 |
|
Assume that the above App\Post::with('author')->get()
has 100 records, how many records will be generated What about the query?
By optimizing preloading, we can avoid extra queries in nested relationships.
1 2 3 4 5 6 7 |
|
You can open your sql log to see the corresponding three queries.
1 2 3 |
|
Lazy loading
Sometimes you may just need to collect associations based on conditions model. In this case you can lazily call other queries for related data:
1 2 3 4 5 6 7 |
|
Looking at your sql logs, you see a total of three queries, but only one that calls $ It will only be displayed when posts->load().
Conclusion
Hopefully you know more about loading models and understand how it works on a deeper level . The documentation related to Laravel is already very comprehensive. I hope the additional practical exercises can help you become more confident in optimizing relational queries.
Summary
The original text is translated from eloquent-eager-loading, simplifying the previous part of constructing data.
The above is the detailed content of Detailed explanation of preloading optimization Laravel Model query related issues. For more information, please follow other related articles on the PHP Chinese website!

Hot Article

Hot tools Tags

Hot Article

Hot Article Tags

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

PHP vs. Flutter: The best choice for mobile development

How to use object-relational mapping (ORM) in PHP to simplify database operations?

Analysis of the advantages and disadvantages of PHP unit testing tools

Comparison of the latest versions of Laravel and CodeIgniter

How do the data processing capabilities in Laravel and CodeIgniter compare?

C++ program optimization: time complexity reduction techniques

PHP code unit testing and integration testing
