Upsert rows (v2 contract; errors in v1) — entropia

The write API is designed for v2 and shipped in v1 as stubs that error with class entropia_error_write_disabled. Every call aborts immediately with guidance: v1 is read-only, and write support arrives in v2 via entropia_connect(path, write = TRUE).

Usage

entropia_upsert(con, table, data, by, dry_run = TRUE)

Arguments

con: An EntropIA connection.
table: Table name.
data: Data to insert or update.
by: Column name(s) identifying the conflict key (required in v2).
dry_run: Logical. In v2, validate without writing when TRUE (default).

Value

Never returns: aborts with entropia_error_write_disabled.

Details

In v2, entropia_upsert() implements upserts as INSERT ... ON CONFLICT(id) DO UPDATE — never INSERT OR REPLACE, whose rowid reassignment would break the contentless FTS5 tables.

Examples

con <- entropia_connect(system.file("extdata", "entropia-example.sqlite",
  package = "entropiaR"
))
err <- tryCatch(entropia_upsert(con, "items", data.frame(id = "x"), by = "id"),
  error = identity
)
class(err) # "entropia_error_write_disabled"
#> [1] "entropia_error_write_disabled" "rlang_error"                  
#> [3] "error"                         "condition"                    
conditionMessage(err)
#> [1] "\033[1m\033[22m`entropia_upsert()` is not available in entropiaR v1.\n\033[36mℹ\033[39m v1 is read-only: the database may be live in EntropIA (WAL) and is protected\n  by 81 sync/activity triggers.\n\033[36mℹ\033[39m Write support ships in v2, where you open the database for writing with\n  `entropia_connect()` (`path`, `write = TRUE`).\n\033[36mℹ\033[39m The v2 write design is documented in \033[34mvignettes/administration.Rmd\033[39m."
entropia_disconnect(con)