Description Usage Arguments Databases Examples
This is a generic function which gives more details about an object than
print
, and is more focussed on human readable output than
str
.
1 2 3 | explain(x, ...)
show_query(x)
|
x |
An object to explain |
... |
Other parameters possibly used by generic |
Explaining a tbl_sql
will run the SQL EXPLAIN
command which
will describe the query plan. This requires a little bit of knowledge about
how EXPLAIN
works for your database, but is very useful for
diagnosing performance problems.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | if (require("RSQLite") && has_lahman("sqlite")) {
lahman_s <- lahman_sqlite()
batting <- tbl(lahman_s, "Batting")
batting %>% show_query()
batting %>% explain()
# The batting database has indices on all ID variables:
# SQLite automatically picks the most restrictive index
batting %>% filter(lgID == "NL" & yearID == 2000L) %>% explain()
# OR's will use multiple indexes
batting %>% filter(lgID == "NL" | yearID == 2000) %>% explain()
# Joins will use indexes in both tables
teams <- tbl(lahman_s, "Teams")
batting %>% left_join(teams, c("yearID", "teamID")) %>% explain()
}
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.