dm (version 0.2.8)

enum_pk_candidates: Primary key candidate

Description

[Questioning]

enum_pk_candidates() checks for each column of a table if the column contains only unique values, and is thus a suitable candidate for a primary key of the table.

dm_enum_pk_candidates() performs these checks for a table in a dm object.

Usage

enum_pk_candidates(table, ...)

dm_enum_pk_candidates(dm, table, ...)

Arguments

table

A table in the dm.

...

These dots are for future extensions and must be empty.

dm

A dm object.

Value

A tibble with the following columns:

columns

columns of table,

candidate

boolean: are these columns a candidate for a primary key,

why

if not a candidate for a primary key column, explanation for this.

Life cycle

These functions are marked "questioning" because we are not yet sure about the interface, in particular if we need both dm_enum...() and enum...() variants. Changing the interface later seems harmless because these functions are most likely used interactively.

See Also

Other primary key functions: dm_add_pk(), dm_get_all_pks(), dm_has_pk(), dm_rm_pk()

Examples

Run this code
# NOT RUN {
nycflights13::flights %>%
  enum_pk_candidates()
# }
# NOT RUN {
dm_nycflights13() %>%
  dm_enum_pk_candidates(airports)
# }

Run the code above in your browser using DataLab