make.db.names-methods {RSQLite} | R Documentation |
These methods are straight-forward implementations of the corresponding generic functions.
any SQLite object (e.g., SQLiteDriver
).
a character vector of R/S-Plus identifiers (symbols) from which we need to make SQL identifiers.
a character vector of SQL identifiers we want to check against keywords from the DBMS.
logical describing whether the resulting set of SQL names should
be unique. Its default is TRUE
. Following the SQL 92
standard, uniqueness of SQL identifiers is determined regardless
of whether letters are upper or lower case.
logical describing whether SQL keywords should be allowed in the
resulting set of SQL names. Its default is TRUE
a character vector with SQL keywords, namely
.SQL92Keywords
defined in the DBI
package.
a character string specifying whether to make the comparison
as lower case, upper case, or any of the two.
it defaults to any
.
currently not used.
The set of SQL keywords is stored in the character vector
.SQL92Keywords
and reflects the SQL ANSI/ISO standard as
documented in "X/Open SQL and RDA", 1994, ISBN 1-872630-68-8.
Users can easily override or update this vector.
SQLite does not add keywords to the SQL 92 standard.
See the Database Interface definition document
DBI.pdf
in the base directory of this package
or http://stat.bell-labs.com/RS-DBI.
SQLite
,
dbReadTable
,
dbWriteTable
,
dbExistsTable
,
dbRemoveTable
,
dbListTables
.
## Not run: # This example shows how we could export a bunch of data.frames # into tables on a remote database. con <- dbConnect("SQLite", dbname = "sqlite.db") export <- c("trantime.email", "trantime.print", "round.trip.time.email") tabs <- make.db.names(con, export, unique = TRUE, allow.keywords = TRUE) for(i in seq_along(export) ) dbWriteTable(con, name = tabs[i], get(export[i])) ## End(Not run)