update_NAs now could be FALSE even if update_values is TRUE
Select rows-to-keep before transformation of updated values and NAs to avoid keeping rows from y that did not match in x but whose values got updated because update_values = TRUE
Solve issues #1 and #19
Change to data.table::merge.data.table syntax in all joins. It makes it easier to work with and consistent across different join types.
Remove previous lazy-loaded data.
possible_ids()
to identify what variables are suitable for uniquely identify the database.Add function is_id()
to check whether the table is uniquely identified by key variables
Add function freq_table()
as a substitute for janitor::tabyl. This makes it more convenient for users who do not have janitor installed.
Fix bug on by
argument when using “=” or “==”.
First Public release