TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Merge pull request #51506 from alonsogarciapablo/patch-1

Browse Source 
[ci skip] Update "Running EXPLAIN" section in the "Active Record Query Interface" guide
This commit is contained in:
fatkodima 2024-04-06 12:21:16 +03:00 committed by GitHub
commit 2e2a3c3fa4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
guides/source/active_record_querying.md
View File

@ -2610,13 +2610,13 @@ Running EXPLAIN
You can run [`explain`][] on a relation. EXPLAIN output varies for each database.
For example, running
For example, running:
```ruby
Customer.where(id: 1).joins(:orders).explain
```
may yield
may yield this for MySQL and MariaDB:
```sql
EXPLAIN SELECT `customers`.* FROM `customers` INNER JOIN `orders` ON `orders`.`customer_id` = `customers`.`id` WHERE `customers`.`id` = 1
@ -2636,11 +2636,9 @@ EXPLAIN SELECT `customers`.* FROM `customers` INNER JOIN `orders` ON `orders`.`c
2 rows in set (0.00 sec)
```
under MySQL and MariaDB.
Active Record performs a pretty printing that emulates that of the
corresponding database shell. So, the same query running with the
PostgreSQL adapter would yield instead
PostgreSQL adapter would yield instead:
```sql
EXPLAIN SELECT "customers".* FROM "customers" INNER JOIN "orders" ON "orders"."customer_id" = "customers"."id" WHERE "customers"."id" = $1 [["id", 1]]
@ -2658,7 +2656,7 @@ EXPLAIN SELECT "customers".* FROM "customers" INNER JOIN "orders" ON "orders"."c
Eager loading may trigger more than one query under the hood, and some queries
may need the results of previous ones. Because of that, `explain` actually
executes the query, and then asks for the query plans. For example,
executes the query, and then asks for the query plans. For example, running:
```ruby
Customer.where(id: 1).includes(:orders).explain