Description Usage Arguments Details Value Examples
See the number of valid and invalid checks either by rule or by record.
1 2 |
x |
|
by |
either by "rule" or by "record" |
... |
not used |
The result of a confront()
on a db tbl
results in a lazy squery. That
is it builds a query without executing it. To store the result in the database
use compute()
or values()
.
A dbplyr::tbl_dbi()
object that represents the aggregation query
(to be executed) on the database.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | income <- data.frame(id = 1:2, age=c(12,35), salary = c(1000,NA))
con <- dbplyr::src_memdb()
tbl_income <- dplyr::copy_to(con, income, overwrite=TRUE)
print(tbl_income)
# Let's define a rule set and confront the table with it:
rules <- validator( is_adult = age >= 18
, has_income = salary > 0
)
# and confront!
# in general with a db table it is handy to use a key
cf <- confront(tbl_income, rules, key="id")
aggregate(cf, by = "rule")
aggregate(cf, by = "record")
# to tweak performance of the db query the following options are available
# 1) store validation result in db
cf <- confront(tbl_income, rules, key="id", compute = TRUE)
# or identical
cf <- confront(tbl_income, rules, key="id")
cf <- compute(cf)
# 2) Store the validation sparsely
cf_sparse <- confront(tbl_income, rules, key="id", sparse=TRUE )
show_query(cf_sparse)
values(cf_sparse, type="tbl")
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.