spec_arrow_create_table_arrow
Source:R/spec-arrow-create-table-arrow.R
spec_arrow_create_table_arrow.Rdspec_arrow_create_table_arrow
Failure modes
If the table exists, an error is raised; the remote table remains unchanged.
An error is raised when calling this method for a closed
or invalid connection.
An error is also raised
if name cannot be processed with DBI::dbQuoteIdentifier() or
if this results in a non-scalar.
Invalid values for the temporary argument
(non-scalars,
unsupported data types,
NA,
incompatible values,
duplicate names)
also raise an error.
Additional arguments
The following arguments are not part of the dbCreateTableArrow() generic
(to improve compatibility across backends)
but are part of the DBI specification:
temporary(default:FALSE)
They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage.
Specification
The name argument is processed as follows,
to support databases that allow non-syntactic names for their objects:
If an unquoted table name as string:
dbCreateTableArrow()will do the quoting, perhaps by callingdbQuoteIdentifier(conn, x = name)If the result of a call to
DBI::dbQuoteIdentifier(): no more quoting is done
The value argument can be:
a data frame,
a nanoarrow array
a nanoarrow array stream (which will still contain the data after the call)
a nanoarrow schema
If the temporary argument is TRUE, the table is not available in a
second connection and is gone after reconnecting.
Not all backends support this argument.
A regular, non-temporary table is visible in a second connection,
in a pre-existing connection,
and after reconnecting to the database.
SQL keywords can be used freely in table names, column names, and data. Quotes, commas, and spaces can also be used for table names and column names, if the database supports non-syntactic identifiers.