returning
option for
dbxInsert
and dbxUpsert
for SQLite 3.35.0+ and
SQL Serverreturning
option for
dbxInsert
and dbxUpsert
for MariaDB 10.5+dbxUpsert
for SQL ServerSQL
with returning
optiontransaction
option to dbxUpdate
where_cols
ordering different than
data framedbxExecute
functiondbxSelect
skip_existing
option to
dbxUpsert
batch_size
option skipping partial
batchesdbxUpdate
transactionvariables
to dbxConnect
connect_timeout
, sslcert
,
sslkey
, and sslcrl
for RPostgreSQLdbx_logging
over dbx_verbose
dbxUpsert
sslmode
and sslrootcert
for
RPostgreSQLhms
objectsBreaking
The dbxInsert
and dbxUpsert
functions
no longer return a data frame by default. For MySQL and SQLite, the data
frame was just the records
argument. For Postgres, if you
use auto-incrementing primary keys, the data frame contained ids of the
newly inserted/upserted records. To get the ids, pass name of the column
as the returning
argument:
dbxInsert(db, table, records, returning=c("id"))
timestamp without time zone
columns in Postgres are
now stored in UTC instead of local time by default. This does not affect
timestamp with time zone
columns. To keep the previous
behavior, use:
dbxConnect(adapter="postgres", storage_tz=Sys.timezone(), ...)