Skip to content

Commit 7e8d06d

Browse files
committed
Fix typos
1 parent 8d39ca4 commit 7e8d06d

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

content/blog/dbplyr-2-5-0/index.Rmd

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ library(dbplyr)
4747

4848
## Referring to tables in a schema
4949

50-
Historically, dbplyr has provided a bewildering array of options to specify a tableinside a schema inside a catalog:
50+
Historically, dbplyr has provided a bewildering array of options to specify a table inside a schema inside a catalog:
5151

5252
```{r}
5353
#| eval: false
@@ -75,7 +75,7 @@ con |> tbl(I("catalog_name.schema_name.table_name"))
7575
con |> tbl(I("schema_name.table_name"))
7676
```
7777

78-
`I()` is a base function, and you may be familiar from it from modelling, e.g. `lm(y ~ x + I(y * z))`. It performs a similar role for both dbplyr and modelling function: it tells the function to treat the argument as is, rather than quoting it in the case of dbplyr, or interpreting as an interaction in the case of `lm()`.
78+
`I()` is a base function, and you may be familiar with it from modelling, e.g. `lm(y ~ x + I(y * z))`. It performs a similar role for both dbplyr and modelling function: it tells the function to treat the argument as is, rather than quoting it in the case of dbplyr, or interpreting as an interaction in the case of `lm()`.
7979

8080
`I()` is dbplyr's preferred way of specifying nested table identifiers and we will eventually formally supersede and then one day deprecate the other options. However, because their usage is widespread, this process will be slow and gradual, and play out over multiple years; there's no need to make changes now.
8181

content/blog/dbplyr-2-5-0/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ photo:
1616
# one of: "deep-dive", "learn", "package", "programming", "roundup", or "other"
1717
categories: [package]
1818
tags: [dbplyr]
19-
rmd_hash: 0bccf87eecfb8f59
19+
rmd_hash: 058bf89f21b3fa2f
2020

2121
---
2222

@@ -53,7 +53,7 @@ This post focuses on the biggest change in dbplyr 2.5.0: improved syntax for tab
5353

5454
## Referring to tables in a schema
5555

56-
Historically, dbplyr has provided a bewildering array of options to specify a tableinside a schema inside a catalog:
56+
Historically, dbplyr has provided a bewildering array of options to specify a table inside a schema inside a catalog:
5757

5858
<div class="highlight">
5959

@@ -84,7 +84,7 @@ Many of these options were poorly supported (i.e. we would accidentally break t
8484

8585
</div>
8686

87-
[`I()`](https://rdrr.io/r/base/AsIs.html) is a base function, and you may be familiar from it from modelling, e.g. `lm(y ~ x + I(y * z))`. It performs a similar role for both dbplyr and modelling function: it tells the function to treat the argument as is, rather than quoting it in the case of dbplyr, or interpreting as an interaction in the case of [`lm()`](https://rdrr.io/r/stats/lm.html).
87+
[`I()`](https://rdrr.io/r/base/AsIs.html) is a base function, and you may be familiar with it from modelling, e.g. `lm(y ~ x + I(y * z))`. It performs a similar role for both dbplyr and modelling function: it tells the function to treat the argument as is, rather than quoting it in the case of dbplyr, or interpreting as an interaction in the case of [`lm()`](https://rdrr.io/r/stats/lm.html).
8888

8989
[`I()`](https://rdrr.io/r/base/AsIs.html) is dbplyr's preferred way of specifying nested table identifiers and we will eventually formally supersede and then one day deprecate the other options. However, because their usage is widespread, this process will be slow and gradual, and play out over multiple years; there's no need to make changes now.
9090

0 commit comments

Comments
 (0)