DBI/0000755000176200001440000000000014563656122010662 5ustar liggesusersDBI/NAMESPACE0000644000176200001440000000632014552712323012074 0ustar liggesusers# Generated by roxygen2: do not edit by hand S3method("[",SQL) S3method("[[",SQL) S3method(toString,Id) export(.SQL92Keywords) export(ANSI) export(Id) export(SQL) export(SQLKeywords) export(dbAppendTable) export(dbAppendTableArrow) export(dbBegin) export(dbBind) export(dbBindArrow) export(dbBreak) export(dbCallProc) export(dbCanConnect) export(dbClearResult) export(dbColumnInfo) export(dbCommit) export(dbConnect) export(dbCreateTable) export(dbCreateTableArrow) export(dbDataType) export(dbDisconnect) export(dbDriver) export(dbExecute) export(dbExistsTable) export(dbFetch) export(dbFetchArrow) export(dbFetchArrowChunk) export(dbGetConnectArgs) export(dbGetDBIVersion) export(dbGetException) export(dbGetInfo) export(dbGetQuery) export(dbGetQueryArrow) export(dbGetRowCount) export(dbGetRowsAffected) export(dbGetStatement) export(dbHasCompleted) export(dbIsReadOnly) export(dbIsValid) export(dbListConnections) export(dbListFields) export(dbListObjects) export(dbListResults) export(dbListTables) export(dbQuoteIdentifier) export(dbQuoteLiteral) export(dbQuoteString) export(dbReadTable) export(dbReadTableArrow) export(dbRemoveTable) export(dbRollback) export(dbSendQuery) export(dbSendQueryArrow) export(dbSendStatement) export(dbSetDataMappings) export(dbUnloadDriver) export(dbUnquoteIdentifier) export(dbWithTransaction) export(dbWriteTable) export(dbWriteTableArrow) export(fetch) export(isSQLKeyword) export(isSQLKeyword.default) export(make.db.names) export(make.db.names.default) export(sqlAppendTable) export(sqlAppendTableTemplate) export(sqlColumnToRownames) export(sqlCommentSpec) export(sqlCreateTable) export(sqlData) export(sqlInterpolate) export(sqlParseVariables) export(sqlParseVariablesImpl) export(sqlQuoteSpec) export(sqlRownamesToColumn) exportClasses(DBIConnection) exportClasses(DBIConnector) exportClasses(DBIDriver) exportClasses(DBIObject) exportClasses(DBIResult) exportClasses(DBIResultArrow) exportClasses(DBIResultArrowDefault) exportClasses(SQL) exportMethods(dbAppendTable) exportMethods(dbAppendTableArrow) exportMethods(dbBind) exportMethods(dbBindArrow) exportMethods(dbCanConnect) exportMethods(dbClearResult) exportMethods(dbConnect) exportMethods(dbCreateTable) exportMethods(dbCreateTableArrow) exportMethods(dbDataType) exportMethods(dbExecute) exportMethods(dbExistsTable) exportMethods(dbFetch) exportMethods(dbFetchArrow) exportMethods(dbFetchArrowChunk) exportMethods(dbGetConnectArgs) exportMethods(dbGetInfo) exportMethods(dbGetQuery) exportMethods(dbGetQueryArrow) exportMethods(dbGetRowCount) exportMethods(dbGetRowsAffected) exportMethods(dbGetStatement) exportMethods(dbHasCompleted) exportMethods(dbIsValid) exportMethods(dbListFields) exportMethods(dbListObjects) exportMethods(dbQuoteIdentifier) exportMethods(dbQuoteLiteral) exportMethods(dbQuoteString) exportMethods(dbReadTable) exportMethods(dbReadTableArrow) exportMethods(dbRemoveTable) exportMethods(dbSendQueryArrow) exportMethods(dbSendStatement) exportMethods(dbUnquoteIdentifier) exportMethods(dbWithTransaction) exportMethods(dbWriteTable) exportMethods(dbWriteTableArrow) exportMethods(show) exportMethods(sqlAppendTable) exportMethods(sqlCreateTable) exportMethods(sqlData) exportMethods(sqlInterpolate) exportMethods(sqlParseVariables) import(methods) DBI/.Rinstignore0000644000176200001440000000002514350241735013155 0ustar liggesusersinst/doc/figure1.pdf DBI/README.md0000644000176200001440000001372014552712323012136 0ustar liggesusers # DBI [![Lifecycle: stable](https://img.shields.io/badge/lifecycle-stable-brightgreen.svg)](https://lifecycle.r-lib.org/articles/stages.html#stable) [![rcc](https://github.com/r-dbi/DBI/workflows/rcc/badge.svg)](https://github.com/r-dbi/DBI/actions) [![Coverage Status](https://codecov.io/gh/r-dbi/DBI/branch/main/graph/badge.svg)](https://app.codecov.io/github/r-dbi/DBI?branch=main) [![CRAN_Status_Badge](https://www.r-pkg.org/badges/version/DBI)](https://cran.r-project.org/package=DBI) [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/1882/badge)](https://bestpractices.coreinfrastructure.org/projects/1882) The DBI package helps connecting R to database management systems (DBMS). DBI separates the connectivity to the DBMS into a “front-end” and a “back-end”. The package defines an interface that is implemented by *DBI backends* such as: - [RPostgres](https://rpostgres.r-dbi.org), - [RMariaDB](https://rmariadb.r-dbi.org), - [RSQLite](https://rsqlite.r-dbi.org), - [odbc](https://github.com/r-dbi/odbc), - [bigrquery](https://github.com/r-dbi/bigrquery), and many more, see the [list of backends](https://github.com/r-dbi/backends#readme). R scripts and packages use DBI to access various databases through their DBI backends. The interface defines a small set of classes and methods similar in spirit to Perl’s [DBI](https://dbi.perl.org/), Java’s JDBC, Python’s [DB-API](https://www.python.org/dev/peps/pep-0249/), and Microsoft’s [ODBC](https://en.wikipedia.org/wiki/ODBC). It supports the following operations: - connect/disconnect to the DBMS - create and execute statements in the DBMS - extract results/output from statements - error/exception handling - information (meta-data) from database objects - transaction management (optional) ## Installation Most users who want to access a database do not need to install DBI directly. It will be installed automatically when you install one of the database backends: - [RPostgres](https://rpostgres.r-dbi.org) for PostgreSQL, - [RMariaDB](https://rmariadb.r-dbi.org) for MariaDB or MySQL, - [RSQLite](https://rsqlite.r-dbi.org) for SQLite, - [odbc](https://github.com/r-dbi/odbc) for databases that you can access via [ODBC](https://en.wikipedia.org/wiki/Open_Database_Connectivity), - [bigrquery](https://github.com/r-dbi/bigrquery), - … . You can install the released version of DBI from [CRAN](https://CRAN.R-project.org) with: ``` r install.packages("DBI") ``` And the development version from [GitHub](https://github.com/) with: ``` r # install.packages("devtools") devtools::install_github("r-dbi/DBI") ``` ## Example The following example illustrates some of the DBI capabilities: ``` r library(DBI) # Create an ephemeral in-memory RSQLite database con <- dbConnect(RSQLite::SQLite(), dbname = ":memory:") dbListTables(con) #> character(0) dbWriteTable(con, "mtcars", mtcars) dbListTables(con) #> [1] "mtcars" dbListFields(con, "mtcars") #> [1] "mpg" "cyl" "disp" "hp" "drat" "wt" "qsec" "vs" "am" "gear" #> [11] "carb" dbReadTable(con, "mtcars") #> mpg cyl disp hp drat wt qsec vs am gear carb #> 1 21.0 6 160.0 110 3.90 2.620 16.46 0 1 4 4 #> 2 21.0 6 160.0 110 3.90 2.875 17.02 0 1 4 4 #> 3 22.8 4 108.0 93 3.85 2.320 18.61 1 1 4 1 #> 4 21.4 6 258.0 110 3.08 3.215 19.44 1 0 3 1 #> 5 18.7 8 360.0 175 3.15 3.440 17.02 0 0 3 2 #> 6 18.1 6 225.0 105 2.76 3.460 20.22 1 0 3 1 #> 7 14.3 8 360.0 245 3.21 3.570 15.84 0 0 3 4 #> 8 24.4 4 146.7 62 3.69 3.190 20.00 1 0 4 2 #> 9 22.8 4 140.8 95 3.92 3.150 22.90 1 0 4 2 #> [ reached 'max' / getOption("max.print") -- omitted 23 rows ] # You can fetch all results: res <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4") dbFetch(res) #> mpg cyl disp hp drat wt qsec vs am gear carb #> 1 22.8 4 108.0 93 3.85 2.320 18.61 1 1 4 1 #> 2 24.4 4 146.7 62 3.69 3.190 20.00 1 0 4 2 #> 3 22.8 4 140.8 95 3.92 3.150 22.90 1 0 4 2 #> 4 32.4 4 78.7 66 4.08 2.200 19.47 1 1 4 1 #> 5 30.4 4 75.7 52 4.93 1.615 18.52 1 1 4 2 #> 6 33.9 4 71.1 65 4.22 1.835 19.90 1 1 4 1 #> 7 21.5 4 120.1 97 3.70 2.465 20.01 1 0 3 1 #> 8 27.3 4 79.0 66 4.08 1.935 18.90 1 1 4 1 #> 9 26.0 4 120.3 91 4.43 2.140 16.70 0 1 5 2 #> [ reached 'max' / getOption("max.print") -- omitted 2 rows ] dbClearResult(res) # Or a chunk at a time res <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4") while (!dbHasCompleted(res)) { chunk <- dbFetch(res, n = 5) print(nrow(chunk)) } #> [1] 5 #> [1] 5 #> [1] 1 dbClearResult(res) dbDisconnect(con) ``` ## Class structure There are four main DBI classes. Three which are each extended by individual database backends: - `DBIObject`: a common base class for all DBI. - `DBIDriver`: a base class representing overall DBMS properties. Typically generator functions instantiate the driver objects like `RSQLite()`, `RPostgreSQL()`, `RMySQL()` etc. - `DBIConnection`: represents a connection to a specific database - `DBIResult`: the result of a DBMS query or statement. All classes are *virtual*: they cannot be instantiated directly and instead must be subclassed. ## Further Reading - [Databases using R](https://db.rstudio.com/) describes the tools and best practices in this ecosystem. - The [DBI project site](https://www.r-dbi.org/) hosts a blog where recent developments are presented. - [A history of DBI](https://dbi.r-dbi.org/articles/DBI-history.html) by David James, the driving force behind the development of DBI, and many of the packages that implement it. ------------------------------------------------------------------------ Please note that the *DBI* project is released with a [Contributor Code of Conduct](https://dbi.r-dbi.org/CODE_OF_CONDUCT.html). By contributing to this project, you agree to abide by its terms. DBI/man/0000755000176200001440000000000014552712323011427 5ustar liggesusersDBI/man/dbQuoteLiteral.Rd0000644000176200001440000000562714552712323014650 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbQuoteLiteral.R \name{dbQuoteLiteral} \alias{dbQuoteLiteral} \title{Quote literal values} \usage{ dbQuoteLiteral(conn, x, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{x}{A vector to quote as string.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbQuoteLiteral()} returns an object that can be coerced to \link{character}, of the same length as the input. For an empty integer, numeric, character, logical, date, time, or blob vector, this function returns a length-0 object. When passing the returned object again to \code{dbQuoteLiteral()} as \code{x} argument, it is returned unchanged. Passing objects of class \link{SQL} should also return them unchanged. (For backends it may be most convenient to return \link{SQL} objects to achieve this behavior, but this is not required.) } \description{ Call these methods to generate a string that is suitable for use in a query as a literal value of the correct type, to make sure that you generate valid SQL and protect against SQL injection attacks. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbQuoteLiteral")} } \section{Failure modes}{ Passing a list for the \code{x} argument raises an error. } \section{Specification}{ The returned expression can be used in a \verb{SELECT ...} query, and the value of \code{dbGetQuery(paste0("SELECT ", dbQuoteLiteral(x)))[[1]]} must be equal to \code{x} for any scalar integer, numeric, string, and logical. If \code{x} is \code{NA}, the result must merely satisfy \code{\link[=is.na]{is.na()}}. The literals \code{"NA"} or \code{"NULL"} are not treated specially. \code{NA} should be translated to an unquoted SQL \code{NULL}, so that the query \verb{SELECT * FROM (SELECT 1) a WHERE ... IS NULL} returns one row. } \examples{ # Quoting ensures that arbitrary input is safe for use in a query name <- "Robert'); DROP TABLE Students;--" dbQuoteLiteral(ANSI(), name) # NAs become NULL dbQuoteLiteral(ANSI(), c(1:3, NA)) # Logicals become integers by default dbQuoteLiteral(ANSI(), c(TRUE, FALSE, NA)) # Raw vectors become hex strings by default dbQuoteLiteral(ANSI(), list(as.raw(1:3), NULL)) # SQL vectors are always passed through as is var_name <- SQL("select") var_name dbQuoteLiteral(ANSI(), var_name) # This mechanism is used to prevent double escaping dbQuoteLiteral(ANSI(), dbQuoteLiteral(ANSI(), name)) } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteString}()} } \concept{DBIResult generics} DBI/man/sqlAppendTable.Rd0000644000176200001440000000531514350241735014621 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/sqlAppendTable.R, R/sqlAppendTableTemplate.R \name{sqlAppendTable} \alias{sqlAppendTable} \alias{sqlAppendTableTemplate} \title{Compose query to insert rows into a table} \usage{ sqlAppendTable(con, table, values, row.names = NA, ...) sqlAppendTableTemplate( con, table, values, row.names = NA, prefix = "?", ..., pattern = "" ) } \arguments{ \item{con}{A database connection.} \item{table}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{values}{A data frame. Factors will be converted to character vectors. Character vectors will be escaped with \code{\link[=dbQuoteString]{dbQuoteString()}}.} \item{row.names}{Either \code{TRUE}, \code{FALSE}, \code{NA} or a string. If \code{TRUE}, always translate row names to a column called "row_names". If \code{FALSE}, never translate row names. If \code{NA}, translate rownames only if they're a character vector. A string is equivalent to \code{TRUE}, but allows you to override the default name. For backward compatibility, \code{NULL} is equivalent to \code{FALSE}.} \item{...}{Other arguments used by individual methods.} \item{prefix}{Parameter prefix to use for placeholders.} \item{pattern}{Parameter pattern to use for placeholders: \itemize{ \item \code{""}: no pattern \item \code{"1"}: position \item anything else: field name }} } \description{ \code{sqlAppendTable()} generates a single SQL string that inserts a data frame into an existing table. \code{sqlAppendTableTemplate()} generates a template suitable for use with \code{\link[=dbBind]{dbBind()}}. The default methods are ANSI SQL 99 compliant. These methods are mostly useful for backend implementers. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("sqlAppendTable")} } \details{ The \code{row.names} argument must be passed explicitly in order to avoid a compatibility warning. The default will be changed in a later release. } \examples{ sqlAppendTable(ANSI(), "iris", head(iris)) sqlAppendTable(ANSI(), "mtcars", head(mtcars)) sqlAppendTable(ANSI(), "mtcars", head(mtcars), row.names = FALSE) sqlAppendTableTemplate(ANSI(), "iris", iris) sqlAppendTableTemplate(ANSI(), "mtcars", mtcars) sqlAppendTableTemplate(ANSI(), "mtcars", mtcars, row.names = FALSE) } \concept{SQL generation} DBI/man/SQL.Rd0000644000176200001440000000360414350241735012360 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/SQL.R \docType{class} \name{SQL} \alias{SQL} \alias{SQL-class} \title{SQL quoting} \usage{ SQL(x, ..., names = NULL) } \arguments{ \item{x}{A character vector to label as being escaped SQL.} \item{...}{Other arguments passed on to methods. Not otherwise used.} \item{names}{Names for the returned object, must have the same length as \code{x}.} } \value{ An object of class \code{SQL}. } \description{ This set of classes and generics make it possible to flexibly deal with SQL escaping needs. By default, any user supplied input to a query should be escaped using either \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or \code{\link[=dbQuoteString]{dbQuoteString()}} depending on whether it refers to a table or variable name, or is a literal string. These functions may return an object of the \code{SQL} class, which tells DBI functions that a character string does not need to be escaped anymore, to prevent double escaping. The \code{SQL} class has associated the \code{SQL()} constructor function. } \section{Implementation notes}{ DBI provides default generics for SQL-92 compatible quoting. If the database uses a different convention, you will need to provide your own methods. Note that because of the way that S4 dispatch finds methods and because SQL inherits from character, if you implement (e.g.) a method for \code{dbQuoteString(MyConnection, character)}, you will also need to implement \code{dbQuoteString(MyConnection, SQL)} - this should simply return \code{x} unchanged. } \examples{ dbQuoteIdentifier(ANSI(), "SELECT") dbQuoteString(ANSI(), "SELECT") # SQL vectors are always passed through as is var_name <- SQL("SELECT") var_name dbQuoteIdentifier(ANSI(), var_name) dbQuoteString(ANSI(), var_name) # This mechanism is used to prevent double escaping dbQuoteString(ANSI(), dbQuoteString(ANSI(), "SELECT")) } DBI/man/dbCanConnect.Rd0000644000176200001440000000337714552712201014244 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbCanConnect.R \name{dbCanConnect} \alias{dbCanConnect} \title{Check if a connection to a DBMS can be established} \usage{ dbCanConnect(drv, ...) } \arguments{ \item{drv}{an object that inherits from \linkS4class{DBIDriver}, or an existing \linkS4class{DBIConnection} object (in order to clone an existing connection).} \item{...}{authentication arguments needed by the DBMS instance; these typically include \code{user}, \code{password}, \code{host}, \code{port}, \code{dbname}, etc. For details see the appropriate \code{DBIDriver}.} } \value{ A scalar logical. If \code{FALSE}, the \code{"reason"} attribute indicates a reason for failure. } \description{ Like \code{\link[=dbConnect]{dbConnect()}}, but only checks validity without actually returning a connection object. The default implementation opens a connection and disconnects on success, but individual backends might implement a lighter-weight check. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbCanConnect")} } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # SQLite only needs a path to the database. (Here, ":memory:" is a special # path that creates an in-memory database.) Other database drivers # will require more details (like user, password, host, port, etc.) dbCanConnect(RSQLite::SQLite(), ":memory:") \dontshow{\}) # examplesIf} } \seealso{ Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbDriver}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListConnections}()} } \concept{DBIDriver generics} DBI/man/Id.Rd0000644000176200001440000000315014552712323012251 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/00-Id.R \docType{class} \name{Id-class} \alias{Id-class} \alias{Id} \title{Refer to a table nested in a hierarchy (e.g. within a schema)} \usage{ Id(...) } \arguments{ \item{...}{Components of the hierarchy, e.g. \code{cluster}, \code{catalog}, \code{schema}, or \code{table}, depending on the database backend. For more on these concepts, see \url{https://stackoverflow.com/questions/7022755/}} } \description{ Objects of class \code{Id} have a single slot \code{name}, which is a character vector. The \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} method converts \code{Id} objects to strings. Support for \code{Id} objects depends on the database backend. They can be used in the following methods as \code{name} or \code{table} argument: \itemize{ \item \code{\link[=dbCreateTable]{dbCreateTable()}} \item \code{\link[=dbAppendTable]{dbAppendTable()}} \item \code{\link[=dbReadTable]{dbReadTable()}} \item \code{\link[=dbWriteTable]{dbWriteTable()}} \item \code{\link[=dbExistsTable]{dbExistsTable()}} \item \code{\link[=dbRemoveTable]{dbRemoveTable()}} } Objects of this class are also returned from \code{\link[=dbListObjects]{dbListObjects()}}. } \examples{ # Identifies a table in a specific schema: Id("dbo", "Customer") # You can name the components if you want, but it's not needed Id(table = "Customer", schema = "dbo") # Create a SQL expression for an identifier: dbQuoteIdentifier(ANSI(), Id("nycflights13", "flights")) # Write a table in a specific schema: \dontrun{ dbWriteTable(con, Id("myschema", "mytable"), data.frame(a = 1)) } } DBI/man/dbGetException.Rd0000644000176200001440000000312314552712323014621 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbGetException.R \name{dbGetException} \alias{dbGetException} \title{Get DBMS exceptions} \usage{ dbGetException(conn, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{...}{Other parameters passed on to methods.} } \value{ a list with elements \code{errorNum} (an integer error number) and \code{errorMsg} (a character string) describing the last error in the connection \code{conn}. } \description{ DEPRECATED. Backends should use R's condition system to signal errors and warnings. } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} \keyword{internal} DBI/man/sqlCreateTable.Rd0000644000176200001440000000455314552712323014620 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/sqlCreateTable.R \name{sqlCreateTable} \alias{sqlCreateTable} \title{Compose query to create a simple table} \usage{ sqlCreateTable(con, table, fields, row.names = NA, temporary = FALSE, ...) } \arguments{ \item{con}{A database connection.} \item{table}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{fields}{Either a character vector or a data frame. A named character vector: Names are column names, values are types. Names are escaped with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Field types are unescaped. A data frame: field types are generated using \code{\link[=dbDataType]{dbDataType()}}.} \item{row.names}{Either \code{TRUE}, \code{FALSE}, \code{NA} or a string. If \code{TRUE}, always translate row names to a column called "row_names". If \code{FALSE}, never translate row names. If \code{NA}, translate rownames only if they're a character vector. A string is equivalent to \code{TRUE}, but allows you to override the default name. For backward compatibility, \code{NULL} is equivalent to \code{FALSE}.} \item{temporary}{If \code{TRUE}, will generate a temporary table.} \item{...}{Other arguments used by individual methods.} } \description{ Exposes an interface to simple \verb{CREATE TABLE} commands. The default method is ANSI SQL 99 compliant. This method is mostly useful for backend implementers. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("sqlCreateTable")} } \details{ The \code{row.names} argument must be passed explicitly in order to avoid a compatibility warning. The default will be changed in a later release. } \examples{ sqlCreateTable(ANSI(), "my-table", c(a = "integer", b = "text")) sqlCreateTable(ANSI(), "my-table", iris) # By default, character row names are converted to a row_names colum sqlCreateTable(ANSI(), "mtcars", mtcars[, 1:5]) sqlCreateTable(ANSI(), "mtcars", mtcars[, 1:5], row.names = FALSE) } DBI/man/sqlInterpolate.Rd0000644000176200001440000000641214350241735014727 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/sqlInterpolate.R \name{sqlInterpolate} \alias{sqlInterpolate} \title{Safely interpolate values into an SQL string} \usage{ sqlInterpolate(conn, sql, ..., .dots = list()) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{sql}{A SQL string containing variables to interpolate. Variables must start with a question mark and can be any valid R identifier, i.e. it must start with a letter or \code{.}, and be followed by a letter, digit, \code{.} or \verb{_}.} \item{..., .dots}{Values (for \code{...}) or a list (for \code{.dots}) to interpolate into a string. Names are required if \code{sql} uses the \code{?name} syntax for placeholders. All values will be first escaped with \code{\link[=dbQuoteLiteral]{dbQuoteLiteral()}} prior to interpolation to protect against SQL injection attacks. Arguments created by \code{\link[=SQL]{SQL()}} or \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} remain unchanged.} } \value{ The \code{sql} query with the values from \code{...} and \code{.dots} safely embedded. } \description{ Accepts a query string with placeholders for values, and returns a string with the values embedded. The function is careful to quote all of its inputs with \code{\link[=dbQuoteLiteral]{dbQuoteLiteral()}} to protect against SQL injection attacks. Placeholders can be specified with one of two syntaxes: \itemize{ \item \verb{?}: each occurrence of a standalone \verb{?} is replaced with a value \item \code{?name1}, \code{?name2}, ...: values are given as named arguments or a named list, the names are used to match the values } Mixing \verb{?} and \code{?name} syntaxes is an error. The number and names of values supplied must correspond to the placeholders used in the query. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("sqlInterpolate")} } \section{Backend authors}{ If you are implementing an SQL backend with non-ANSI quoting rules, you'll need to implement a method for \code{\link[=sqlParseVariables]{sqlParseVariables()}}. Failure to do so does not expose you to SQL injection attacks, but will (rarely) result in errors matching supplied and interpolated variables. } \examples{ sql <- "SELECT * FROM X WHERE name = ?name" sqlInterpolate(ANSI(), sql, name = "Hadley") # This is safe because the single quote has been double escaped sqlInterpolate(ANSI(), sql, name = "H'); DROP TABLE--;") # Using paste0() could lead to dangerous SQL with carefully crafted inputs # (SQL injection) name <- "H'); DROP TABLE--;" paste0("SELECT * FROM X WHERE name = '", name, "'") # Use SQL() or dbQuoteIdentifier() to avoid escaping sql2 <- "SELECT * FROM ?table WHERE name in ?names" sqlInterpolate(ANSI(), sql2, table = dbQuoteIdentifier(ANSI(), "X"), names = SQL("('a', 'b')") ) # Don't use SQL() to escape identifiers to avoid SQL injection sqlInterpolate(ANSI(), sql2, table = SQL("X; DELETE FROM X; SELECT * FROM X"), names = SQL("('a', 'b')") ) # Use dbGetQuery() or dbExecute() to process these queries: if (requireNamespace("RSQLite", quietly = TRUE)) { con <- dbConnect(RSQLite::SQLite()) sql <- "SELECT ?value AS value" query <- sqlInterpolate(con, sql, value = 3) print(dbGetQuery(con, query)) dbDisconnect(con) } } DBI/man/DBIResultArrow-class.Rd0000644000176200001440000000234614552712323015636 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/07-DBIResultArrow.R \docType{class} \name{DBIResultArrow-class} \alias{DBIResultArrow-class} \alias{DBIResultArrowDefault-class} \title{DBIResultArrow class} \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} This virtual class describes the result and state of execution of a DBMS statement (any statement, query or non-query) for returning data as an Arrow object. } \section{Implementation notes}{ Individual drivers are free to allow single or multiple active results per connection. The default show method displays a summary of the query using other DBI generics. } \seealso{ Other DBI classes: \code{\link{DBIConnection-class}}, \code{\link{DBIConnector-class}}, \code{\link{DBIDriver-class}}, \code{\link{DBIObject-class}}, \code{\link{DBIResult-class}} Other DBIResultArrow generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsValid}()} } \concept{DBI classes} \concept{DBIResultArrow generics} DBI/man/sqlData.Rd0000644000176200001440000000336014552712201013304 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/sqlData.R \name{sqlData} \alias{sqlData} \title{Convert a data frame into form suitable for upload to an SQL database} \usage{ sqlData(con, value, row.names = NA, ...) } \arguments{ \item{con}{A database connection.} \item{value}{A data frame} \item{row.names}{Either \code{TRUE}, \code{FALSE}, \code{NA} or a string. If \code{TRUE}, always translate row names to a column called "row_names". If \code{FALSE}, never translate row names. If \code{NA}, translate rownames only if they're a character vector. A string is equivalent to \code{TRUE}, but allows you to override the default name. For backward compatibility, \code{NULL} is equivalent to \code{FALSE}.} \item{...}{Other arguments used by individual methods.} } \description{ This is a generic method that coerces R objects into vectors suitable for upload to the database. The output will vary a little from method to method depending on whether the main upload device is through a single SQL string or multiple parameterized queries. This method is mostly useful for backend implementers. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("sqlData")} } \details{ The default method: \itemize{ \item Converts factors to characters \item Quotes all strings with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} \item Converts all columns to strings with \code{\link[=dbQuoteLiteral]{dbQuoteLiteral()}} \item Replaces NA with NULL } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") sqlData(con, head(iris)) sqlData(con, head(mtcars)) dbDisconnect(con) \dontshow{\}) # examplesIf} } DBI/man/dbSendQuery.Rd0000644000176200001440000002214614552712323014150 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/14-dbSendQuery.R \name{dbSendQuery} \alias{dbSendQuery} \title{Execute a query on a given database connection} \usage{ dbSendQuery(conn, statement, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{statement}{a character string containing SQL.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbSendQuery()} returns an S4 object that inherits from \linkS4class{DBIResult}. The result set can be used with \code{\link[=dbFetch]{dbFetch()}} to extract records. Once you have finished using a result, make sure to clear it with \code{\link[=dbClearResult]{dbClearResult()}}. } \description{ The \code{dbSendQuery()} method only submits and synchronously executes the SQL query to the database engine. It does \emph{not} extract any records --- for that you need to use the \code{\link[=dbFetch]{dbFetch()}} method, and then you must call \code{\link[=dbClearResult]{dbClearResult()}} when you finish fetching the records you need. For interactive use, you should almost always prefer \code{\link[=dbGetQuery]{dbGetQuery()}}. Use \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}} or \code{\link[=dbGetQueryArrow]{dbGetQueryArrow()}} instead to retrieve the results as an Arrow object. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbSendQuery")} } \details{ This method is for \code{SELECT} queries only. Some backends may support data manipulation queries through this method for compatibility reasons. However, callers are strongly encouraged to use \code{\link[=dbSendStatement]{dbSendStatement()}} for data manipulation statements. The query is submitted to the database server and the DBMS executes it, possibly generating vast amounts of data. Where these data live is driver-specific: some drivers may choose to leave the output on the server and transfer them piecemeal to R, others may transfer all the data to the client -- but not necessarily to the memory that R manages. See individual drivers' \code{dbSendQuery()} documentation for details. } \section{The data retrieval flow}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbGetQuery]{dbGetQuery()}}, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQuery]{dbSendQuery()}} to create a result set object of class \linkS4class{DBIResult}. \item Optionally, bind query parameters with \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbColumnInfo]{dbColumnInfo()}} to retrieve the structure of the result set without retrieving actual data. \item Use \code{\link[=dbFetch]{dbFetch()}} to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. \item Use \code{\link[=dbHasCompleted]{dbHasCompleted()}} to tell when you're done. This method returns \code{TRUE} if no more rows are available for fetching. \item Repeat the last four steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ An error is raised when issuing a query over a closed or invalid connection, or if the query is not a non-\code{NA} string. An error is also raised if the syntax of the query is invalid and all query parameters are given (by passing the \code{params} argument) or the \code{immediate} argument is set to \code{TRUE}. } \section{Additional arguments}{ The following arguments are not part of the \code{dbSendQuery()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{params} (default: \code{NULL}) \item \code{immediate} (default: \code{NULL}) } They must be provided as named arguments. See the "Specification" sections for details on their usage. } \section{Specification}{ No warnings occur under normal conditions. When done, the DBIResult object must be cleared with a call to \code{\link[=dbClearResult]{dbClearResult()}}. Failure to clear the result set leads to a warning when the connection is closed. If the backend supports only one open result set per connection, issuing a second query invalidates an already open result set and raises a warning. The newly opened result set is valid and must be cleared with \code{dbClearResult()}. The \code{param} argument allows passing query parameters, see \code{\link[=dbBind]{dbBind()}} for details. } \section{Specification for the \code{immediate} argument}{ The \code{immediate} argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing \code{immediate = TRUE} leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default \code{NULL} means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct \code{immediate} argument. Examples for possible behaviors: \enumerate{ \item DBI backend defaults to \code{immediate = TRUE} internally \enumerate{ \item A query without parameters is passed: query is executed \item A query with parameters is passed: \enumerate{ \item \code{params} not given: rejected immediately by the database because of a syntax error in the query, the backend tries \code{immediate = FALSE} (and gives a message) \item \code{params} given: query is executed using \code{immediate = FALSE} } } \item DBI backend defaults to \code{immediate = FALSE} internally \enumerate{ \item A query without parameters is passed: \enumerate{ \item simple query: query is executed \item "special" query (such as setting a config options): fails, the backend tries \code{immediate = TRUE} (and gives a message) } \item A query with parameters is passed: \enumerate{ \item \code{params} not given: waiting for parameters via \code{\link[=dbBind]{dbBind()}} \item \code{params} given: query is executed } } } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4") dbFetch(rs) dbClearResult(rs) # Pass one set of values with the param argument: rs <- dbSendQuery( con, "SELECT * FROM mtcars WHERE cyl = ?", params = list(4L) ) dbFetch(rs) dbClearResult(rs) # Pass multiple sets of values with dbBind(): rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = ?") dbBind(rs, list(6L)) dbFetch(rs) dbBind(rs, list(8L)) dbFetch(rs) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ For updates: \code{\link[=dbSendStatement]{dbSendStatement()}} and \code{\link[=dbExecute]{dbExecute()}}. Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQueryArrow}()} } \concept{DBIConnection generics} \concept{data retrieval generics} DBI/man/dbCallProc.Rd0000644000176200001440000000125014350241735013721 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbCallProc.R \name{dbCallProc} \alias{dbCallProc} \title{Call an SQL stored procedure} \usage{ dbCallProc(conn, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{...}{Other parameters passed on to methods.} } \description{ \strong{Deprecated since 2014} } \details{ The recommended way of calling a stored procedure is now \enumerate{ \item{\code{\link{dbGetQuery}} if a result set is returned} \item{\code{\link{dbExecute}} for data manipulation and other cases where no result set is returned} } } \keyword{internal} DBI/man/dot-SQL92Keywords.Rd0000644000176200001440000000064114552712323015045 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/deprecated.R \docType{data} \name{.SQL92Keywords} \alias{.SQL92Keywords} \title{Keywords according to the SQL-92 standard} \format{ An object of class \code{character} of length 220. } \usage{ .SQL92Keywords } \description{ A character vector of SQL-92 keywords, uppercase. } \examples{ "SELECT" \%in\% .SQL92Keywords } \keyword{datasets} DBI/man/dbGetInfo.Rd0000644000176200001440000001026414552712323013562 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/04-DBIResult.R, R/dbGetInfo.R \name{dbGetInfo} \alias{dbGetInfo} \title{Get DBMS metadata} \usage{ dbGetInfo(dbObj, ...) } \arguments{ \item{dbObj}{An object inheriting from \linkS4class{DBIObject}, i.e. \linkS4class{DBIDriver}, \linkS4class{DBIConnection}, or a \linkS4class{DBIResult}} \item{...}{Other arguments to methods.} } \value{ For objects of class \linkS4class{DBIDriver}, \code{dbGetInfo()} returns a named list that contains at least the following components: \itemize{ \item \code{driver.version}: the package version of the DBI backend, \item \code{client.version}: the version of the DBMS client library. } For objects of class \linkS4class{DBIConnection}, \code{dbGetInfo()} returns a named list that contains at least the following components: \itemize{ \item \code{db.version}: version of the database server, \item \code{dbname}: database name, \item \code{username}: username to connect to the database, \item \code{host}: hostname of the database server, \item \code{port}: port on the database server. It must not contain a \code{password} component. Components that are not applicable should be set to \code{NA}. } For objects of class \linkS4class{DBIResult}, \code{dbGetInfo()} returns a named list that contains at least the following components: \itemize{ \item \code{statatment}: the statement used with \code{\link[=dbSendQuery]{dbSendQuery()}} or \code{\link[=dbExecute]{dbExecute()}}, as returned by \code{\link[=dbGetStatement]{dbGetStatement()}}, \item \code{row.count}: the number of rows fetched so far (for queries), as returned by \code{\link[=dbGetRowCount]{dbGetRowCount()}}, \item \code{rows.affected}: the number of rows affected (for statements), as returned by \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}} \item \code{has.completed}: a logical that indicates if the query or statement has completed, as returned by \code{\link[=dbHasCompleted]{dbHasCompleted()}}. } } \description{ Retrieves information on objects of class \linkS4class{DBIDriver}, \linkS4class{DBIConnection} or \linkS4class{DBIResult}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbGetInfo")} } \section{Implementation notes}{ The default implementation for \verb{DBIResult objects} constructs such a list from the return values of the corresponding methods, \code{\link[=dbGetStatement]{dbGetStatement()}}, \code{\link[=dbGetRowCount]{dbGetRowCount()}}, \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}}, and \code{\link[=dbHasCompleted]{dbHasCompleted()}}. } \seealso{ Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbCanConnect}()}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbDriver}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListConnections}()} Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} } \concept{DBIConnection generics} \concept{DBIDriver generics} \concept{DBIResult generics} DBI/man/dbAppendTable.Rd0000644000176200001440000001471214552712323014410 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/11-dbAppendTable.R \name{dbAppendTable} \alias{dbAppendTable} \title{Insert rows into a table} \usage{ dbAppendTable(conn, name, value, ..., row.names = NULL) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{value}{A \link{data.frame} (or coercible to data.frame).} \item{...}{Other parameters passed on to methods.} \item{row.names}{Must be \code{NULL}.} } \value{ \code{dbAppendTable()} returns a scalar numeric. } \description{ The \code{dbAppendTable()} method assumes that the table has been created beforehand, e.g. with \code{\link[=dbCreateTable]{dbCreateTable()}}. The default implementation calls \code{\link[=sqlAppendTableTemplate]{sqlAppendTableTemplate()}} and then \code{\link[=dbExecute]{dbExecute()}} with the \code{param} argument. Use \code{\link[=dbAppendTableArrow]{dbAppendTableArrow()}} to append data from an Arrow stream. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbAppendTable")} } \details{ Backends compliant to ANSI SQL 99 which use \verb{?} as a placeholder for prepared queries don't need to override it. Backends with a different SQL syntax which use \verb{?} as a placeholder for prepared queries can override \code{\link[=sqlAppendTable]{sqlAppendTable()}}. Other backends (with different placeholders or with entirely different ways to create tables) need to override the \code{dbAppendTable()} method. The \code{row.names} argument is not supported by this method. Process the values with \code{\link[=sqlRownamesToColumn]{sqlRownamesToColumn()}} before calling this method. } \section{Failure modes}{ If the table does not exist, or the new data in \code{values} is not a data frame or has different column names, 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 \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. Invalid values for the \code{row.names} argument (non-scalars, unsupported data types, \code{NA}) also raise an error. Passing a \code{value} argument different to \code{NULL} to the \code{row.names} argument (in particular \code{TRUE}, \code{NA}, and a string) raises an error. } \section{Specification}{ SQL keywords can be used freely in table names, column names, and data. Quotes, commas, spaces, and other special characters such as newlines and tabs, can also be used in the data, and, if the database supports non-syntactic identifiers, also for table names and column names. The following data types must be supported at least, and be read identically with \code{\link[=dbReadTable]{dbReadTable()}}: \itemize{ \item integer \item numeric (the behavior for \code{Inf} and \code{NaN} is not specified) \item logical \item \code{NA} as NULL \item 64-bit values (using \code{"bigint"} as field type); the result can be \itemize{ \item converted to a numeric, which may lose precision, \item converted a character vector, which gives the full decimal representation \item written to another table and read again unchanged } \item character (in both UTF-8 and native encodings), supporting empty strings (before and after non-empty strings) \item factor (returned as character, with a warning) \item list of raw (if supported by the database) \item objects of type \link[blob:blob]{blob::blob} (if supported by the database) \item date (if supported by the database; returned as \code{Date}) also for dates prior to 1970 or 1900 or after 2038 \item time (if supported by the database; returned as objects that inherit from \code{difftime}) \item timestamp (if supported by the database; returned as \code{POSIXct} respecting the time zone but not necessarily preserving the input time zone), also for timestamps prior to 1970 or 1900 or after 2038 respecting the time zone but not necessarily preserving the input time zone) } Mixing column types in the same table is supported. The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbAppendTable()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done to support databases that allow non-syntactic names for their objects: } The \code{row.names} argument must be \code{NULL}, the default value. Row names are ignored. The \code{value} argument must be a data frame with a subset of the columns of the existing table. The order of the columns does not matter. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbCreateTable(con, "iris", iris) dbAppendTable(con, "iris", iris) dbReadTable(con, "iris") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbCreateTable.Rd0000644000176200001440000001305614552712323014404 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/12-dbCreateTable.R \name{dbCreateTable} \alias{dbCreateTable} \title{Create a table in the database} \usage{ dbCreateTable(conn, name, fields, ..., row.names = NULL, temporary = FALSE) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{fields}{Either a character vector or a data frame. A named character vector: Names are column names, values are types. Names are escaped with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Field types are unescaped. A data frame: field types are generated using \code{\link[=dbDataType]{dbDataType()}}.} \item{...}{Other parameters passed on to methods.} \item{row.names}{Must be \code{NULL}.} \item{temporary}{If \code{TRUE}, will generate a temporary table.} } \value{ \code{dbCreateTable()} returns \code{TRUE}, invisibly. } \description{ The default \code{dbCreateTable()} method calls \code{\link[=sqlCreateTable]{sqlCreateTable()}} and \code{\link[=dbExecute]{dbExecute()}}. Use \code{\link[=dbCreateTableArrow]{dbCreateTableArrow()}} to create a table from an Arrow schema. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbCreateTable")} } \details{ Backends compliant to ANSI SQL 99 don't need to override it. Backends with a different SQL syntax can override \code{sqlCreateTable()}, backends with entirely different ways to create tables need to override this method. The \code{row.names} argument is not supported by this method. Process the values with \code{\link[=sqlRownamesToColumn]{sqlRownamesToColumn()}} before calling this method. The argument order is different from the \code{sqlCreateTable()} method, the latter will be adapted in a later release of DBI. } \section{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 \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. Invalid values for the \code{row.names} and \code{temporary} arguments (non-scalars, unsupported data types, \code{NA}, incompatible values, duplicate names) also raise an error. } \section{Additional arguments}{ The following arguments are not part of the \code{dbCreateTable()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{temporary} (default: \code{FALSE}) } They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage. } \section{Specification}{ The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbCreateTable()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done } The \code{value} argument can be: \itemize{ \item a data frame, \item a named list of SQL types } If the \code{temporary} argument is \code{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. The \code{row.names} argument must be missing or \code{NULL}, the default value. All other values for the \code{row.names} argument (in particular \code{TRUE}, \code{NA}, and a string) raise an error. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbCreateTable(con, "iris", iris) dbReadTable(con, "iris") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/ANSI.Rd0000644000176200001440000000046314552712156012457 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/06-ANSI.R \name{ANSI} \alias{ANSI} \title{A dummy DBI connector that simulates ANSI-SQL compliance} \usage{ ANSI() } \description{ A dummy DBI connector that simulates ANSI-SQL compliance } \examples{ ANSI() } \keyword{internal} DBI/man/dbListResults.Rd0000644000176200001440000000316014552712323014521 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbListResults.R \name{dbListResults} \alias{dbListResults} \title{A list of all pending results} \usage{ dbListResults(conn, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{...}{Other parameters passed on to methods.} } \value{ a list. If no results are active, an empty list. If only a single result is active, a list with one element. } \description{ DEPRECATED. DBI currenty supports only one open result set per connection, you need to keep track of the result sets you open if you need this functionality. } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} \keyword{internal} DBI/man/dbGetQueryArrow.Rd0000644000176200001440000001503214552712323015005 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbGetQueryArrow.R \name{dbGetQueryArrow} \alias{dbGetQueryArrow} \title{Retrieve results from a query as an Arrow object} \usage{ dbGetQueryArrow(conn, statement, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{statement}{a character string containing SQL.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbGetQueryArrow()} always returns an object coercible to a \link{data.frame}, with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows. } \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} Returns the result of a query as an Arrow object. \code{dbGetQueryArrow()} comes with a default implementation (which should work with most backends) that calls \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}}, then \code{\link[=dbFetchArrow]{dbFetchArrow()}}, ensuring that the result is always freed by \code{\link[=dbClearResult]{dbClearResult()}}. For passing query parameters, see \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}}, in particular the "The data retrieval flow for Arrow streams" section. For retrieving results as a data frame, see \code{\link[=dbGetQuery]{dbGetQuery()}}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbGetQueryArrow")} } \details{ This method is for \code{SELECT} queries only (incl. other SQL statements that return a \code{SELECT}-alike result, e.g., execution of a stored procedure or data manipulation queries like \verb{INSERT INTO ... RETURNING ...}). To execute a stored procedure that does not return a result set, use \code{\link[=dbExecute]{dbExecute()}}. Some backends may support data manipulation statements through this method. However, callers are strongly advised to use \code{\link[=dbExecute]{dbExecute()}} for data manipulation statements. } \section{Implementation notes}{ Subclasses should override this method only if they provide some sort of performance optimization. } \section{Failure modes}{ An error is raised when issuing a query over a closed or invalid connection, if the syntax of the query is invalid, or if the query is not a non-\code{NA} string. The object returned by \code{dbGetQueryArrow()} can also be passed to \code{\link[nanoarrow:as_nanoarrow_array_stream]{nanoarrow::as_nanoarrow_array_stream()}} to create a nanoarrow array stream object that can be used to read the result set in batches. The chunk size is implementation-specific. } \section{Additional arguments}{ The following arguments are not part of the \code{dbGetQueryArrow()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{params} (default: \code{NULL}) \item \code{immediate} (default: \code{NULL}) } They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage. The \code{param} argument allows passing query parameters, see \code{\link[=dbBind]{dbBind()}} for details. } \section{Specification for the \code{immediate} argument}{ The \code{immediate} argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing \code{immediate = TRUE} leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default \code{NULL} means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct \code{immediate} argument. Examples for possible behaviors: \enumerate{ \item DBI backend defaults to \code{immediate = TRUE} internally \enumerate{ \item A query without parameters is passed: query is executed \item A query with parameters is passed: \enumerate{ \item \code{params} not given: rejected immediately by the database because of a syntax error in the query, the backend tries \code{immediate = FALSE} (and gives a message) \item \code{params} given: query is executed using \code{immediate = FALSE} } } \item DBI backend defaults to \code{immediate = FALSE} internally \enumerate{ \item A query without parameters is passed: \enumerate{ \item simple query: query is executed \item "special" query (such as setting a config options): fails, the backend tries \code{immediate = TRUE} (and gives a message) } \item A query with parameters is passed: \enumerate{ \item \code{params} not given: waiting for parameters via \code{\link[=dbBind]{dbBind()}} \item \code{params} given: query is executed } } } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # Retrieve data as arrow table con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) dbGetQueryArrow(con, "SELECT * FROM mtcars") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ For updates: \code{\link[=dbSendStatement]{dbSendStatement()}} and \code{\link[=dbExecute]{dbExecute()}}. Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQuery}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()} } \concept{DBIConnection generics} \concept{data retrieval generics} DBI/man/dbExecute.Rd0000644000176200001440000001337614552712323013640 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbExecute.R \name{dbExecute} \alias{dbExecute} \title{Change database state} \usage{ dbExecute(conn, statement, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{statement}{a character string containing SQL.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbExecute()} always returns a scalar numeric that specifies the number of rows affected by the statement. } \description{ Executes a statement and returns the number of rows affected. \code{dbExecute()} comes with a default implementation (which should work with most backends) that calls \code{\link[=dbSendStatement]{dbSendStatement()}}, then \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}}, ensuring that the result is always freed by \code{\link[=dbClearResult]{dbClearResult()}}. For passing query parameters, see \code{\link[=dbBind]{dbBind()}}, in particular the "The command execution flow" section. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbExecute")} } \details{ You can also use \code{dbExecute()} to call a stored procedure that performs data manipulation or other actions that do not return a result set. To execute a stored procedure that returns a result set, or a data manipulation query that also returns a result set such as \verb{INSERT INTO ... RETURNING ...}, use \code{\link[=dbGetQuery]{dbGetQuery()}} instead. } \section{Implementation notes}{ Subclasses should override this method only if they provide some sort of performance optimization. } \section{Failure modes}{ An error is raised when issuing a statement over a closed or invalid connection, if the syntax of the statement is invalid, or if the statement is not a non-\code{NA} string. } \section{Additional arguments}{ The following arguments are not part of the \code{dbExecute()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{params} (default: \code{NULL}) \item \code{immediate} (default: \code{NULL}) } They must be provided as named arguments. See the "Specification" sections for details on their usage. } \section{Specification}{ The \code{param} argument allows passing query parameters, see \code{\link[=dbBind]{dbBind()}} for details. } \section{Specification for the \code{immediate} argument}{ The \code{immediate} argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing \code{immediate = TRUE} leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default \code{NULL} means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct \code{immediate} argument. Examples for possible behaviors: \enumerate{ \item DBI backend defaults to \code{immediate = TRUE} internally \enumerate{ \item A query without parameters is passed: query is executed \item A query with parameters is passed: \enumerate{ \item \code{params} not given: rejected immediately by the database because of a syntax error in the query, the backend tries \code{immediate = FALSE} (and gives a message) \item \code{params} given: query is executed using \code{immediate = FALSE} } } \item DBI backend defaults to \code{immediate = FALSE} internally \enumerate{ \item A query without parameters is passed: \enumerate{ \item simple query: query is executed \item "special" query (such as setting a config options): fails, the backend tries \code{immediate = TRUE} (and gives a message) } \item A query with parameters is passed: \enumerate{ \item \code{params} not given: waiting for parameters via \code{\link[=dbBind]{dbBind()}} \item \code{params} given: query is executed } } } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cars", head(cars, 3)) dbReadTable(con, "cars") # there are 3 rows dbExecute( con, "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" ) dbReadTable(con, "cars") # there are now 6 rows # Pass values using the param argument: dbExecute( con, "INSERT INTO cars (speed, dist) VALUES (?, ?)", params = list(4:7, 5:8) ) dbReadTable(con, "cars") # there are now 10 rows dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ For queries: \code{\link[=dbSendQuery]{dbSendQuery()}} and \code{\link[=dbGetQuery]{dbGetQuery()}}. Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other command execution generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbSendStatement}()} } \concept{DBIConnection generics} \concept{command execution generics} DBI/man/DBIObject-class.Rd0000644000176200001440000000347714552712323014561 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/01-DBIObject.R \docType{class} \name{DBIObject-class} \alias{DBIObject-class} \title{DBIObject class} \description{ Base class for all other DBI classes (e.g., drivers, connections). This is a virtual Class: No objects may be created from it. } \details{ More generally, the DBI defines a very small set of classes and generics that allows users and applications access DBMS with a common interface. The virtual classes are \code{DBIDriver} that individual drivers extend, \code{DBIConnection} that represent instances of DBMS connections, and \code{DBIResult} that represent the result of a DBMS statement. These three classes extend the basic class of \code{DBIObject}, which serves as the root or parent of the class hierarchy. } \section{Implementation notes}{ An implementation MUST provide methods for the following generics: \itemize{ \item \code{\link[=dbGetInfo]{dbGetInfo()}}. } It MAY also provide methods for: \itemize{ \item \code{\link[=summary]{summary()}}. Print a concise description of the object. The default method invokes \code{dbGetInfo(dbObj)} and prints the name-value pairs one per line. Individual implementations may tailor this appropriately. } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} drv <- RSQLite::SQLite() con <- dbConnect(drv) rs <- dbSendQuery(con, "SELECT 1") is(drv, "DBIObject") ## True is(con, "DBIObject") ## True is(rs, "DBIObject") dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBI classes: \code{\link{DBIConnection-class}}, \code{\link{DBIConnector-class}}, \code{\link{DBIDriver-class}}, \code{\link{DBIResult-class}}, \code{\link{DBIResultArrow-class}} } \concept{DBI classes} DBI/man/dbIsValid.Rd0000644000176200001440000000772714552712323013574 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbIsValid.R \name{dbIsValid} \alias{dbIsValid} \title{Is this DBMS object still valid?} \usage{ dbIsValid(dbObj, ...) } \arguments{ \item{dbObj}{An object inheriting from \linkS4class{DBIObject}, i.e. \linkS4class{DBIDriver}, \linkS4class{DBIConnection}, or a \linkS4class{DBIResult}} \item{...}{Other arguments to methods.} } \value{ \code{dbIsValid()} returns a logical scalar, \code{TRUE} if the object specified by \code{dbObj} is valid, \code{FALSE} otherwise. A \linkS4class{DBIConnection} object is initially valid, and becomes invalid after disconnecting with \code{\link[=dbDisconnect]{dbDisconnect()}}. For an invalid connection object (e.g., for some drivers if the object is saved to a file and then restored), the method also returns \code{FALSE}. A \linkS4class{DBIResult} object is valid after a call to \code{\link[=dbSendQuery]{dbSendQuery()}}, and stays valid even after all rows have been fetched; only clearing it with \code{\link[=dbClearResult]{dbClearResult()}} invalidates it. A \linkS4class{DBIResult} object is also valid after a call to \code{\link[=dbSendStatement]{dbSendStatement()}}, and stays valid after querying the number of rows affected; only clearing it with \code{\link[=dbClearResult]{dbClearResult()}} invalidates it. If the connection to the database system is dropped (e.g., due to connectivity problems, server failure, etc.), \code{dbIsValid()} should return \code{FALSE}. This is not tested automatically. } \description{ This generic tests whether a database object is still valid (i.e. it hasn't been disconnected or cleared). \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbIsValid")} } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} dbIsValid(RSQLite::SQLite()) con <- dbConnect(RSQLite::SQLite(), ":memory:") dbIsValid(con) rs <- dbSendQuery(con, "SELECT 1") dbIsValid(rs) dbClearResult(rs) dbIsValid(rs) dbDisconnect(con) dbIsValid(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbCanConnect}()}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbDriver}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbListConnections}()} Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} Other DBIResultArrow generics: \code{\link{DBIResultArrow-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbHasCompleted}()} } \concept{DBIConnection generics} \concept{DBIDriver generics} \concept{DBIResult generics} \concept{DBIResultArrow generics} DBI/man/dbGetRowCount.Rd0000644000176200001440000000442214552712323014446 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbGetRowCount.R \name{dbGetRowCount} \alias{dbGetRowCount} \title{The number of rows fetched so far} \usage{ dbGetRowCount(res, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbGetRowCount()} returns a scalar number (integer or numeric), the number of rows fetched so far. After calling \code{\link[=dbSendQuery]{dbSendQuery()}}, the row count is initially zero. After a call to \code{\link[=dbFetch]{dbFetch()}} without limit, the row count matches the total number of rows returned. Fetching a limited number of rows increases the number of rows by the number of rows returned, even if fetching past the end of the result set. For queries with an empty result set, zero is returned even after fetching. For data manipulation statements issued with \code{\link[=dbSendStatement]{dbSendStatement()}}, zero is returned before and after calling \code{dbFetch()}. } \description{ Returns the total number of rows actually fetched with calls to \code{\link[=dbFetch]{dbFetch()}} for this result set. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbGetRowCount")} } \section{Failure modes}{ Attempting to get the row count for a result set cleared with \code{\link[=dbClearResult]{dbClearResult()}} gives an error. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQuery(con, "SELECT * FROM mtcars") dbGetRowCount(rs) ret1 <- dbFetch(rs, 10) dbGetRowCount(rs) ret2 <- dbFetch(rs) dbGetRowCount(rs) nrow(ret1) + nrow(ret2) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} } \concept{DBIResult generics} DBI/man/dbReadTable.Rd0000644000176200001440000001214414552712323014051 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbReadTable.R \name{dbReadTable} \alias{dbReadTable} \title{Read database tables as data frames} \usage{ dbReadTable(conn, name, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbReadTable()} returns a data frame that contains the complete data from the remote table, effectively the result of calling \code{\link[=dbGetQuery]{dbGetQuery()}} with \verb{SELECT * FROM }. An empty table is returned as a data frame with zero rows. The presence of \link{rownames} depends on the \code{row.names} argument, see \code{\link[=sqlColumnToRownames]{sqlColumnToRownames()}} for details: \itemize{ \item If \code{FALSE} or \code{NULL}, the returned data frame doesn't have row names. \item If \code{TRUE}, a column named "row_names" is converted to row names. } \itemize{ \item If \code{NA}, a column named "row_names" is converted to row names if it exists, otherwise no translation occurs. \item If a string, this specifies the name of the column in the remote table that contains the row names. } The default is \code{row.names = FALSE}. If the database supports identifiers with special characters, the columns in the returned data frame are converted to valid R identifiers if the \code{check.names} argument is \code{TRUE}, If \code{check.names = FALSE}, the returned table has non-syntactic column names without quotes. } \description{ Reads a database table to a data frame, optionally converting a column to row names and converting the column names to valid R identifiers. Use \code{\link[=dbReadTableArrow]{dbReadTableArrow()}} instead to obtain an Arrow object. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbReadTable")} } \details{ This function returns a data frame. Use \code{\link[=dbReadTableArrow]{dbReadTableArrow()}} to obtain an Arrow object. } \section{Failure modes}{ An error is raised if the table does not exist. An error is raised if \code{row.names} is \code{TRUE} and no "row_names" column exists, An error is raised if \code{row.names} is set to a string and no corresponding column exists. An error is raised when calling this method for a closed or invalid connection. An error is raised if \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. Unsupported values for \code{row.names} and \code{check.names} (non-scalars, unsupported data types, \code{NA} for \code{check.names}) also raise an error. } \section{Additional arguments}{ The following arguments are not part of the \code{dbReadTable()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{row.names} (default: \code{FALSE}) \item \code{check.names} } They must be provided as named arguments. See the "Value" section for details on their usage. } \section{Specification}{ The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbReadTable()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars[1:10, ]) dbReadTable(con, "mtcars") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbQuoteIdentifier.Rd0000644000176200001440000000752514552712323015335 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbQuoteIdentifier.R \name{dbQuoteIdentifier} \alias{dbQuoteIdentifier} \title{Quote identifiers} \usage{ dbQuoteIdentifier(conn, x, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{x}{A character vector, \link{SQL} or \link{Id} object to quote as identifier.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbQuoteIdentifier()} returns an object that can be coerced to \link{character}, of the same length as the input. For an empty character vector this function returns a length-0 object. The names of the input argument are preserved in the output. When passing the returned object again to \code{dbQuoteIdentifier()} as \code{x} argument, it is returned unchanged. Passing objects of class \link{SQL} should also return them unchanged. (For backends it may be most convenient to return \link{SQL} objects to achieve this behavior, but this is not required.) } \description{ Call this method to generate a string that is suitable for use in a query as a column or table name, to make sure that you generate valid SQL and protect against SQL injection attacks. The inverse operation is \code{\link[=dbUnquoteIdentifier]{dbUnquoteIdentifier()}}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbQuoteIdentifier")} } \section{Failure modes}{ An error is raised if the input contains \code{NA}, but not for an empty string. } \section{Specification}{ Calling \code{\link[=dbGetQuery]{dbGetQuery()}} for a query of the format \verb{SELECT 1 AS ...} returns a data frame with the identifier, unquoted, as column name. Quoted identifiers can be used as table and column names in SQL queries, in particular in queries like \verb{SELECT 1 AS ...} and \verb{SELECT * FROM (SELECT 1) ...}. The method must use a quoting mechanism that is unambiguously different from the quoting mechanism used for strings, so that a query like \verb{SELECT ... FROM (SELECT 1 AS ...)} throws an error if the column names do not match. The method can quote column names that contain special characters such as a space, a dot, a comma, or quotes used to mark strings or identifiers, if the database supports this. In any case, checking the validity of the identifier should be performed only when executing a query, and not by \code{dbQuoteIdentifier()}. } \examples{ # Quoting ensures that arbitrary input is safe for use in a query name <- "Robert'); DROP TABLE Students;--" dbQuoteIdentifier(ANSI(), name) # Use Id() to specify other components such as the schema id_name <- Id(schema = "schema_name", table = "table_name") id_name dbQuoteIdentifier(ANSI(), id_name) # SQL vectors are always passed through as is var_name <- SQL("select") var_name dbQuoteIdentifier(ANSI(), var_name) # This mechanism is used to prevent double escaping dbQuoteIdentifier(ANSI(), dbQuoteIdentifier(ANSI(), name)) } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbSendQueryArrow.Rd0000644000176200001440000002013414552712323015156 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/24-dbSendQueryArrow.R \name{dbSendQueryArrow} \alias{dbSendQueryArrow} \title{Execute a query on a given database connection for retrieval via Arrow} \usage{ dbSendQueryArrow(conn, statement, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{statement}{a character string containing SQL.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbSendQueryArrow()} returns an S4 object that inherits from \linkS4class{DBIResultArrow}. The result set can be used with \code{\link[=dbFetchArrow]{dbFetchArrow()}} to extract records. Once you have finished using a result, make sure to clear it with \code{\link[=dbClearResult]{dbClearResult()}}. } \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} The \code{dbSendQueryArrow()} method only submits and synchronously executes the SQL query to the database engine. It does \emph{not} extract any records --- for that you need to use the \code{\link[=dbFetchArrow]{dbFetchArrow()}} method, and then you must call \code{\link[=dbClearResult]{dbClearResult()}} when you finish fetching the records you need. For interactive use, you should almost always prefer \code{\link[=dbGetQueryArrow]{dbGetQueryArrow()}}. Use \code{\link[=dbSendQuery]{dbSendQuery()}} or \code{\link[=dbGetQuery]{dbGetQuery()}} instead to retrieve the results as a data frame. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbSendQueryArrow")} } \details{ This method is for \code{SELECT} queries only. Some backends may support data manipulation queries through this method for compatibility reasons. However, callers are strongly encouraged to use \code{\link[=dbSendStatement]{dbSendStatement()}} for data manipulation statements. } \section{The data retrieval flow for Arrow streams}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as an Arrow stream. Most of this flow, except repeated calling of \code{\link[=dbBindArrow]{dbBindArrow()}} or \code{\link[=dbBind]{dbBind()}}, is implemented by \code{\link[=dbGetQueryArrow]{dbGetQueryArrow()}}, which should be sufficient unless you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}} to create a result set object of class \linkS4class{DBIResultArrow}. \item Optionally, bind query parameters with \code{\link[=dbBindArrow]{dbBindArrow()}} or \code{\link[=dbBind]{dbBind()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Use \code{\link[=dbFetchArrow]{dbFetchArrow()}} to get a data stream. \item Repeat the last two steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ An error is raised when issuing a query over a closed or invalid connection, or if the query is not a non-\code{NA} string. An error is also raised if the syntax of the query is invalid and all query parameters are given (by passing the \code{params} argument) or the \code{immediate} argument is set to \code{TRUE}. } \section{Additional arguments}{ The following arguments are not part of the \code{dbSendQueryArrow()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{params} (default: \code{NULL}) \item \code{immediate} (default: \code{NULL}) } They must be provided as named arguments. See the "Specification" sections for details on their usage. } \section{Specification}{ No warnings occur under normal conditions. When done, the DBIResult object must be cleared with a call to \code{\link[=dbClearResult]{dbClearResult()}}. Failure to clear the result set leads to a warning when the connection is closed. If the backend supports only one open result set per connection, issuing a second query invalidates an already open result set and raises a warning. The newly opened result set is valid and must be cleared with \code{dbClearResult()}. The \code{param} argument allows passing query parameters, see \code{\link[=dbBind]{dbBind()}} for details. } \section{Specification for the \code{immediate} argument}{ The \code{immediate} argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing \code{immediate = TRUE} leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default \code{NULL} means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct \code{immediate} argument. Examples for possible behaviors: \enumerate{ \item DBI backend defaults to \code{immediate = TRUE} internally \enumerate{ \item A query without parameters is passed: query is executed \item A query with parameters is passed: \enumerate{ \item \code{params} not given: rejected immediately by the database because of a syntax error in the query, the backend tries \code{immediate = FALSE} (and gives a message) \item \code{params} given: query is executed using \code{immediate = FALSE} } } \item DBI backend defaults to \code{immediate = FALSE} internally \enumerate{ \item A query without parameters is passed: \enumerate{ \item simple query: query is executed \item "special" query (such as setting a config options): fails, the backend tries \code{immediate = TRUE} (and gives a message) } \item A query with parameters is passed: \enumerate{ \item \code{params} not given: waiting for parameters via \code{\link[=dbBind]{dbBind()}} \item \code{params} given: query is executed } } } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # Retrieve data as arrow table con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQueryArrow(con, "SELECT * FROM mtcars WHERE cyl = 4") dbFetchArrow(rs) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ For updates: \code{\link[=dbSendStatement]{dbSendStatement()}} and \code{\link[=dbExecute]{dbExecute()}}. Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQuery}()} } \concept{DBIConnection generics} \concept{data retrieval generics} DBI/man/dbGetStatement.Rd0000644000176200001440000000327614552712323014640 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbGetStatement.R \name{dbGetStatement} \alias{dbGetStatement} \title{Get the statement associated with a result set} \usage{ dbGetStatement(res, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbGetStatement()} returns a string, the query used in either \code{\link[=dbSendQuery]{dbSendQuery()}} or \code{\link[=dbSendStatement]{dbSendStatement()}}. } \description{ Returns the statement that was passed to \code{\link[=dbSendQuery]{dbSendQuery()}} or \code{\link[=dbSendStatement]{dbSendStatement()}}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbGetStatement")} } \section{Failure modes}{ Attempting to query the statement for a result set cleared with \code{\link[=dbClearResult]{dbClearResult()}} gives an error. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQuery(con, "SELECT * FROM mtcars") dbGetStatement(rs) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} } \concept{DBIResult generics} DBI/man/dbSetDataMappings.Rd0000644000176200001440000000165114350241735015253 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbSetDataMappings.R \name{dbSetDataMappings} \alias{dbSetDataMappings} \title{Set data mappings between an DBMS and R.} \usage{ dbSetDataMappings(res, flds, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}.} \item{flds}{a field description object as returned by \code{dbColumnInfo}.} \item{...}{Other arguments passed on to methods.} } \description{ This generic is deprecated since no working implementation was ever produced. } \details{ Sets one or more conversion functions to handle the translation of DBMS data types to R objects. This is only needed for non-primitive data, since all DBI drivers handle the common base types (integers, numeric, strings, etc.) The details on conversion functions (e.g., arguments, whether they can invoke initializers and/or destructors) have not been specified. } \keyword{internal} DBI/man/dbColumnInfo.Rd0000644000176200001440000001067514552712323014306 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbColumnInfo.R \name{dbColumnInfo} \alias{dbColumnInfo} \title{Information about result types} \usage{ dbColumnInfo(res, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbColumnInfo()} returns a data frame with at least two columns \code{"name"} and \code{"type"} (in that order) (and optional columns that start with a dot). The \code{"name"} and \code{"type"} columns contain the names and types of the R columns of the data frame that is returned from \code{\link[=dbFetch]{dbFetch()}}. The \code{"type"} column is of type \code{character} and only for information. Do not compute on the \code{"type"} column, instead use \code{dbFetch(res, n = 0)} to create a zero-row data frame initialized with the correct data types. } \description{ Produces a data.frame that describes the output of a query. The data.frame should have as many rows as there are output fields in the result set, and each column in the data.frame describes an aspect of the result set field (field name, type, etc.) \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbColumnInfo")} } \section{The data retrieval flow}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbGetQuery]{dbGetQuery()}}, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQuery]{dbSendQuery()}} to create a result set object of class \linkS4class{DBIResult}. \item Optionally, bind query parameters with \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbColumnInfo]{dbColumnInfo()}} to retrieve the structure of the result set without retrieving actual data. \item Use \code{\link[=dbFetch]{dbFetch()}} to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. \item Use \code{\link[=dbHasCompleted]{dbHasCompleted()}} to tell when you're done. This method returns \code{TRUE} if no more rows are available for fetching. \item Repeat the last four steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ An attempt to query columns for a closed result set raises an error. } \section{Specification}{ A column named \code{row_names} is treated like any other column. The column names are always consistent with the data returned by \code{dbFetch()}. If the query returns unnamed columns, non-empty and non-\code{NA} names are assigned. Column names that correspond to SQL or R keywords are left unchanged. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") rs <- dbSendQuery(con, "SELECT 1 AS a, 2 AS b") dbColumnInfo(rs) dbFetch(rs) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} } \concept{DBIResult generics} DBI/man/dbListTables.Rd0000644000176200001440000000467614552712323014307 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbListTables.R \name{dbListTables} \alias{dbListTables} \title{List remote tables} \usage{ dbListTables(conn, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbListTables()} returns a character vector that enumerates all tables and views in the database. Tables added with \code{\link[=dbWriteTable]{dbWriteTable()}} are part of the list. As soon a table is removed from the database, it is also removed from the list of database tables. The same applies to temporary tables if supported by the database. The returned names are suitable for quoting with \code{dbQuoteIdentifier()}. } \description{ Returns the unquoted names of remote tables accessible through this connection. This should include views and temporary objects, but not all database backends (in particular \pkg{RMariaDB} and \pkg{RMySQL}) support this. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbListTables")} } \section{Failure modes}{ An error is raised when calling this method for a closed or invalid connection. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbListTables(con) dbWriteTable(con, "mtcars", mtcars) dbListTables(con) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/sqlParseVariables.Rd0000644000176200001440000000315414350241735015344 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/interpolate.R, R/sqlParseVariables.R \name{sqlCommentSpec} \alias{sqlCommentSpec} \alias{sqlQuoteSpec} \alias{sqlParseVariablesImpl} \alias{sqlParseVariables} \title{Parse interpolated variables from SQL.} \usage{ sqlCommentSpec(start, end, endRequired) sqlQuoteSpec(start, end, escape = "", doubleEscape = TRUE) sqlParseVariablesImpl(sql, quotes, comments) sqlParseVariables(conn, sql, ...) } \arguments{ \item{start, end}{Start and end characters for quotes and comments} \item{endRequired}{Is the ending character of a comment required?} \item{escape}{What character can be used to escape quoting characters? Defaults to \code{""}, i.e. nothing.} \item{doubleEscape}{Can quoting characters be escaped by doubling them? Defaults to \code{TRUE}.} \item{sql}{SQL to parse (a character string)} \item{quotes}{A list of \code{QuoteSpec} calls defining the quoting specification.} \item{comments}{A list of \code{CommentSpec} calls defining the commenting specification.} } \description{ If you're implementing a backend that uses non-ANSI quoting or commenting rules, you'll need to implement a method for \code{sqlParseVariables} that calls \code{sqlParseVariablesImpl} with the appropriate quote and comment specifications. } \examples{ # Use [] for quoting and no comments sqlParseVariablesImpl("[?a]", list(sqlQuoteSpec("[", "]", "\\\\", FALSE)), list() ) # Standard quotes, use # for commenting sqlParseVariablesImpl("# ?a\n?b", list(sqlQuoteSpec("'", "'"), sqlQuoteSpec('"', '"')), list(sqlCommentSpec("#", "\n", FALSE)) ) } \keyword{internal} DBI/man/dbDriver.Rd0000644000176200001440000000471314552712201013457 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbDriver.R, R/dbUnloadDriver.R \name{dbDriver} \alias{dbDriver} \alias{dbUnloadDriver} \title{Load and unload database drivers} \usage{ dbDriver(drvName, ...) dbUnloadDriver(drv, ...) } \arguments{ \item{drvName}{character name of the driver to instantiate.} \item{...}{any other arguments are passed to the driver \code{drvName}.} \item{drv}{an object that inherits from \code{DBIDriver} as created by \code{dbDriver}.} } \value{ In the case of \code{dbDriver}, an driver object whose class extends \code{DBIDriver}. This object may be used to create connections to the actual DBMS engine. In the case of \code{dbUnloadDriver}, a logical indicating whether the operation succeeded or not. } \description{ These methods are deprecated, please consult the documentation of the individual backends for the construction of driver instances. \code{dbDriver()} is a helper method used to create an new driver object given the name of a database or the corresponding R package. It works through convention: all DBI-extending packages should provide an exported object with the same name as the package. \code{dbDriver()} just looks for this object in the right places: if you know what database you are connecting to, you should call the function directly. \code{dbUnloadDriver()} is not implemented for modern backends. } \details{ The client part of the database communication is initialized (typically dynamically loading C code, etc.) but note that connecting to the database engine itself needs to be done through calls to \code{dbConnect}. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # Create a RSQLite driver with a string d <- dbDriver("SQLite") d # But better, access the object directly RSQLite::SQLite() \dontshow{\}) # examplesIf} } \seealso{ Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbCanConnect}()}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListConnections}()} Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbCanConnect}()}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListConnections}()} } \concept{DBIDriver generics} \keyword{internal} DBI/man/dbDisconnect.Rd0000644000176200001440000000412114552712323014313 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbDisconnect.R \name{dbDisconnect} \alias{dbDisconnect} \title{Disconnect (close) a connection} \usage{ dbDisconnect(conn, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbDisconnect()} returns \code{TRUE}, invisibly. } \description{ This closes the connection, discards all pending work, and frees resources (e.g., memory, sockets). \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbDisconnect")} } \section{Failure modes}{ A warning is issued on garbage collection when a connection has been released without calling \code{dbDisconnect()}, but this cannot be tested automatically. A warning is issued immediately when calling \code{dbDisconnect()} on an already disconnected or invalid connection. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbClearResult.Rd0000644000176200001440000001454014552712323014455 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbClearResult.R \name{dbClearResult} \alias{dbClearResult} \title{Clear a result set} \usage{ dbClearResult(res, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbClearResult()} returns \code{TRUE}, invisibly, for result sets obtained from \code{dbSendQuery()}, \code{dbSendStatement()}, or \code{dbSendQueryArrow()}, } \description{ Frees all resources (local and remote) associated with a result set. This step is mandatory for all objects obtained by calling \code{\link[=dbSendQuery]{dbSendQuery()}} or \code{\link[=dbSendStatement]{dbSendStatement()}}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbClearResult")} } \section{The data retrieval flow}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbGetQuery]{dbGetQuery()}}, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQuery]{dbSendQuery()}} to create a result set object of class \linkS4class{DBIResult}. \item Optionally, bind query parameters with \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbColumnInfo]{dbColumnInfo()}} to retrieve the structure of the result set without retrieving actual data. \item Use \code{\link[=dbFetch]{dbFetch()}} to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. \item Use \code{\link[=dbHasCompleted]{dbHasCompleted()}} to tell when you're done. This method returns \code{TRUE} if no more rows are available for fetching. \item Repeat the last four steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{The command execution flow}{ This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbExecute]{dbExecute()}}, which should be sufficient for non-parameterized queries. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendStatement]{dbSendStatement()}} to create a result set object of class \linkS4class{DBIResult}. For some queries you need to pass \code{immediate = TRUE}. \item Optionally, bind query parameters with\code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}} to retrieve the number of rows affected by the query. \item Repeat the last two steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ An attempt to close an already closed result set issues a warning for \code{dbSendQuery()}, \code{dbSendStatement()}, and \code{dbSendQueryArrow()}, } \section{Specification}{ \code{dbClearResult()} frees all resources associated with retrieving the result of a query or update operation. The DBI backend can expect a call to \code{dbClearResult()} for each \code{\link[=dbSendQuery]{dbSendQuery()}} or \code{\link[=dbSendStatement]{dbSendStatement()}} call. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") rs <- dbSendQuery(con, "SELECT 1") print(dbFetch(rs)) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} Other DBIResultArrow generics: \code{\link{DBIResultArrow-class}}, \code{\link{dbBind}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsValid}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()} Other command execution generics: \code{\link{dbBind}()}, \code{\link{dbExecute}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbSendStatement}()} } \concept{DBIResult generics} \concept{DBIResultArrow generics} \concept{command execution generics} \concept{data retrieval generics} DBI/man/dbReadTableArrow.Rd0000644000176200001440000000745214552712323015072 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbReadTableArrow.R \name{dbReadTableArrow} \alias{dbReadTableArrow} \title{Read database tables as Arrow objects} \usage{ dbReadTableArrow(conn, name, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbReadTableArrow()} returns an Arrow object that contains the complete data from the remote table, effectively the result of calling \code{\link[=dbGetQueryArrow]{dbGetQueryArrow()}} with \verb{SELECT * FROM }. An empty table is returned as an Arrow object with zero rows. } \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} Reads a database table as an Arrow object. Use \code{\link[=dbReadTable]{dbReadTable()}} instead to obtain a data frame. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbReadTableArrow")} } \details{ This function returns an Arrow object. Convert it to a data frame with \code{\link[=as.data.frame]{as.data.frame()}} or use \code{\link[=dbReadTable]{dbReadTable()}} to obtain a data frame. } \section{Failure modes}{ An error is raised if the table does not exist. An error is raised when calling this method for a closed or invalid connection. An error is raised if \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. } \section{Specification}{ The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbReadTableArrow()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # Read data as Arrow table con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars[1:10, ]) dbReadTableArrow(con, "mtcars") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/DBI-package.Rd0000644000176200001440000000506214552712323013710 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/DBI-package.R \docType{package} \name{DBI-package} \alias{DBI} \alias{DBI-package} \title{DBI: R Database Interface} \description{ DBI defines an interface for communication between R and relational database management systems. All classes in this package are virtual and need to be extended by the various R/DBMS implementations (so-called \emph{DBI backends}). } \section{Definition}{ A DBI backend is an R package which imports the \pkg{DBI} and \pkg{methods} packages. For better or worse, the names of many existing backends start with \sQuote{R}, e.g., \pkg{RSQLite}, \pkg{RMySQL}, \pkg{RSQLServer}; it is up to the backend author to adopt this convention or not. } \section{DBI classes and methods}{ A backend defines three classes, which are subclasses of \linkS4class{DBIDriver}, \linkS4class{DBIConnection}, and \linkS4class{DBIResult}. The backend provides implementation for all methods of these base classes that are defined but not implemented by DBI. All methods defined in \pkg{DBI} are reexported (so that the package can be used without having to attach \pkg{DBI}), and have an ellipsis \code{...} in their formals for extensibility. } \section{Construction of the DBIDriver object}{ The backend must support creation of an instance of its \linkS4class{DBIDriver} subclass with a \dfn{constructor function}. By default, its name is the package name without the leading \sQuote{R} (if it exists), e.g., \code{SQLite} for the \pkg{RSQLite} package. However, backend authors may choose a different name. The constructor must be exported, and it must be a function that is callable without arguments. DBI recommends to define a constructor with an empty argument list. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} RSQLite::SQLite() \dontshow{\}) # examplesIf} } \seealso{ Important generics: \code{\link[=dbConnect]{dbConnect()}}, \code{\link[=dbGetQuery]{dbGetQuery()}}, \code{\link[=dbReadTable]{dbReadTable()}}, \code{\link[=dbWriteTable]{dbWriteTable()}}, \code{\link[=dbDisconnect]{dbDisconnect()}} Formal specification (currently work in progress and incomplete): \code{vignette("spec", package = "DBI")} } \author{ \strong{Maintainer}: Kirill Müller \email{kirill@cynkra.com} (\href{https://orcid.org/0000-0002-1416-3412}{ORCID}) Authors: \itemize{ \item R Special Interest Group on Databases (R-SIG-DB) \item Hadley Wickham } Other contributors: \itemize{ \item R Consortium [funder] } } DBI/man/dbWithTransaction.Rd0000644000176200001440000000663714552712201015354 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbWithTransaction.R, % R/dbWithTransaction_DBIConnection.R \name{dbWithTransaction} \alias{dbWithTransaction} \alias{dbBreak} \title{Self-contained SQL transactions} \usage{ dbWithTransaction(conn, code, ...) dbBreak() } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{code}{An arbitrary block of R code.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbWithTransaction()} returns the value of the executed code. } \description{ Given that \link{transactions} are implemented, this function allows you to pass in code that is run in a transaction. The default method of \code{dbWithTransaction()} calls \code{\link[=dbBegin]{dbBegin()}} before executing the code, and \code{\link[=dbCommit]{dbCommit()}} after successful completion, or \code{\link[=dbRollback]{dbRollback()}} in case of an error. The advantage is that you don't have to remember to do \code{dbBegin()} and \code{dbCommit()} or \code{dbRollback()} -- that is all taken care of. The special function \code{dbBreak()} allows an early exit with rollback, it can be called only inside \code{dbWithTransaction()}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbWithTransaction")} } \details{ DBI implements \code{dbWithTransaction()}, backends should need to override this generic only if they implement specialized handling. } \section{Failure modes}{ Failure to initiate the transaction (e.g., if the connection is closed or invalid of if \code{\link[=dbBegin]{dbBegin()}} has been called already) gives an error. } \section{Specification}{ \code{dbWithTransaction()} initiates a transaction with \code{dbBegin()}, executes the code given in the \code{code} argument, and commits the transaction with \code{\link[=dbCommit]{dbCommit()}}. If the code raises an error, the transaction is instead aborted with \code{\link[=dbRollback]{dbRollback()}}, and the error is propagated. If the code calls \code{dbBreak()}, execution of the code stops and the transaction is silently aborted. All side effects caused by the code (such as the creation of new variables) propagate to the calling environment. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cash", data.frame(amount = 100)) dbWriteTable(con, "account", data.frame(amount = 2000)) # All operations are carried out as logical unit: dbWithTransaction( con, { withdrawal <- 300 dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) } ) # The code is executed as if in the curent environment: withdrawal # The changes are committed to the database after successful execution: dbReadTable(con, "cash") dbReadTable(con, "account") # Rolling back with dbBreak(): dbWithTransaction( con, { withdrawal <- 5000 dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) if (dbReadTable(con, "account")$amount < 0) { dbBreak() } } ) # These changes were not committed to the database: dbReadTable(con, "cash") dbReadTable(con, "account") dbDisconnect(con) \dontshow{\}) # examplesIf} } DBI/man/dbConnect.Rd0000644000176200001440000000751714552712201013622 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbConnect.R \name{dbConnect} \alias{dbConnect} \title{Create a connection to a DBMS} \usage{ dbConnect(drv, ...) } \arguments{ \item{drv}{an object that inherits from \linkS4class{DBIDriver}, or an existing \linkS4class{DBIConnection} object (in order to clone an existing connection).} \item{...}{authentication arguments needed by the DBMS instance; these typically include \code{user}, \code{password}, \code{host}, \code{port}, \code{dbname}, etc. For details see the appropriate \code{DBIDriver}.} } \value{ \code{dbConnect()} returns an S4 object that inherits from \linkS4class{DBIConnection}. This object is used to communicate with the database engine. A \code{\link[=format]{format()}} method is defined for the connection object. It returns a string that consists of a single line of text. } \description{ Connect to a DBMS going through the appropriate authentication procedure. Some implementations may allow you to have multiple connections open, so you may invoke this function repeatedly assigning its output to different objects. The authentication mechanism is left unspecified, so check the documentation of individual drivers for details. Use \code{\link[=dbCanConnect]{dbCanConnect()}} to check if a connection can be established. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbConnect")} } \section{Specification}{ DBI recommends using the following argument names for authentication parameters, with \code{NULL} default: \itemize{ \item \code{user} for the user name (default: current user) \item \code{password} for the password \item \code{host} for the host name (default: local connection) \item \code{port} for the port number (default: local connection) \item \code{dbname} for the name of the database on the host, or the database file name } The defaults should provide reasonable behavior, in particular a local connection for \code{host = NULL}. For some DBMS (e.g., PostgreSQL), this is different to a TCP/IP connection to \code{localhost}. In addition, DBI supports the \code{bigint} argument that governs how 64-bit integer data is returned. The following values are supported: \itemize{ \item \code{"integer"}: always return as \code{integer}, silently overflow \item \code{"numeric"}: always return as \code{numeric}, silently round \item \code{"character"}: always return the decimal representation as \code{character} \item \code{"integer64"}: return as a data type that can be coerced using \code{\link[=as.integer]{as.integer()}} (with warning on overflow), \code{\link[=as.numeric]{as.numeric()}} and \code{\link[=as.character]{as.character()}} } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # SQLite only needs a path to the database. (Here, ":memory:" is a special # path that creates an in-memory database.) Other database drivers # will require more details (like user, password, host, port, etc.) con <- dbConnect(RSQLite::SQLite(), ":memory:") con dbListTables(con) dbDisconnect(con) # Bad, for subtle reasons: # This code fails when RSQLite isn't loaded yet, # because dbConnect() doesn't know yet about RSQLite. dbListTables(con <- dbConnect(RSQLite::SQLite(), ":memory:")) \dontshow{\}) # examplesIf} } \seealso{ \code{\link[=dbDisconnect]{dbDisconnect()}} to disconnect from a database. Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbCanConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbDriver}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListConnections}()} Other DBIConnector generics: \code{\link{DBIConnector-class}}, \code{\link{dbDataType}()}, \code{\link{dbGetConnectArgs}()}, \code{\link{dbIsReadOnly}()} } \concept{DBIConnector generics} \concept{DBIDriver generics} DBI/man/figures/0000755000176200001440000000000014552712323013073 5ustar liggesusersDBI/man/figures/lifecycle-defunct.svg0000644000176200001440000000242414552712323017203 0ustar liggesusers lifecycle: defunct lifecycle defunct DBI/man/figures/lifecycle-maturing.svg0000644000176200001440000000243014552712323017376 0ustar liggesusers lifecycle: maturing lifecycle maturing DBI/man/figures/lifecycle-archived.svg0000644000176200001440000000243014552712323017335 0ustar liggesusers lifecycle: archived lifecycle archived DBI/man/figures/lifecycle-soft-deprecated.svg0000644000176200001440000000246614552712323020632 0ustar liggesusers lifecycle: soft-deprecated lifecycle soft-deprecated DBI/man/figures/lifecycle-questioning.svg0000644000176200001440000000244414552712323020122 0ustar liggesusers lifecycle: questioning lifecycle questioning DBI/man/figures/lifecycle-superseded.svg0000644000176200001440000000244014552712323017714 0ustar liggesusers lifecycle: superseded lifecycle superseded DBI/man/figures/lifecycle-stable.svg0000644000176200001440000000247214552712323017030 0ustar liggesusers lifecycle: stable lifecycle stable DBI/man/figures/lifecycle-experimental.svg0000644000176200001440000000245014552712323020247 0ustar liggesusers lifecycle: experimental lifecycle experimental DBI/man/figures/lifecycle-deprecated.svg0000644000176200001440000000244014552712323017651 0ustar liggesusers lifecycle: deprecated lifecycle deprecated DBI/man/rownames.Rd0000644000176200001440000000267714350241735013565 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/rownames.R \name{rownames} \alias{rownames} \alias{sqlRownamesToColumn} \alias{sqlColumnToRownames} \title{Convert row names back and forth between columns} \usage{ sqlRownamesToColumn(df, row.names = NA) sqlColumnToRownames(df, row.names = NA) } \arguments{ \item{df}{A data frame} \item{row.names}{Either \code{TRUE}, \code{FALSE}, \code{NA} or a string. If \code{TRUE}, always translate row names to a column called "row_names". If \code{FALSE}, never translate row names. If \code{NA}, translate rownames only if they're a character vector. A string is equivalent to \code{TRUE}, but allows you to override the default name. For backward compatibility, \code{NULL} is equivalent to \code{FALSE}.} } \description{ These functions provide a reasonably automatic way of preserving the row names of data frame during back-and-forth translation to an SQL table. By default, row names will be converted to an explicit column called "row_names", and any query returning a column called "row_names" will have those automatically set as row names. These methods are mostly useful for backend implementers. } \examples{ # If have row names sqlRownamesToColumn(head(mtcars)) sqlRownamesToColumn(head(mtcars), FALSE) sqlRownamesToColumn(head(mtcars), "ROWNAMES") # If don't have sqlRownamesToColumn(head(iris)) sqlRownamesToColumn(head(iris), TRUE) sqlRownamesToColumn(head(iris), "ROWNAMES") } DBI/man/DBIResult-class.Rd0000644000176200001440000000257214552712323014624 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/04-DBIResult.R \docType{class} \name{DBIResult-class} \alias{DBIResult-class} \title{DBIResult class} \description{ This virtual class describes the result and state of execution of a DBMS statement (any statement, query or non-query). The result set keeps track of whether the statement produces output how many rows were affected by the operation, how many rows have been fetched (if statement is a query), whether there are more rows to fetch, etc. } \section{Implementation notes}{ Individual drivers are free to allow single or multiple active results per connection. The default show method displays a summary of the query using other DBI generics. } \seealso{ Other DBI classes: \code{\link{DBIConnection-class}}, \code{\link{DBIConnector-class}}, \code{\link{DBIDriver-class}}, \code{\link{DBIObject-class}}, \code{\link{DBIResultArrow-class}} Other DBIResult generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} } \concept{DBI classes} \concept{DBIResult generics} DBI/man/dbExistsTable.Rd0000644000176200001440000000641114552712323014455 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbExistsTable.R \name{dbExistsTable} \alias{dbExistsTable} \title{Does a table exist?} \usage{ dbExistsTable(conn, name, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbExistsTable()} returns a logical scalar, \code{TRUE} if the table or view specified by the \code{name} argument exists, \code{FALSE} otherwise. This includes temporary tables if supported by the database. } \description{ Returns if a table given by name exists in the database. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbExistsTable")} } \section{Failure modes}{ An error is raised when calling this method for a closed or invalid connection. An error is also raised if \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. } \section{Specification}{ The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbExistsTable()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done } For all tables listed by \code{\link[=dbListTables]{dbListTables()}}, \code{dbExistsTable()} returns \code{TRUE}. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbExistsTable(con, "iris") dbWriteTable(con, "iris", iris) dbExistsTable(con, "iris") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbFetchArrowChunk.Rd0000644000176200001440000001046014552712323015262 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbFetchArrowChunk.R \name{dbFetchArrowChunk} \alias{dbFetchArrowChunk} \title{Fetch the next batch of records from a previously executed query as an Arrow object} \usage{ dbFetchArrowChunk(res, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResultArrow}, created by \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}}.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbFetchArrowChunk()} always returns an object coercible to a \link{data.frame} with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows. } \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} Fetch the next chunk of the result set and return it as an Arrow object. The chunk size is implementation-specific. Use \code{\link[=dbFetchArrow]{dbFetchArrow()}} to fetch all results. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbFetchArrowChunk")} } \section{The data retrieval flow for Arrow streams}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as an Arrow stream. Most of this flow, except repeated calling of \code{\link[=dbBindArrow]{dbBindArrow()}} or \code{\link[=dbBind]{dbBind()}}, is implemented by \code{\link[=dbGetQueryArrow]{dbGetQueryArrow()}}, which should be sufficient unless you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}} to create a result set object of class \linkS4class{DBIResultArrow}. \item Optionally, bind query parameters with \code{\link[=dbBindArrow]{dbBindArrow()}} or \code{\link[=dbBind]{dbBind()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Use \code{\link[=dbFetchArrow]{dbFetchArrow()}} to get a data stream. \item Repeat the last two steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ An attempt to fetch from a closed result set raises an error. } \section{Specification}{ Fetching multi-row queries with one or more columns returns the next chunk. The size of the chunk is implementation-specific. The object returned by \code{dbFetchArrowChunk()} can also be passed to \code{\link[nanoarrow:as_nanoarrow_array]{nanoarrow::as_nanoarrow_array()}} to create a nanoarrow array object. The chunk size is implementation-specific. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) # Fetch all results rs <- dbSendQueryArrow(con, "SELECT * FROM mtcars WHERE cyl = 4") dbHasCompleted(rs) as.data.frame(dbFetchArrowChunk(rs)) dbHasCompleted(rs) as.data.frame(dbFetchArrowChunk(rs)) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Close the result set with \code{\link[=dbClearResult]{dbClearResult()}} as soon as you finish retrieving the records you want. Other DBIResultArrow generics: \code{\link{DBIResultArrow-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsValid}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()} } \concept{DBIResultArrow generics} \concept{data retrieval generics} DBI/man/hidden_aliases.Rd0000644000176200001440000002737714552712323014672 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/06-ANSI.R, R/SQLKeywords_DBIObject.R, % R/SQLKeywords_missing.R, R/dbAppendTableArrow_DBIConnection.R, % R/dbAppendTable_DBIConnection.R, R/dbBindArrow_DBIResult.R, % R/dbBindArrow_DBIResultArrowDefault.R, R/dbBind_DBIResultArrow.R, % R/dbCanConnect_DBIDriver.R, R/dbClearResult_DBIResultArrow.R, % R/dbConnect_DBIConnector.R, R/dbCreateTableArrow_DBIConnection.R, % R/dbCreateTable_DBIConnection.R, R/dbDataType_DBIConnector.R, % R/dbDataType_DBIObject.R, R/dbDriver_character.R, % R/dbExecute_DBIConnection_character.R, R/dbExistsTable_DBIConnection_Id.R, % R/dbFetchArrowChunk_DBIResultArrow.R, R/dbFetchArrow_DBIResultArrow.R, % R/dbFetch_DBIResult.R, R/dbFetch_DBIResultArrow.R, % R/dbGetConnectArgs_DBIConnector.R, R/dbGetInfo_DBIResult.R, % R/dbGetInfo_DBIResultArrow.R, R/dbGetQueryArrow_DBIConnection.R, % R/dbGetQuery_DBIConnection_character.R, R/dbGetRowCount_DBIResultArrow.R, % R/dbGetRowsAffected_DBIResultArrow.R, R/dbGetStatement_DBIResultArrow.R, % R/dbHasCompleted_DBIResultArrow.R, R/dbIsReadOnly_DBIConnector.R, % R/dbIsReadOnly_DBIObject.R, R/dbIsValid_DBIResultArrowDefault.R, % R/dbListFields_DBIConnection_Id.R, R/dbListFields_DBIConnection_character.R, % R/dbListObjects_DBIConnection_ANY.R, R/dbQuoteIdentifier_DBIConnection.R, % R/dbQuoteLiteral_DBIConnection.R, R/dbQuoteString_DBIConnection.R, % R/dbReadTableArrow_DBIConnection.R, R/dbReadTable_DBIConnection_Id.R, % R/dbReadTable_DBIConnection_character.R, % R/dbRemoveTable_DBIConnection_Id.R, R/dbSendQueryArrow_DBIConnection.R, % R/dbSendStatement_DBIConnection_character.R, % R/dbUnquoteIdentifier_DBIConnection.R, R/dbWithTransaction_DBIConnection.R, % R/dbWriteTableArrow_DBIConnection.R, R/dbWriteTable_DBIConnection_Id_ANY.R, % R/isSQLKeyword_DBIObject_character.R, R/make.db.names_DBIObject_character.R, % R/show_AnsiConnection.R, R/show_DBIConnection.R, R/show_DBIConnector.R, % R/show_DBIDriver.R, R/show_DBIResult.R, R/show_Id.R, R/show_SQL.R, % R/sqlAppendTable_DBIConnection.R, R/sqlCreateTable_DBIConnection.R, % R/sqlData_DBIConnection.R, R/sqlInterpolate_DBIConnection.R, % R/sqlParseVariables_DBIConnection.R \docType{methods} \name{hidden_aliases} \alias{hidden_aliases} \alias{SQLKeywords_DBIObject} \alias{SQLKeywords,DBIObject-method} \alias{SQLKeywords_missing} \alias{SQLKeywords,missing-method} \alias{dbAppendTableArrow_DBIConnection} \alias{dbAppendTableArrow,DBIConnection-method} \alias{dbAppendTable_DBIConnection} \alias{dbAppendTable,DBIConnection-method} \alias{dbBindArrow_DBIResult} \alias{dbBindArrow,DBIResult-method} \alias{dbBindArrow_DBIResultArrowDefault} \alias{dbBindArrow,DBIResultArrowDefault-method} \alias{dbBind_DBIResultArrow} \alias{dbBind,DBIResultArrow-method} \alias{dbCanConnect_DBIDriver} \alias{dbCanConnect,DBIDriver-method} \alias{dbClearResult_DBIResultArrow} \alias{dbClearResult,DBIResultArrow-method} \alias{dbConnect_DBIConnector} \alias{dbConnect,DBIConnector-method} \alias{dbCreateTableArrow_DBIConnection} \alias{dbCreateTableArrow,DBIConnection-method} \alias{dbCreateTable_DBIConnection} \alias{dbCreateTable,DBIConnection-method} \alias{dbDataType_DBIConnector} \alias{dbDataType,DBIConnector-method} \alias{dbDataType_DBIObject} \alias{dbDataType,DBIObject-method} \alias{dbDriver_character} \alias{dbDriver,character-method} \alias{dbExecute_DBIConnection_character} \alias{dbExecute,DBIConnection,character-method} \alias{dbExistsTable_DBIConnection_Id} \alias{dbExistsTable,DBIConnection,Id-method} \alias{dbFetchArrowChunk_DBIResultArrow} \alias{dbFetchArrowChunk,DBIResultArrow-method} \alias{dbFetchArrow_DBIResultArrow} \alias{dbFetchArrow,DBIResultArrow-method} \alias{dbFetch_DBIResult} \alias{dbFetch,DBIResult-method} \alias{dbFetch_DBIResultArrow} \alias{dbFetch,DBIResultArrow-method} \alias{dbGetConnectArgs_DBIConnector} \alias{dbGetConnectArgs,DBIConnector-method} \alias{dbGetInfo_DBIResult} \alias{dbGetInfo,DBIResult-method} \alias{dbGetInfo_DBIResultArrow} \alias{dbGetInfo,DBIResultArrow-method} \alias{dbGetQueryArrow_DBIConnection_character} \alias{dbGetQueryArrow,DBIConnection-method} \alias{dbGetQuery_DBIConnection_character} \alias{dbGetQuery,DBIConnection,character-method} \alias{dbGetRowCount_DBIResultArrow} \alias{dbGetRowCount,DBIResultArrow-method} \alias{dbGetRowsAffected_DBIResultArrow} \alias{dbGetRowsAffected,DBIResultArrow-method} \alias{dbGetStatement_DBIResultArrow} \alias{dbGetStatement,DBIResultArrow-method} \alias{dbHasCompleted_DBIResultArrow} \alias{dbHasCompleted,DBIResultArrow-method} \alias{dbIsReadOnly_DBIConnector} \alias{dbIsReadOnly,DBIConnector-method} \alias{dbIsReadOnly_DBIObject} \alias{dbIsReadOnly,DBIObject-method} \alias{dbIsValid_DBIResultArrowDefault} \alias{dbIsValid,DBIResultArrowDefault-method} \alias{dbListFields_DBIConnection_Id} \alias{dbListFields,DBIConnection,Id-method} \alias{dbListFields_DBIConnection_character} \alias{dbListFields,DBIConnection,character-method} \alias{dbListObjects_DBIConnection_ANY} \alias{dbListObjects,DBIConnection-method} \alias{dbQuoteIdentifier_DBIConnection} \alias{dbQuoteIdentifier,DBIConnection,ANY-method} \alias{dbQuoteIdentifier,DBIConnection,character-method} \alias{dbQuoteIdentifier,DBIConnection,SQL-method} \alias{dbQuoteIdentifier,DBIConnection,Id-method} \alias{dbQuoteLiteral_DBIConnection} \alias{dbQuoteLiteral,DBIConnection-method} \alias{dbQuoteString_DBIConnection} \alias{dbQuoteString,DBIConnection,ANY-method} \alias{dbQuoteString,DBIConnection,character-method} \alias{dbQuoteString,DBIConnection,SQL-method} \alias{dbReadTableArrow_DBIConnection} \alias{dbReadTableArrow,DBIConnection-method} \alias{dbReadTable_DBIConnection_Id} \alias{dbReadTable,DBIConnection,Id-method} \alias{dbReadTable_DBIConnection_character} \alias{dbReadTable,DBIConnection,character-method} \alias{dbRemoveTable_DBIConnection_Id} \alias{dbRemoveTable,DBIConnection,Id-method} \alias{dbSendQueryArrow_DBIConnection} \alias{dbSendQueryArrow,DBIConnection-method} \alias{dbSendStatement_DBIConnection_character} \alias{dbSendStatement,DBIConnection,character-method} \alias{dbUnquoteIdentifier_DBIConnection} \alias{dbUnquoteIdentifier,DBIConnection-method} \alias{dbWithTransaction_DBIConnection} \alias{dbWithTransaction,DBIConnection-method} \alias{dbWriteTableArrow_DBIConnection} \alias{dbWriteTableArrow,DBIConnection-method} \alias{dbWriteTable_DBIConnection_Id_ANY} \alias{dbWriteTable,DBIConnection,Id-method} \alias{isSQLKeyword_DBIObject_character} \alias{isSQLKeyword,DBIObject,character-method} \alias{make.db.names_DBIObject_character} \alias{make.db.names,DBIObject,character-method} \alias{show_AnsiConnection} \alias{show,AnsiConnection-method} \alias{show_DBIConnection} \alias{show,DBIConnection-method} \alias{show_DBIConnector} \alias{show,DBIConnector-method} \alias{show_DBIDriver} \alias{show,DBIDriver-method} \alias{show_DBIResult} \alias{show,DBIResult-method} \alias{show_Id} \alias{show,Id-method} \alias{show_SQL} \alias{show,SQL-method} \alias{sqlAppendTable_DBIConnection} \alias{sqlAppendTable,DBIConnection-method} \alias{sqlCreateTable_DBIConnection} \alias{sqlCreateTable,DBIConnection-method} \alias{sqlData_DBIConnection} \alias{sqlData,DBIConnection-method} \alias{sqlInterpolate_DBIConnection} \alias{sqlInterpolate,DBIConnection-method} \alias{sqlParseVariables_DBIConnection} \alias{sqlParseVariables,DBIConnection-method} \title{Internal page for hidden aliases} \usage{ \S4method{SQLKeywords}{DBIObject}(dbObj, ...) \S4method{SQLKeywords}{missing}(dbObj, ...) \S4method{dbAppendTableArrow}{DBIConnection}(conn, name, value, ...) \S4method{dbAppendTable}{DBIConnection}(conn, name, value, ..., row.names = NULL) \S4method{dbBindArrow}{DBIResult}(res, params, ...) \S4method{dbBindArrow}{DBIResultArrowDefault}(res, params, ...) \S4method{dbBind}{DBIResultArrow}(res, params, ...) \S4method{dbCanConnect}{DBIDriver}(drv, ...) \S4method{dbClearResult}{DBIResultArrow}(res, ...) \S4method{dbConnect}{DBIConnector}(drv, ...) \S4method{dbCreateTableArrow}{DBIConnection}(conn, name, value, ..., temporary = FALSE) \S4method{dbCreateTable}{DBIConnection}(conn, name, fields, ..., row.names = NULL, temporary = FALSE) \S4method{dbDataType}{DBIConnector}(dbObj, obj, ...) \S4method{dbDataType}{DBIObject}(dbObj, obj, ...) \S4method{dbDriver}{character}(drvName, ...) \S4method{dbExecute}{DBIConnection,character}(conn, statement, ...) \S4method{dbExistsTable}{DBIConnection,Id}(conn, name, ...) \S4method{dbFetchArrowChunk}{DBIResultArrow}(res, ...) \S4method{dbFetchArrow}{DBIResultArrow}(res, ...) \S4method{dbFetch}{DBIResult}(res, n = -1, ...) \S4method{dbFetch}{DBIResultArrow}(res, n = -1, ...) \S4method{dbGetConnectArgs}{DBIConnector}(drv, eval = TRUE, ...) \S4method{dbGetInfo}{DBIResult}(dbObj, ...) \S4method{dbGetInfo}{DBIResultArrow}(dbObj, ...) \S4method{dbGetQueryArrow}{DBIConnection}(conn, statement, ...) \S4method{dbGetQuery}{DBIConnection,character}(conn, statement, ..., n = -1L) \S4method{dbGetRowCount}{DBIResultArrow}(res, ...) \S4method{dbGetRowsAffected}{DBIResultArrow}(res, ...) \S4method{dbGetStatement}{DBIResultArrow}(res, ...) \S4method{dbHasCompleted}{DBIResultArrow}(res, ...) \S4method{dbIsReadOnly}{DBIConnector}(dbObj, ...) \S4method{dbIsReadOnly}{DBIObject}(dbObj, ...) \S4method{dbIsValid}{DBIResultArrowDefault}(dbObj, ...) \S4method{dbListFields}{DBIConnection,Id}(conn, name, ...) \S4method{dbListFields}{DBIConnection,character}(conn, name, ...) \S4method{dbListObjects}{DBIConnection}(conn, prefix = NULL, ...) \S4method{dbQuoteIdentifier}{DBIConnection,ANY}(conn, x, ...) \S4method{dbQuoteIdentifier}{DBIConnection,character}(conn, x, ...) \S4method{dbQuoteIdentifier}{DBIConnection,SQL}(conn, x, ...) \S4method{dbQuoteIdentifier}{DBIConnection,Id}(conn, x, ...) \S4method{dbQuoteLiteral}{DBIConnection}(conn, x, ...) \S4method{dbQuoteString}{DBIConnection,ANY}(conn, x, ...) \S4method{dbQuoteString}{DBIConnection,character}(conn, x, ...) \S4method{dbQuoteString}{DBIConnection,SQL}(conn, x, ...) \S4method{dbReadTableArrow}{DBIConnection}(conn, name, ...) \S4method{dbReadTable}{DBIConnection,Id}(conn, name, ...) \S4method{dbReadTable}{DBIConnection,character}(conn, name, ..., row.names = FALSE, check.names = TRUE) \S4method{dbRemoveTable}{DBIConnection,Id}(conn, name, ...) \S4method{dbSendQueryArrow}{DBIConnection}(conn, statement, params = NULL, ...) \S4method{dbSendStatement}{DBIConnection,character}(conn, statement, ...) \S4method{dbUnquoteIdentifier}{DBIConnection}(conn, x, ...) \S4method{dbWithTransaction}{DBIConnection}(conn, code) \S4method{dbWriteTableArrow}{DBIConnection}( conn, name, value, append = FALSE, overwrite = FALSE, ..., temporary = FALSE ) \S4method{dbWriteTable}{DBIConnection,Id}(conn, name, value, ...) \S4method{isSQLKeyword}{DBIObject,character}( dbObj, name, keywords = .SQL92Keywords, case = c("lower", "upper", "any")[3], ... ) \S4method{make.db.names}{DBIObject,character}( dbObj, snames, keywords = .SQL92Keywords, unique = TRUE, allow.keywords = TRUE, ... ) \S4method{show}{AnsiConnection}(object) \S4method{show}{DBIConnection}(object) \S4method{show}{DBIConnector}(object) \S4method{show}{DBIDriver}(object) \S4method{show}{DBIResult}(object) \S4method{show}{Id}(object) \S4method{show}{SQL}(object) \S4method{sqlAppendTable}{DBIConnection}(con, table, values, row.names = NA, ...) \S4method{sqlCreateTable}{DBIConnection}(con, table, fields, row.names = NA, temporary = FALSE, ...) \S4method{sqlData}{DBIConnection}(con, value, row.names = NA, ...) \S4method{sqlInterpolate}{DBIConnection}(conn, sql, ..., .dots = list()) \S4method{sqlParseVariables}{DBIConnection}(conn, sql, ...) } \arguments{ \item{n}{Number of rows to fetch, default -1} \item{object}{Table object to print} } \description{ For S4 methods that require a documentation entry but only clutter the index. } \keyword{internal} DBI/man/make.db.names.Rd0000644000176200001440000000671014350241735014325 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/deprecated.R, R/isSQLKeyword.R, % R/make.db.names.R \name{make.db.names.default} \alias{make.db.names.default} \alias{isSQLKeyword.default} \alias{isSQLKeyword} \alias{make.db.names} \alias{SQLKeywords} \title{Make R identifiers into legal SQL identifiers} \usage{ make.db.names.default( snames, keywords = .SQL92Keywords, unique = TRUE, allow.keywords = TRUE ) isSQLKeyword.default( name, keywords = .SQL92Keywords, case = c("lower", "upper", "any")[3] ) isSQLKeyword( dbObj, name, keywords = .SQL92Keywords, case = c("lower", "upper", "any")[3], ... ) make.db.names( dbObj, snames, keywords = .SQL92Keywords, unique = TRUE, allow.keywords = TRUE, ... ) } \arguments{ \item{snames}{a character vector of R identifiers (symbols) from which we need to make SQL identifiers.} \item{keywords}{a character vector with SQL keywords, by default it's \code{.SQL92Keywords} defined by the DBI.} \item{unique}{logical describing whether the resulting set of SQL names should be unique. Its default is \code{TRUE}. Following the SQL 92 standard, uniqueness of SQL identifiers is determined regardless of whether letters are upper or lower case.} \item{allow.keywords}{logical describing whether SQL keywords should be allowed in the resulting set of SQL names. Its default is \code{TRUE}} \item{name}{a character vector with database identifier candidates we need to determine whether they are legal SQL identifiers or not.} \item{case}{a character string specifying whether to make the comparison as lower case, upper case, or any of the two. it defaults to \code{any}.} \item{dbObj}{any DBI object (e.g., \code{DBIDriver}).} \item{\dots}{any other argument are passed to the driver implementation.} } \value{ \code{make.db.names} returns a character vector of legal SQL identifiers corresponding to its \code{snames} argument. \code{SQLKeywords} returns a character vector of all known keywords for the database-engine associated with \code{dbObj}. \code{isSQLKeyword} returns a logical vector parallel to \code{name}. } \description{ These methods are DEPRECATED. Please use \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} (or possibly \code{\link[=dbQuoteString]{dbQuoteString()}}) instead. } \details{ The algorithm in \code{make.db.names} first invokes \code{make.names} and then replaces each occurrence of a dot \code{.} by an underscore \verb{_}. If \code{allow.keywords} is \code{FALSE} and identifiers collide with SQL keywords, a small integer is appended to the identifier in the form of \code{"_n"}. The set of SQL keywords is stored in the character vector \code{.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. } \section{Bugs}{ The current mapping is not guaranteed to be fully reversible: some SQL identifiers that get mapped into R identifiers with \code{make.names} and then back to SQL with \code{\link[=make.db.names]{make.db.names()}} will not be equal to the original SQL identifiers (e.g., compound SQL identifiers of the form \code{username.tablename} will loose the dot ``.''). } \references{ The set of SQL keywords is stored in the character vector \code{.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. } \keyword{internal} DBI/man/dbGetRowsAffected.Rd0000644000176200001440000000746414552712323015253 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbGetRowsAffected.R \name{dbGetRowsAffected} \alias{dbGetRowsAffected} \title{The number of rows affected} \usage{ dbGetRowsAffected(res, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbGetRowsAffected()} returns a scalar number (integer or numeric), the number of rows affected by a data manipulation statement issued with \code{\link[=dbSendStatement]{dbSendStatement()}}. The value is available directly after the call and does not change after calling \code{\link[=dbFetch]{dbFetch()}}. \code{NA_integer_} or \code{NA_numeric_} are allowed if the number of rows affected is not known. For queries issued with \code{\link[=dbSendQuery]{dbSendQuery()}}, zero is returned before and after the call to \code{dbFetch()}. \code{NA} values are not allowed. } \description{ This method returns the number of rows that were added, deleted, or updated by a data manipulation statement. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbGetRowsAffected")} } \section{The command execution flow}{ This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbExecute]{dbExecute()}}, which should be sufficient for non-parameterized queries. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendStatement]{dbSendStatement()}} to create a result set object of class \linkS4class{DBIResult}. For some queries you need to pass \code{immediate = TRUE}. \item Optionally, bind query parameters with\code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}} to retrieve the number of rows affected by the query. \item Repeat the last two steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ Attempting to get the rows affected for a result set cleared with \code{\link[=dbClearResult]{dbClearResult()}} gives an error. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendStatement(con, "DELETE FROM mtcars") dbGetRowsAffected(rs) nrow(mtcars) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} Other command execution generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbExecute}()}, \code{\link{dbSendStatement}()} } \concept{DBIResult generics} \concept{command execution generics} DBI/man/dbListObjects.Rd0000644000176200001440000001072014552712323014451 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbListObjects.R \name{dbListObjects} \alias{dbListObjects} \title{List remote objects} \usage{ dbListObjects(conn, prefix = NULL, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{prefix}{A fully qualified path in the database's namespace, or \code{NULL}. This argument will be processed with \code{\link[=dbUnquoteIdentifier]{dbUnquoteIdentifier()}}. If given the method will return all objects accessible through this prefix.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbListObjects()} returns a data frame with columns \code{table} and \code{is_prefix} (in that order), optionally with other columns with a dot (\code{.}) prefix. The \code{table} column is of type list. Each object in this list is suitable for use as argument in \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. The \code{is_prefix} column is a logical. This data frame contains one row for each object (schema, table and view) accessible from the prefix (if passed) or from the global namespace (if prefix is omitted). Tables added with \code{\link[=dbWriteTable]{dbWriteTable()}} are part of the data frame. As soon a table is removed from the database, it is also removed from the data frame of database objects. The same applies to temporary objects if supported by the database. The returned names are suitable for quoting with \code{dbQuoteIdentifier()}. } \description{ Returns the names of remote objects accessible through this connection as a data frame. This should include temporary objects, but not all database backends (in particular \pkg{RMariaDB} and \pkg{RMySQL}) support this. Compared to \code{\link[=dbListTables]{dbListTables()}}, this method also enumerates tables and views in schemas, and returns fully qualified identifiers to access these objects. This allows exploration of all database objects available to the current user, including those that can only be accessed by giving the full namespace. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbListObjects")} } \section{Failure modes}{ An error is raised when calling this method for a closed or invalid connection. } \section{Specification}{ The \code{prefix} column indicates if the \code{table} value refers to a table or a prefix. For a call with the default \code{prefix = NULL}, the \code{table} values that have \code{is_prefix == FALSE} correspond to the tables returned from \code{\link[=dbListTables]{dbListTables()}}, The \code{table} object can be quoted with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. The result of quoting can be passed to \code{\link[=dbUnquoteIdentifier]{dbUnquoteIdentifier()}}. (For backends it may be convenient to use the \link{Id} class, but this is not required.) Values in \code{table} column that have \code{is_prefix == TRUE} can be passed as the \code{prefix} argument to another call to \code{dbListObjects()}. For the data frame returned from a \code{dbListObject()} call with the \code{prefix} argument set, all \code{table} values where \code{is_prefix} is \code{FALSE} can be used in a call to \code{\link[=dbExistsTable]{dbExistsTable()}} which returns \code{TRUE}. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbListObjects(con) dbWriteTable(con, "mtcars", mtcars) dbListObjects(con) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbListFields.Rd0000644000176200001440000000640114552712323014267 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbListFields.R \name{dbListFields} \alias{dbListFields} \title{List field names of a remote table} \usage{ dbListFields(conn, name, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbListFields()} returns a character vector that enumerates all fields in the table in the correct order. This also works for temporary tables if supported by the database. The returned names are suitable for quoting with \code{dbQuoteIdentifier()}. } \description{ Returns the field names of a remote table as a character vector. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbListFields")} } \section{Failure modes}{ If the table does not exist, an error is raised. Invalid types for the \code{name} argument (e.g., \code{character} of length not equal to one, or numeric) lead to an error. An error is also raised when calling this method for a closed or invalid connection. } \section{Specification}{ The \code{name} argument can be \itemize{ \item a string \item the return value of \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} \item a value from the \code{table} column from the return value of \code{\link[=dbListObjects]{dbListObjects()}} where \code{is_prefix} is \code{FALSE} } A column named \code{row_names} is treated like any other column. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) dbListFields(con, "mtcars") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ \code{\link[=dbColumnInfo]{dbColumnInfo()}} to get the type of the fields. Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbDataType.Rd0000644000176200001440000001200214552712323013732 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbDataType.R \name{dbDataType} \alias{dbDataType} \title{Determine the SQL data type of an object} \usage{ dbDataType(dbObj, obj, ...) } \arguments{ \item{dbObj}{A object inheriting from \linkS4class{DBIDriver} or \linkS4class{DBIConnection}} \item{obj}{An R object whose SQL type we want to determine.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbDataType()} returns the SQL type that corresponds to the \code{obj} argument as a non-empty character string. For data frames, a character vector with one element per column is returned. } \description{ Returns an SQL string that describes the SQL data type to be used for an object. The default implementation of this generic determines the SQL type of an R object according to the SQL 92 specification, which may serve as a starting point for driver implementations. DBI also provides an implementation for data.frame which will return a character vector giving the type for each column in the dataframe. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbDataType")} } \details{ The data types supported by databases are different than the data types in R, but the mapping between the primitive types is straightforward: \itemize{ \item Any of the many fixed and varying length character types are mapped to character vectors \item Fixed-precision (non-IEEE) numbers are mapped into either numeric or integer vectors. } Notice that many DBMS do not follow IEEE arithmetic, so there are potential problems with under/overflows and loss of precision. } \section{Failure modes}{ An error is raised for invalid values for the \code{obj} argument such as a \code{NULL} value. } \section{Specification}{ The backend can override the \code{\link[=dbDataType]{dbDataType()}} generic for its driver class. This generic expects an arbitrary object as second argument. To query the values returned by the default implementation, run \code{example(dbDataType, package = "DBI")}. If the backend needs to override this generic, it must accept all basic R data types as its second argument, namely \link{logical}, \link{integer}, \link{numeric}, \link{character}, dates (see \link{Dates}), date-time (see \link{DateTimeClasses}), and \link{difftime}. If the database supports blobs, this method also must accept lists of \link{raw} vectors, and \link[blob:blob]{blob::blob} objects. As-is objects (i.e., wrapped by \code{\link[=I]{I()}}) must be supported and return the same results as their unwrapped counterparts. The SQL data type for \link{factor} and \link{ordered} is the same as for character. The behavior for other object types is not specified. All data types returned by \code{dbDataType()} are usable in an SQL statement of the form \code{"CREATE TABLE test (a ...)"}. } \examples{ dbDataType(ANSI(), 1:5) dbDataType(ANSI(), 1) dbDataType(ANSI(), TRUE) dbDataType(ANSI(), Sys.Date()) dbDataType(ANSI(), Sys.time()) dbDataType(ANSI(), Sys.time() - as.POSIXct(Sys.Date())) dbDataType(ANSI(), c("x", "abc")) dbDataType(ANSI(), list(raw(10), raw(20))) dbDataType(ANSI(), I(3)) dbDataType(ANSI(), iris) \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbDataType(con, 1:5) dbDataType(con, 1) dbDataType(con, TRUE) dbDataType(con, Sys.Date()) dbDataType(con, Sys.time()) dbDataType(con, Sys.time() - as.POSIXct(Sys.Date())) dbDataType(con, c("x", "abc")) dbDataType(con, list(raw(10), raw(20))) dbDataType(con, I(3)) dbDataType(con, iris) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbCanConnect}()}, \code{\link{dbConnect}()}, \code{\link{dbDriver}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListConnections}()} Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other DBIConnector generics: \code{\link{DBIConnector-class}}, \code{\link{dbConnect}()}, \code{\link{dbGetConnectArgs}()}, \code{\link{dbIsReadOnly}()} } \concept{DBIConnection generics} \concept{DBIConnector generics} \concept{DBIDriver generics} DBI/man/dbRemoveTable.Rd0000644000176200001440000001036414552712323014435 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbRemoveTable.R \name{dbRemoveTable} \alias{dbRemoveTable} \title{Remove a table from the database} \usage{ dbRemoveTable(conn, name, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbRemoveTable()} returns \code{TRUE}, invisibly. } \description{ Remove a remote table (e.g., created by \code{\link[=dbWriteTable]{dbWriteTable()}}) from the database. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbRemoveTable")} } \section{Failure modes}{ If the table does not exist, an error is raised. An attempt to remove a view with this function may result in an error. An error is raised when calling this method for a closed or invalid connection. An error is also raised if \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. } \section{Additional arguments}{ The following arguments are not part of the \code{dbRemoveTable()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{temporary} (default: \code{FALSE}) \item \code{fail_if_missing} (default: \code{TRUE}) } These arguments must be provided as named arguments. If \code{temporary} is \code{TRUE}, the call to \code{dbRemoveTable()} will consider only temporary tables. Not all backends support this argument. In particular, permanent tables of the same name are left untouched. If \code{fail_if_missing} is \code{FALSE}, the call to \code{dbRemoveTable()} succeeds if the table does not exist. } \section{Specification}{ A table removed by \code{dbRemoveTable()} doesn't appear in the list of tables returned by \code{\link[=dbListTables]{dbListTables()}}, and \code{\link[=dbExistsTable]{dbExistsTable()}} returns \code{FALSE}. The removal propagates immediately to other connections to the same database. This function can also be used to remove a temporary table. The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbRemoveTable()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbExistsTable(con, "iris") dbWriteTable(con, "iris", iris) dbExistsTable(con, "iris") dbRemoveTable(con, "iris") dbExistsTable(con, "iris") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbAppendTableArrow.Rd0000644000176200001440000001326014552712323015420 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/21-dbAppendTableArrow.R \name{dbAppendTableArrow} \alias{dbAppendTableArrow} \title{Insert rows into a table from an Arrow stream} \usage{ dbAppendTableArrow(conn, name, value, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{value}{An object coercible with \code{\link[nanoarrow:as_nanoarrow_array_stream]{nanoarrow::as_nanoarrow_array_stream()}}.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbAppendTableArrow()} returns a scalar numeric. } \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} The \code{dbAppendTableArrow()} method assumes that the table has been created beforehand, e.g. with \code{\link[=dbCreateTableArrow]{dbCreateTableArrow()}}. The default implementation calls \code{\link[=dbAppendTable]{dbAppendTable()}} for each chunk of the stream. Use \code{\link[=dbAppendTable]{dbAppendTable()}} to append data from a data.frame. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbAppendTableArrow")} } \section{Failure modes}{ If the table does not exist, or the new data in \code{values} is not a data frame or has different column names, 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 \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. } \section{Specification}{ SQL keywords can be used freely in table names, column names, and data. Quotes, commas, spaces, and other special characters such as newlines and tabs, can also be used in the data, and, if the database supports non-syntactic identifiers, also for table names and column names. The following data types must be supported at least, and be read identically with \code{\link[=dbReadTable]{dbReadTable()}}: \itemize{ \item integer \item numeric (the behavior for \code{Inf} and \code{NaN} is not specified) \item logical \item \code{NA} as NULL \item 64-bit values (using \code{"bigint"} as field type); the result can be \itemize{ \item converted to a numeric, which may lose precision, \item converted a character vector, which gives the full decimal representation \item written to another table and read again unchanged } \item character (in both UTF-8 and native encodings), supporting empty strings (before and after non-empty strings) \item factor (possibly returned as character) \item objects of type \link[blob:blob]{blob::blob} (if supported by the database) \item date (if supported by the database; returned as \code{Date}) also for dates prior to 1970 or 1900 or after 2038 \item time (if supported by the database; returned as objects that inherit from \code{difftime}) \item timestamp (if supported by the database; returned as \code{POSIXct} respecting the time zone but not necessarily preserving the input time zone), also for timestamps prior to 1970 or 1900 or after 2038 respecting the time zone but not necessarily preserving the input time zone) } Mixing column types in the same table is supported. The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbAppendTableArrow()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done to support databases that allow non-syntactic names for their objects: } The \code{value} argument must be a data frame with a subset of the columns of the existing table. The order of the columns does not matter. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbCreateTableArrow(con, "iris", iris[0, ]) dbAppendTableArrow(con, "iris", iris[1:5, ]) dbReadTable(con, "iris") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbFetchArrow.Rd0000644000176200001440000001025414552712323014272 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbFetchArrow.R \name{dbFetchArrow} \alias{dbFetchArrow} \title{Fetch records from a previously executed query as an Arrow object} \usage{ dbFetchArrow(res, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResultArrow}, created by \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}}.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbFetchArrow()} always returns an object coercible to a \link{data.frame} with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows. } \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} Fetch the result set and return it as an Arrow object. Use \code{\link[=dbFetchArrowChunk]{dbFetchArrowChunk()}} to fetch results in chunks. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbFetchArrow")} } \section{The data retrieval flow for Arrow streams}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as an Arrow stream. Most of this flow, except repeated calling of \code{\link[=dbBindArrow]{dbBindArrow()}} or \code{\link[=dbBind]{dbBind()}}, is implemented by \code{\link[=dbGetQueryArrow]{dbGetQueryArrow()}}, which should be sufficient unless you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}} to create a result set object of class \linkS4class{DBIResultArrow}. \item Optionally, bind query parameters with \code{\link[=dbBindArrow]{dbBindArrow()}} or \code{\link[=dbBind]{dbBind()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Use \code{\link[=dbFetchArrow]{dbFetchArrow()}} to get a data stream. \item Repeat the last two steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ An attempt to fetch from a closed result set raises an error. } \section{Specification}{ Fetching multi-row queries with one or more columns by default returns the entire result. The object returned by \code{dbFetchArrow()} can also be passed to \code{\link[nanoarrow:as_nanoarrow_array_stream]{nanoarrow::as_nanoarrow_array_stream()}} to create a nanoarrow array stream object that can be used to read the result set in batches. The chunk size is implementation-specific. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) # Fetch all results rs <- dbSendQueryArrow(con, "SELECT * FROM mtcars WHERE cyl = 4") as.data.frame(dbFetchArrow(rs)) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Close the result set with \code{\link[=dbClearResult]{dbClearResult()}} as soon as you finish retrieving the records you want. Other DBIResultArrow generics: \code{\link{DBIResultArrow-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsValid}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()} } \concept{DBIResultArrow generics} \concept{data retrieval generics} DBI/man/dbBind.Rd0000644000176200001440000003765114552712323013114 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/15-dbBind.R, R/25-dbBindArrow.R \name{dbBind} \alias{dbBind} \alias{dbBindArrow} \title{Bind values to a parameterized/prepared statement} \usage{ dbBind(res, params, ...) dbBindArrow(res, params, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}.} \item{params}{For \code{dbBind()}, a list of values, named or unnamed, or a data frame, with one element/column per query parameter. For \code{dbBindArrow()}, values as a nanoarrow stream, with one column per query parameter.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbBind()} returns the result set, invisibly, for queries issued by \code{\link[=dbSendQuery]{dbSendQuery()}} or \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}} and also for data manipulation statements issued by \code{\link[=dbSendStatement]{dbSendStatement()}}. } \description{ For parametrized or prepared statements, the \code{\link[=dbSendQuery]{dbSendQuery()}}, \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}}, and \code{\link[=dbSendStatement]{dbSendStatement()}} functions can be called with statements that contain placeholders for values. The \code{dbBind()} and \code{dbBindArrow()} functions bind these placeholders to actual values, and are intended to be called on the result set before calling \code{\link[=dbFetch]{dbFetch()}} or \code{\link[=dbFetchArrow]{dbFetchArrow()}}. The values are passed to \code{dbBind()} as lists or data frames, and to \code{dbBindArrow()} as a stream created by \code{\link[nanoarrow:as_nanoarrow_array_stream]{nanoarrow::as_nanoarrow_array_stream()}}. \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} \code{dbBindArrow()} is experimental, as are the other \verb{*Arrow} functions. \code{dbSendQuery()} is compatible with \code{dbBindArrow()}, and \code{dbSendQueryArrow()} is compatible with \code{dbBind()}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbBind")} } \details{ \pkg{DBI} supports parametrized (or prepared) queries and statements via the \code{dbBind()} and \code{dbBindArrow()} generics. Parametrized queries are different from normal queries in that they allow an arbitrary number of placeholders, which are later substituted by actual values. Parametrized queries (and statements) serve two purposes: \itemize{ \item The same query can be executed more than once with different values. The DBMS may cache intermediate information for the query, such as the execution plan, and execute it faster. \item Separation of query syntax and parameters protects against SQL injection. } The placeholder format is currently not specified by \pkg{DBI}; in the future, a uniform placeholder syntax may be supported. Consult the backend documentation for the supported formats. For automated testing, backend authors specify the placeholder syntax with the \code{placeholder_pattern} tweak. Known examples are: \itemize{ \item \verb{?} (positional matching in order of appearance) in \pkg{RMariaDB} and \pkg{RSQLite} \item \verb{$1} (positional matching by index) in \pkg{RPostgres} and \pkg{RSQLite} \item \verb{:name} and \verb{$name} (named matching) in \pkg{RSQLite} } } \section{The data retrieval flow}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbGetQuery]{dbGetQuery()}}, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQuery]{dbSendQuery()}} to create a result set object of class \linkS4class{DBIResult}. \item Optionally, bind query parameters with \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbColumnInfo]{dbColumnInfo()}} to retrieve the structure of the result set without retrieving actual data. \item Use \code{\link[=dbFetch]{dbFetch()}} to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. \item Use \code{\link[=dbHasCompleted]{dbHasCompleted()}} to tell when you're done. This method returns \code{TRUE} if no more rows are available for fetching. \item Repeat the last four steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{The data retrieval flow for Arrow streams}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as an Arrow stream. Most of this flow, except repeated calling of \code{\link[=dbBindArrow]{dbBindArrow()}} or \code{\link[=dbBind]{dbBind()}}, is implemented by \code{\link[=dbGetQueryArrow]{dbGetQueryArrow()}}, which should be sufficient unless you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}} to create a result set object of class \linkS4class{DBIResultArrow}. \item Optionally, bind query parameters with \code{\link[=dbBindArrow]{dbBindArrow()}} or \code{\link[=dbBind]{dbBind()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Use \code{\link[=dbFetchArrow]{dbFetchArrow()}} to get a data stream. \item Repeat the last two steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{The command execution flow}{ This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbExecute]{dbExecute()}}, which should be sufficient for non-parameterized queries. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendStatement]{dbSendStatement()}} to create a result set object of class \linkS4class{DBIResult}. For some queries you need to pass \code{immediate = TRUE}. \item Optionally, bind query parameters with\code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}} to retrieve the number of rows affected by the query. \item Repeat the last two steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ Calling \code{dbBind()} for a query without parameters raises an error. Binding too many or not enough values, or parameters with wrong names or unequal length, also raises an error. If the placeholders in the query are named, all parameter values must have names (which must not be empty or \code{NA}), and vice versa, otherwise an error is raised. The behavior for mixing placeholders of different types (in particular mixing positional and named placeholders) is not specified. Calling \code{dbBind()} on a result set already cleared by \code{\link[=dbClearResult]{dbClearResult()}} also raises an error. } \section{Specification}{ \pkg{DBI} clients execute parametrized statements as follows: \enumerate{ \item Call \code{\link[=dbSendQuery]{dbSendQuery()}}, \code{\link[=dbSendQueryArrow]{dbSendQueryArrow()}} or \code{\link[=dbSendStatement]{dbSendStatement()}} with a query or statement that contains placeholders, store the returned \linkS4class{DBIResult} object in a variable. Mixing placeholders (in particular, named and unnamed ones) is not recommended. It is good practice to register a call to \code{\link[=dbClearResult]{dbClearResult()}} via \code{\link[=on.exit]{on.exit()}} right after calling \code{dbSendQuery()} or \code{dbSendStatement()} (see the last enumeration item). Until \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}} have been called, the returned result set object has the following behavior: \itemize{ \item \code{\link[=dbFetch]{dbFetch()}} raises an error (for \code{dbSendQuery()} and \code{dbSendQueryArrow()}) \item \code{\link[=dbGetRowCount]{dbGetRowCount()}} returns zero (for \code{dbSendQuery()} and \code{dbSendQueryArrow()}) \item \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}} returns an integer \code{NA} (for \code{dbSendStatement()}) \item \code{\link[=dbIsValid]{dbIsValid()}} returns \code{TRUE} \item \code{\link[=dbHasCompleted]{dbHasCompleted()}} returns \code{FALSE} } \item Call \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}: \itemize{ \item For \code{\link[=dbBind]{dbBind()}}, the \code{params} argument must be a list where all elements have the same lengths and contain values supported by the backend. A \link{data.frame} is internally stored as such a list. \item For \code{\link[=dbBindArrow]{dbBindArrow()}}, the \code{params} argument must be a nanoarrow array stream, with one column per query parameter. } \item Retrieve the data or the number of affected rows from the \code{DBIResult} object. \itemize{ \item For queries issued by \code{dbSendQuery()} or \code{dbSendQueryArrow()}, call \code{\link[=dbFetch]{dbFetch()}}. \item For statements issued by \code{dbSendStatements()}, call \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}}. (Execution begins immediately after the \code{\link[=dbBind]{dbBind()}} call, the statement is processed entirely before the function returns.) } \item Repeat 2. and 3. as necessary. \item Close the result set via \code{\link[=dbClearResult]{dbClearResult()}}. } The elements of the \code{params} argument do not need to be scalars, vectors of arbitrary length (including length 0) are supported. For queries, calling \code{dbFetch()} binding such parameters returns concatenated results, equivalent to binding and fetching for each set of values and connecting via \code{\link[=rbind]{rbind()}}. For data manipulation statements, \code{dbGetRowsAffected()} returns the total number of rows affected if binding non-scalar parameters. \code{dbBind()} also accepts repeated calls on the same result set for both queries and data manipulation statements, even if no results are fetched between calls to \code{dbBind()}, for both queries and data manipulation statements. If the placeholders in the query are named, their order in the \code{params} argument is not important. At least the following data types are accepted on input (including \link{NA}): \itemize{ \item \link{integer} \item \link{numeric} \item \link{logical} for Boolean values \item \link{character} (also with special characters such as spaces, newlines, quotes, and backslashes) \item \link{factor} (bound as character, with warning) \item \link{Date} (also when stored internally as integer) \item \link{POSIXct} timestamps \item \link{POSIXlt} timestamps \item \link{difftime} values (also with units other than seconds and with the value stored as integer) \item lists of \link{raw} for blobs (with \code{NULL} entries for SQL NULL values) \item objects of type \link[blob:blob]{blob::blob} } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # Data frame flow: con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "iris", iris) # Using the same query for different values iris_result <- dbSendQuery(con, "SELECT * FROM iris WHERE [Petal.Width] > ?") dbBind(iris_result, list(2.3)) dbFetch(iris_result) dbBind(iris_result, list(3)) dbFetch(iris_result) dbClearResult(iris_result) # Executing the same statement with different values at once iris_result <- dbSendStatement(con, "DELETE FROM iris WHERE [Species] = $species") dbBind(iris_result, list(species = c("setosa", "versicolor", "unknown"))) dbGetRowsAffected(iris_result) dbClearResult(iris_result) nrow(dbReadTable(con, "iris")) dbDisconnect(con) \dontshow{\}) # examplesIf} \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # Arrow flow: con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "iris", iris) # Using the same query for different values iris_result <- dbSendQueryArrow(con, "SELECT * FROM iris WHERE [Petal.Width] > ?") dbBindArrow( iris_result, nanoarrow::as_nanoarrow_array_stream(data.frame(2.3, fix.empty.names = FALSE)) ) as.data.frame(dbFetchArrow(iris_result)) dbBindArrow( iris_result, nanoarrow::as_nanoarrow_array_stream(data.frame(3, fix.empty.names = FALSE)) ) as.data.frame(dbFetchArrow(iris_result)) dbClearResult(iris_result) # Executing the same statement with different values at once iris_result <- dbSendStatement(con, "DELETE FROM iris WHERE [Species] = $species") dbBindArrow(iris_result, nanoarrow::as_nanoarrow_array_stream(data.frame( species = c("setosa", "versicolor", "unknown") ))) dbGetRowsAffected(iris_result) dbClearResult(iris_result) nrow(dbReadTable(con, "iris")) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} Other DBIResultArrow generics: \code{\link{DBIResultArrow-class}}, \code{\link{dbClearResult}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsValid}()} Other data retrieval generics: \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()} Other command execution generics: \code{\link{dbClearResult}()}, \code{\link{dbExecute}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbSendStatement}()} } \concept{DBIResult generics} \concept{DBIResultArrow generics} \concept{command execution generics} \concept{data retrieval generics} DBI/man/dbGetConnectArgs.Rd0000644000176200001440000000252514552712201015071 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbGetConnectArgs.R \name{dbGetConnectArgs} \alias{dbGetConnectArgs} \title{Get connection arguments} \usage{ dbGetConnectArgs(drv, eval = TRUE, ...) } \arguments{ \item{drv}{A object inheriting from \linkS4class{DBIConnector}.} \item{eval}{Set to \code{FALSE} to return the functions that generate the argument instead of evaluating them.} \item{...}{Other arguments passed on to methods. Not otherwise used.} } \description{ Returns the arguments stored in a \linkS4class{DBIConnector} object for inspection, optionally evaluating them. This function is called by \code{\link[=dbConnect]{dbConnect()}} and usually does not need to be called directly. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbGetConnectArgs")} } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} cnr <- new("DBIConnector", .drv = RSQLite::SQLite(), .conn_args = list(dbname = ":memory:", password = function() "supersecret") ) dbGetConnectArgs(cnr) dbGetConnectArgs(cnr, eval = FALSE) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnector generics: \code{\link{DBIConnector-class}}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbIsReadOnly}()} } \concept{DBIConnector generics} DBI/man/DBIConnection-class.Rd0000644000176200001440000000371114552712323015441 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/03-DBIConnection.R \docType{class} \name{DBIConnection-class} \alias{DBIConnection-class} \title{DBIConnection class} \description{ This virtual class encapsulates the connection to a DBMS, and it provides access to dynamic queries, result sets, DBMS session management (transactions), etc. } \section{Implementation note}{ Individual drivers are free to implement single or multiple simultaneous connections. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") con dbDisconnect(con) \dontrun{ con <- dbConnect(RPostgreSQL::PostgreSQL(), "username", "passsword") con dbDisconnect(con) } \dontshow{\}) # examplesIf} } \seealso{ Other DBI classes: \code{\link{DBIConnector-class}}, \code{\link{DBIDriver-class}}, \code{\link{DBIObject-class}}, \code{\link{DBIResult-class}}, \code{\link{DBIResultArrow-class}} Other DBIConnection generics: \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBI classes} \concept{DBIConnection generics} DBI/man/dbFetch.Rd0000644000176200001440000002027714552712323013265 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbFetch.R, R/fetch.R \name{dbFetch} \alias{dbFetch} \alias{fetch} \title{Fetch records from a previously executed query} \usage{ dbFetch(res, n = -1, ...) fetch(res, n = -1, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}, created by \code{\link[=dbSendQuery]{dbSendQuery()}}.} \item{n}{maximum number of records to retrieve per fetch. Use \code{n = -1} or \code{n = Inf} to retrieve all pending records. Some implementations may recognize other special values.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbFetch()} always returns a \link{data.frame} with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows. Passing \code{n = NA} is supported and returns an arbitrary number of rows (at least one) as specified by the driver, but at most the remaining rows in the result set. } \description{ Fetch the next \code{n} elements (rows) from the result set and return them as a data.frame. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbFetch")} } \details{ \code{fetch()} is provided for compatibility with older DBI clients - for all new code you are strongly encouraged to use \code{dbFetch()}. The default implementation for \code{dbFetch()} calls \code{fetch()} so that it is compatible with existing code. Modern backends should implement for \code{dbFetch()} only. } \section{The data retrieval flow}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbGetQuery]{dbGetQuery()}}, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQuery]{dbSendQuery()}} to create a result set object of class \linkS4class{DBIResult}. \item Optionally, bind query parameters with \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbColumnInfo]{dbColumnInfo()}} to retrieve the structure of the result set without retrieving actual data. \item Use \code{\link[=dbFetch]{dbFetch()}} to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. \item Use \code{\link[=dbHasCompleted]{dbHasCompleted()}} to tell when you're done. This method returns \code{TRUE} if no more rows are available for fetching. \item Repeat the last four steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ An attempt to fetch from a closed result set raises an error. If the \code{n} argument is not an atomic whole number greater or equal to -1 or Inf, an error is raised, but a subsequent call to \code{dbFetch()} with proper \code{n} argument succeeds. Calling \code{dbFetch()} on a result set from a data manipulation query created by \code{\link[=dbSendStatement]{dbSendStatement()}} can be fetched and return an empty data frame, with a warning. } \section{Specification}{ Fetching multi-row queries with one or more columns by default returns the entire result. Multi-row queries can also be fetched progressively by passing a whole number (\link{integer} or \link{numeric}) as the \code{n} argument. A value of \link{Inf} for the \code{n} argument is supported and also returns the full result. If more rows than available are fetched, the result is returned in full without warning. If fewer rows than requested are returned, further fetches will return a data frame with zero rows. If zero rows are fetched, the columns of the data frame are still fully typed. Fetching fewer rows than available is permitted, no warning is issued when clearing the result set. A column named \code{row_names} is treated like any other column. The column types of the returned data frame depend on the data returned: \itemize{ \item \link{integer} (or coercible to an integer) for integer values between -2^31 and 2^31 - 1, with \link{NA} for SQL \code{NULL} values \item \link{numeric} for numbers with a fractional component, with NA for SQL \code{NULL} values \item \link{logical} for Boolean values (some backends may return an integer); with NA for SQL \code{NULL} values \item \link{character} for text, with NA for SQL \code{NULL} values \item lists of \link{raw} for blobs with \link{NULL} entries for SQL NULL values \item coercible using \code{\link[=as.Date]{as.Date()}} for dates, with NA for SQL \code{NULL} values (also applies to the return value of the SQL function \code{current_date}) \item coercible using \code{\link[hms:hms]{hms::as_hms()}} for times, with NA for SQL \code{NULL} values (also applies to the return value of the SQL function \code{current_time}) \item coercible using \code{\link[=as.POSIXct]{as.POSIXct()}} for timestamps, with NA for SQL \code{NULL} values (also applies to the return value of the SQL function \code{current_timestamp}) } If dates and timestamps are supported by the backend, the following R types are used: \itemize{ \item \link{Date} for dates (also applies to the return value of the SQL function \code{current_date}) \item \link{POSIXct} for timestamps (also applies to the return value of the SQL function \code{current_timestamp}) } R has no built-in type with lossless support for the full range of 64-bit or larger integers. If 64-bit integers are returned from a query, the following rules apply: \itemize{ \item Values are returned in a container with support for the full range of valid 64-bit values (such as the \code{integer64} class of the \pkg{bit64} package) \item Coercion to numeric always returns a number that is as close as possible to the true value \item Loss of precision when converting to numeric gives a warning \item Conversion to character always returns a lossless decimal representation of the data } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) # Fetch all results rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4") dbFetch(rs) dbClearResult(rs) # Fetch in chunks rs <- dbSendQuery(con, "SELECT * FROM mtcars") while (!dbHasCompleted(rs)) { chunk <- dbFetch(rs, 10) print(nrow(chunk)) } dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Close the result set with \code{\link[=dbClearResult]{dbClearResult()}} as soon as you finish retrieving the records you want. Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()} } \concept{DBIResult generics} \concept{data retrieval generics} DBI/man/dbSendStatement.Rd0000644000176200001440000002031614552712323015004 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbSendStatement.R \name{dbSendStatement} \alias{dbSendStatement} \title{Execute a data manipulation statement on a given database connection} \usage{ dbSendStatement(conn, statement, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{statement}{a character string containing SQL.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbSendStatement()} returns an S4 object that inherits from \linkS4class{DBIResult}. The result set can be used with \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}} to determine the number of rows affected by the query. Once you have finished using a result, make sure to clear it with \code{\link[=dbClearResult]{dbClearResult()}}. } \description{ The \code{dbSendStatement()} method only submits and synchronously executes the SQL data manipulation statement (e.g., \code{UPDATE}, \code{DELETE}, \verb{INSERT INTO}, \verb{DROP TABLE}, ...) to the database engine. To query the number of affected rows, call \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}} on the returned result object. You must also call \code{\link[=dbClearResult]{dbClearResult()}} after that. For interactive use, you should almost always prefer \code{\link[=dbExecute]{dbExecute()}}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbSendStatement")} } \details{ \code{\link[=dbSendStatement]{dbSendStatement()}} comes with a default implementation that simply forwards to \code{\link[=dbSendQuery]{dbSendQuery()}}, to support backends that only implement the latter. } \section{The command execution flow}{ This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbExecute]{dbExecute()}}, which should be sufficient for non-parameterized queries. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendStatement]{dbSendStatement()}} to create a result set object of class \linkS4class{DBIResult}. For some queries you need to pass \code{immediate = TRUE}. \item Optionally, bind query parameters with\code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbGetRowsAffected]{dbGetRowsAffected()}} to retrieve the number of rows affected by the query. \item Repeat the last two steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ An error is raised when issuing a statement over a closed or invalid connection, or if the statement is not a non-\code{NA} string. An error is also raised if the syntax of the query is invalid and all query parameters are given (by passing the \code{params} argument) or the \code{immediate} argument is set to \code{TRUE}. } \section{Additional arguments}{ The following arguments are not part of the \code{dbSendStatement()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{params} (default: \code{NULL}) \item \code{immediate} (default: \code{NULL}) } They must be provided as named arguments. See the "Specification" sections for details on their usage. } \section{Specification}{ No warnings occur under normal conditions. When done, the DBIResult object must be cleared with a call to \code{\link[=dbClearResult]{dbClearResult()}}. Failure to clear the result set leads to a warning when the connection is closed. If the backend supports only one open result set per connection, issuing a second query invalidates an already open result set and raises a warning. The newly opened result set is valid and must be cleared with \code{dbClearResult()}. The \code{param} argument allows passing query parameters, see \code{\link[=dbBind]{dbBind()}} for details. } \section{Specification for the \code{immediate} argument}{ The \code{immediate} argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing \code{immediate = TRUE} leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default \code{NULL} means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct \code{immediate} argument. Examples for possible behaviors: \enumerate{ \item DBI backend defaults to \code{immediate = TRUE} internally \enumerate{ \item A query without parameters is passed: query is executed \item A query with parameters is passed: \enumerate{ \item \code{params} not given: rejected immediately by the database because of a syntax error in the query, the backend tries \code{immediate = FALSE} (and gives a message) \item \code{params} given: query is executed using \code{immediate = FALSE} } } \item DBI backend defaults to \code{immediate = FALSE} internally \enumerate{ \item A query without parameters is passed: \enumerate{ \item simple query: query is executed \item "special" query (such as setting a config options): fails, the backend tries \code{immediate = TRUE} (and gives a message) } \item A query with parameters is passed: \enumerate{ \item \code{params} not given: waiting for parameters via \code{\link[=dbBind]{dbBind()}} \item \code{params} given: query is executed } } } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cars", head(cars, 3)) rs <- dbSendStatement( con, "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" ) dbHasCompleted(rs) dbGetRowsAffected(rs) dbClearResult(rs) dbReadTable(con, "cars") # there are now 6 rows # Pass one set of values directly using the param argument: rs <- dbSendStatement( con, "INSERT INTO cars (speed, dist) VALUES (?, ?)", params = list(4L, 5L) ) dbClearResult(rs) # Pass multiple sets of values using dbBind(): rs <- dbSendStatement( con, "INSERT INTO cars (speed, dist) VALUES (?, ?)" ) dbBind(rs, list(5:6, 6:7)) dbBind(rs, list(7L, 8L)) dbClearResult(rs) dbReadTable(con, "cars") # there are now 10 rows dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ For queries: \code{\link[=dbSendQuery]{dbSendQuery()}} and \code{\link[=dbGetQuery]{dbGetQuery()}}. Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other command execution generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbExecute}()}, \code{\link{dbGetRowsAffected}()} } \concept{DBIConnection generics} \concept{command execution generics} DBI/man/dbCreateTableArrow.Rd0000644000176200001440000001233014552712323015411 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/22-dbCreateTableArrow.R \name{dbCreateTableArrow} \alias{dbCreateTableArrow} \title{Create a table in the database based on an Arrow object} \usage{ dbCreateTableArrow(conn, name, value, ..., temporary = FALSE) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{value}{An object for which a schema can be determined via \code{\link[nanoarrow:as_nanoarrow_schema]{nanoarrow::infer_nanoarrow_schema()}}.} \item{...}{Other parameters passed on to methods.} \item{temporary}{If \code{TRUE}, will generate a temporary table.} } \value{ \code{dbCreateTableArrow()} returns \code{TRUE}, invisibly. } \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} The default \code{dbCreateTableArrow()} method determines the R data types of the Arrow schema associated with the Arrow object, and calls \code{\link[=dbCreateTable]{dbCreateTable()}}. Backends that implement \code{\link[=dbAppendTableArrow]{dbAppendTableArrow()}} should typically also implement this generic. Use \code{\link[=dbCreateTable]{dbCreateTable()}} to create a table from the column types as defined in a data frame. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbCreateTableArrow")} } \section{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 \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. Invalid values for the \code{temporary} argument (non-scalars, unsupported data types, \code{NA}, incompatible values, duplicate names) also raise an error. } \section{Additional arguments}{ The following arguments are not part of the \code{dbCreateTableArrow()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{temporary} (default: \code{FALSE}) } They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage. } \section{Specification}{ The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbCreateTableArrow()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done } The \code{value} argument can be: \itemize{ \item a data frame, \item a nanoarrow array \item a nanoarrow array stream (which will still contain the data after the call) \item a nanoarrow schema } If the \code{temporary} argument is \code{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. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") ptype <- data.frame(a = numeric()) dbCreateTableArrow(con, "df", nanoarrow::infer_nanoarrow_schema(ptype)) dbReadTable(con, "df") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/transactions.Rd0000644000176200001440000000766014552712201014432 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbBegin.R, R/dbCommit.R, R/dbRollback.R, % R/transactions.R \name{dbBegin} \alias{dbBegin} \alias{dbCommit} \alias{dbRollback} \alias{transactions} \title{Begin/commit/rollback SQL transactions} \usage{ dbBegin(conn, ...) dbCommit(conn, ...) dbRollback(conn, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbBegin()}, \code{dbCommit()} and \code{dbRollback()} return \code{TRUE}, invisibly. } \description{ A transaction encapsulates several SQL statements in an atomic unit. It is initiated with \code{dbBegin()} and either made persistent with \code{dbCommit()} or undone with \code{dbRollback()}. In any case, the DBMS guarantees that either all or none of the statements have a permanent effect. This helps ensuring consistency of write operations to multiple tables. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("transactions")} } \details{ Not all database engines implement transaction management, in which case these methods should not be implemented for the specific \linkS4class{DBIConnection} subclass. } \section{Failure modes}{ The implementations are expected to raise an error in case of failure, but this is not tested. In any way, all generics throw an error with a closed or invalid connection. In addition, a call to \code{dbCommit()} or \code{dbRollback()} without a prior call to \code{dbBegin()} raises an error. Nested transactions are not supported by DBI, an attempt to call \code{dbBegin()} twice yields an error. } \section{Specification}{ Actual support for transactions may vary between backends. A transaction is initiated by a call to \code{dbBegin()} and committed by a call to \code{dbCommit()}. Data written in a transaction must persist after the transaction is committed. For example, a record that is missing when the transaction is started but is created during the transaction must exist both during and after the transaction, and also in a new connection. A transaction can also be aborted with \code{dbRollback()}. All data written in such a transaction must be removed after the transaction is rolled back. For example, a record that is missing when the transaction is started but is created during the transaction must not exist anymore after the rollback. Disconnection from a connection with an open transaction effectively rolls back the transaction. All data written in such a transaction must be removed after the transaction is rolled back. The behavior is not specified if other arguments are passed to these functions. In particular, \pkg{RSQLite} issues named transactions with support for nesting if the \code{name} argument is set. The transaction isolation level is not specified by DBI. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cash", data.frame(amount = 100)) dbWriteTable(con, "account", data.frame(amount = 2000)) # All operations are carried out as logical unit: dbBegin(con) withdrawal <- 300 dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) dbCommit(con) dbReadTable(con, "cash") dbReadTable(con, "account") # Rolling back after detecting negative value on account: dbBegin(con) withdrawal <- 5000 dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) if (dbReadTable(con, "account")$amount >= 0) { dbCommit(con) } else { dbRollback(con) } dbReadTable(con, "cash") dbReadTable(con, "account") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Self-contained transactions: \code{\link[=dbWithTransaction]{dbWithTransaction()}} } DBI/man/dbUnquoteIdentifier.Rd0000644000176200001440000000733314552712323015675 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbUnquoteIdentifier.R \name{dbUnquoteIdentifier} \alias{dbUnquoteIdentifier} \title{Unquote identifiers} \usage{ dbUnquoteIdentifier(conn, x, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{x}{An \link{SQL} or \link{Id} object.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbUnquoteIdentifier()} returns a list of objects of the same length as the input. For an empty vector, this function returns a length-0 object. The names of the input argument are preserved in the output. If \code{x} is a value returned by \code{dbUnquoteIdentifier()}, calling \code{dbUnquoteIdentifier(..., dbQuoteIdentifier(..., x))} returns \code{list(x)}. If \code{x} is an object of class \link{Id}, calling \code{dbUnquoteIdentifier(..., x)} returns \code{list(x)}. (For backends it may be most convenient to return \link{Id} objects to achieve this behavior, but this is not required.) Plain character vectors can also be passed to \code{dbUnquoteIdentifier()}. } \description{ Call this method to convert a \link{SQL} object created by \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} back to a list of \link{Id} objects. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbUnquoteIdentifier")} } \section{Failure modes}{ An error is raised if a character vectors with a missing value is passed as the \code{x} argument. } \section{Specification}{ For any character vector of length one, quoting (with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}) then unquoting then quoting the first element is identical to just quoting. This is also true for strings that contain special characters such as a space, a dot, a comma, or quotes used to mark strings or identifiers, if the database supports this. Unquoting simple strings (consisting of only letters) wrapped with \code{\link[=SQL]{SQL()}} and then quoting via \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} gives the same result as just quoting the string. Similarly, unquoting expressions of the form \code{SQL("schema.table")} and then quoting gives the same result as quoting the identifier constructed by \code{Id("schema", "table")}. } \examples{ # Unquoting allows to understand the structure of a # possibly complex quoted identifier dbUnquoteIdentifier( ANSI(), SQL(c('"Catalog"."Schema"."Table"', '"Schema"."Table"', '"UnqualifiedTable"')) ) # The returned object is always a list, # also for Id objects dbUnquoteIdentifier(ANSI(), Id("Catalog", "Schema", "Table")) # Quoting and unquoting are inverses dbQuoteIdentifier( ANSI(), dbUnquoteIdentifier(ANSI(), SQL("UnqualifiedTable"))[[1]] ) dbQuoteIdentifier( ANSI(), dbUnquoteIdentifier(ANSI(), Id("Schema", "Table"))[[1]] ) } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbListConnections.Rd0000644000176200001440000000147714542245565015363 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbListConnections.R \name{dbListConnections} \alias{dbListConnections} \title{List currently open connections} \usage{ dbListConnections(drv, ...) } \arguments{ \item{drv}{A object inheriting from \linkS4class{DBIDriver}} \item{...}{Other arguments passed on to methods.} } \value{ a list } \description{ DEPRECATED, drivers are no longer required to implement this method. Keep track of the connections you opened if you require a list. } \seealso{ Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbCanConnect}()}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbDriver}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()} } \concept{DBIDriver generics} \keyword{internal} DBI/man/dbHasCompleted.Rd0000644000176200001440000001216214552712323014576 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbHasCompleted.R \name{dbHasCompleted} \alias{dbHasCompleted} \title{Completion status} \usage{ dbHasCompleted(res, ...) } \arguments{ \item{res}{An object inheriting from \linkS4class{DBIResult}.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbHasCompleted()} returns a logical scalar. For a query initiated by \code{\link[=dbSendQuery]{dbSendQuery()}} with non-empty result set, \code{dbHasCompleted()} returns \code{FALSE} initially and \code{TRUE} after calling \code{\link[=dbFetch]{dbFetch()}} without limit. For a query initiated by \code{\link[=dbSendStatement]{dbSendStatement()}}, \code{dbHasCompleted()} always returns \code{TRUE}. } \description{ This method returns if the operation has completed. A \code{SELECT} query is completed if all rows have been fetched. A data manipulation statement is always completed. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbHasCompleted")} } \section{The data retrieval flow}{ This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}, is implemented by \code{\link[=dbGetQuery]{dbGetQuery()}}, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by \code{\link[=dbConnect]{dbConnect()}}. See also \code{vignette("dbi-advanced")} for a walkthrough. \enumerate{ \item Use \code{\link[=dbSendQuery]{dbSendQuery()}} to create a result set object of class \linkS4class{DBIResult}. \item Optionally, bind query parameters with \code{\link[=dbBind]{dbBind()}} or \code{\link[=dbBindArrow]{dbBindArrow()}}. This is required only if the query contains placeholders such as \verb{?} or \verb{$1}, depending on the database backend. \item Optionally, use \code{\link[=dbColumnInfo]{dbColumnInfo()}} to retrieve the structure of the result set without retrieving actual data. \item Use \code{\link[=dbFetch]{dbFetch()}} to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. \item Use \code{\link[=dbHasCompleted]{dbHasCompleted()}} to tell when you're done. This method returns \code{TRUE} if no more rows are available for fetching. \item Repeat the last four steps as necessary. \item Use \code{\link[=dbClearResult]{dbClearResult()}} to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use \code{\link[=on.exit]{on.exit()}} or \code{\link[withr:defer]{withr::defer()}} to ensure that this step is always executed. } } \section{Failure modes}{ Attempting to query completion status for a result set cleared with \code{\link[=dbClearResult]{dbClearResult()}} gives an error. } \section{Specification}{ The completion status for a query is only guaranteed to be set to \code{FALSE} after attempting to fetch past the end of the entire result. Therefore, for a query with an empty result set, the initial return value is unspecified, but the result value is \code{TRUE} after trying to fetch only one row. Similarly, for a query with a result set of length n, the return value is unspecified after fetching n rows, but the result value is \code{TRUE} after trying to fetch only one more row. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQuery(con, "SELECT * FROM mtcars") dbHasCompleted(rs) ret1 <- dbFetch(rs, 10) dbHasCompleted(rs) ret2 <- dbFetch(rs) dbHasCompleted(rs) dbClearResult(rs) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} Other DBIResultArrow generics: \code{\link{DBIResultArrow-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbIsValid}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()} } \concept{DBIResult generics} \concept{DBIResultArrow generics} \concept{data retrieval generics} DBI/man/dbGetDBIVersion.Rd0000644000176200001440000000045514350241735014634 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/deprecated.R \name{dbGetDBIVersion} \alias{dbGetDBIVersion} \title{Determine the current version of the package.} \usage{ dbGetDBIVersion() } \description{ Determine the current version of the package. } \keyword{internal} DBI/man/DBIConnector-class.Rd0000644000176200001440000000324014552712323015271 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/DBIConnector.R \docType{class} \name{DBIConnector-class} \alias{DBIConnector-class} \title{DBIConnector class} \description{ Wraps objects of the \linkS4class{DBIDriver} class to include connection options. The purpose of this class is to store both the driver and the connection options. A database connection can be established with a call to \code{\link[=dbConnect]{dbConnect()}}, passing only that object without additional arguments. } \details{ To prevent leakage of passwords and other credentials, this class supports delayed evaluation. All arguments can optionally be a function (callable without arguments). In such a case, the function is evaluated transparently when connecting in \code{\link[=dbGetConnectArgs]{dbGetConnectArgs()}}. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} # Create a connector: cnr <- new("DBIConnector", .drv = RSQLite::SQLite(), .conn_args = list(dbname = ":memory:") ) cnr # Establish a connection through this connector: con <- dbConnect(cnr) con # Access the database through this connection: dbGetQuery(con, "SELECT 1 AS a") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBI classes: \code{\link{DBIConnection-class}}, \code{\link{DBIDriver-class}}, \code{\link{DBIObject-class}}, \code{\link{DBIResult-class}}, \code{\link{DBIResultArrow-class}} Other DBIConnector generics: \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbGetConnectArgs}()}, \code{\link{dbIsReadOnly}()} } \concept{DBI classes} \concept{DBIConnector generics} DBI/man/dbQuoteString.Rd0000644000176200001440000000562514552712323014520 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbQuoteString.R \name{dbQuoteString} \alias{dbQuoteString} \title{Quote literal strings} \usage{ dbQuoteString(conn, x, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{x}{A character vector to quote as string.} \item{...}{Other arguments passed on to methods.} } \value{ \code{dbQuoteString()} returns an object that can be coerced to \link{character}, of the same length as the input. For an empty character vector this function returns a length-0 object. When passing the returned object again to \code{dbQuoteString()} as \code{x} argument, it is returned unchanged. Passing objects of class \link{SQL} should also return them unchanged. (For backends it may be most convenient to return \link{SQL} objects to achieve this behavior, but this is not required.) } \description{ Call this method to generate a string that is suitable for use in a query as a string literal, to make sure that you generate valid SQL and protect against SQL injection attacks. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbQuoteString")} } \section{Failure modes}{ Passing a numeric, integer, logical, or raw vector, or a list for the \code{x} argument raises an error. } \section{Specification}{ The returned expression can be used in a \verb{SELECT ...} query, and for any scalar character \code{x} the value of \code{dbGetQuery(paste0("SELECT ", dbQuoteString(x)))[[1]]} must be identical to \code{x}, even if \code{x} contains spaces, tabs, quotes (single or double), backticks, or newlines (in any combination) or is itself the result of a \code{dbQuoteString()} call coerced back to character (even repeatedly). If \code{x} is \code{NA}, the result must merely satisfy \code{\link[=is.na]{is.na()}}. The strings \code{"NA"} or \code{"NULL"} are not treated specially. \code{NA} should be translated to an unquoted SQL \code{NULL}, so that the query \verb{SELECT * FROM (SELECT 1) a WHERE ... IS NULL} returns one row. } \examples{ # Quoting ensures that arbitrary input is safe for use in a query name <- "Robert'); DROP TABLE Students;--" dbQuoteString(ANSI(), name) # NAs become NULL dbQuoteString(ANSI(), c("x", NA)) # SQL vectors are always passed through as is var_name <- SQL("select") var_name dbQuoteString(ANSI(), var_name) # This mechanism is used to prevent double escaping dbQuoteString(ANSI(), dbQuoteString(ANSI(), name)) } \seealso{ Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()} } \concept{DBIResult generics} DBI/man/dbWriteTable.Rd0000644000176200001440000002140614552712323014271 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/13-dbWriteTable.R \name{dbWriteTable} \alias{dbWriteTable} \title{Copy data frames to database tables} \usage{ dbWriteTable(conn, name, value, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{value}{A \link{data.frame} (or coercible to data.frame).} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbWriteTable()} returns \code{TRUE}, invisibly. } \description{ Writes, overwrites or appends a data frame to a database table, optionally converting row names to a column and specifying SQL data types for fields. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbWriteTable")} } \details{ This function expects a data frame. Use \code{\link[=dbWriteTableArrow]{dbWriteTableArrow()}} to write an Arrow object. This function is useful if you want to create and load a table at the same time. Use \code{\link[=dbAppendTable]{dbAppendTable()}} or \code{\link[=dbAppendTableArrow]{dbAppendTableArrow()}} for appending data to an existing table, \code{\link[=dbCreateTable]{dbCreateTable()}} or \code{\link[=dbCreateTableArrow]{dbCreateTableArrow()}} for creating a table, and \code{\link[=dbExistsTable]{dbExistsTable()}} and \code{\link[=dbRemoveTable]{dbRemoveTable()}} for overwriting tables. DBI only standardizes writing data frames with \code{dbWriteTable()}. Some backends might implement methods that can consume CSV files or other data formats. For details, see the documentation for the individual methods. } \section{Failure modes}{ If the table exists, and both \code{append} and \code{overwrite} arguments are unset, or \code{append = TRUE} and the data frame with the new data has different column names, 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 \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. Invalid values for the additional arguments \code{row.names}, \code{overwrite}, \code{append}, \code{field.types}, and \code{temporary} (non-scalars, unsupported data types, \code{NA}, incompatible values, duplicate or missing names, incompatible columns) also raise an error. } \section{Additional arguments}{ The following arguments are not part of the \code{dbWriteTable()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{row.names} (default: \code{FALSE}) \item \code{overwrite} (default: \code{FALSE}) \item \code{append} (default: \code{FALSE}) \item \code{field.types} (default: \code{NULL}) \item \code{temporary} (default: \code{FALSE}) } They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage. } \section{Specification}{ The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbWriteTable()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done } The \code{value} argument must be a data frame with a subset of the columns of the existing table if \code{append = TRUE}. The order of the columns does not matter with \code{append = TRUE}. If the \code{overwrite} argument is \code{TRUE}, an existing table of the same name will be overwritten. This argument doesn't change behavior if the table does not exist yet. If the \code{append} argument is \code{TRUE}, the rows in an existing table are preserved, and the new data are appended. If the table doesn't exist yet, it is created. If the \code{temporary} argument is \code{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, spaces, and other special characters such as newlines and tabs, can also be used in the data, and, if the database supports non-syntactic identifiers, also for table names and column names. The following data types must be supported at least, and be read identically with \code{\link[=dbReadTable]{dbReadTable()}}: \itemize{ \item integer \item numeric (the behavior for \code{Inf} and \code{NaN} is not specified) \item logical \item \code{NA} as NULL \item 64-bit values (using \code{"bigint"} as field type); the result can be \itemize{ \item converted to a numeric, which may lose precision, \item converted a character vector, which gives the full decimal representation \item written to another table and read again unchanged } \item character (in both UTF-8 and native encodings), supporting empty strings before and after a non-empty string \item factor (returned as character) \item list of raw (if supported by the database) \item objects of type \link[blob:blob]{blob::blob} (if supported by the database) \item date (if supported by the database; returned as \code{Date}), also for dates prior to 1970 or 1900 or after 2038 \item time (if supported by the database; returned as objects that inherit from \code{difftime}) \item timestamp (if supported by the database; returned as \code{POSIXct} respecting the time zone but not necessarily preserving the input time zone), also for timestamps prior to 1970 or 1900 or after 2038 respecting the time zone but not necessarily preserving the input time zone) } Mixing column types in the same table is supported. The \code{field.types} argument must be a named character vector with at most one entry for each column. It indicates the SQL data type to be used for a new column. If a column is missed from \code{field.types}, the type is inferred from the input data with \code{\link[=dbDataType]{dbDataType()}}. The interpretation of \link{rownames} depends on the \code{row.names} argument, see \code{\link[=sqlRownamesToColumn]{sqlRownamesToColumn()}} for details: \itemize{ \item If \code{FALSE} or \code{NULL}, row names are ignored. \item If \code{TRUE}, row names are converted to a column named "row_names", even if the input data frame only has natural row names from 1 to \code{nrow(...)}. \item If \code{NA}, a column named "row_names" is created if the data has custom row names, no extra column is created in the case of natural row names. \item If a string, this specifies the name of the column in the remote table that contains the row names, even if the input data frame only has natural row names. } The default is \code{row.names = FALSE}. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars[1:5, ]) dbReadTable(con, "mtcars") dbWriteTable(con, "mtcars", mtcars[6:10, ], append = TRUE) dbReadTable(con, "mtcars") dbWriteTable(con, "mtcars", mtcars[1:10, ], overwrite = TRUE) dbReadTable(con, "mtcars") # No row names dbWriteTable(con, "mtcars", mtcars[1:10, ], overwrite = TRUE, row.names = FALSE) dbReadTable(con, "mtcars") \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTableArrow}()} } \concept{DBIConnection generics} DBI/man/dbWriteTableArrow.Rd0000644000176200001440000001660414552712323015310 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/23-dbWriteTableArrow.R \name{dbWriteTableArrow} \alias{dbWriteTableArrow} \title{Copy Arrow objects to database tables} \usage{ dbWriteTableArrow(conn, name, value, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{name}{The table name, passed on to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}. Options are: \itemize{ \item a character string with the unquoted DBMS table name, e.g. \code{"table_name"}, \item a call to \code{\link[=Id]{Id()}} with components to the fully qualified table name, e.g. \code{Id(schema = "my_schema", table = "table_name")} \item a call to \code{\link[=SQL]{SQL()}} with the quoted and fully qualified table name given verbatim, e.g. \code{SQL('"my_schema"."table_name"')} }} \item{value}{An nanoarray stream, or an object coercible to a nanoarray stream with \code{\link[nanoarrow:as_nanoarrow_array_stream]{nanoarrow::as_nanoarrow_array_stream()}}.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbWriteTableArrow()} returns \code{TRUE}, invisibly. } \description{ \ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#experimental}{\figure{lifecycle-experimental.svg}{options: alt='[Experimental]'}}}{\strong{[Experimental]}} Writes, overwrites or appends an Arrow object to a database table. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbWriteTableArrow")} } \details{ This function expects an Arrow object. Convert a data frame to an Arrow object with \code{\link[nanoarrow:as_nanoarrow_array_stream]{nanoarrow::as_nanoarrow_array_stream()}} or use \code{\link[=dbWriteTable]{dbWriteTable()}} to write a data frame. This function is useful if you want to create and load a table at the same time. Use \code{\link[=dbAppendTableArrow]{dbAppendTableArrow()}} for appending data to an existing table, \code{\link[=dbCreateTableArrow]{dbCreateTableArrow()}} for creating a table and specifying field types, and \code{\link[=dbRemoveTable]{dbRemoveTable()}} for overwriting tables. } \section{Failure modes}{ If the table exists, and both \code{append} and \code{overwrite} arguments are unset, or \code{append = TRUE} and the data frame with the new data has different column names, 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 \code{name} cannot be processed with \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}} or if this results in a non-scalar. Invalid values for the additional arguments \code{overwrite}, \code{append}, and \code{temporary} (non-scalars, unsupported data types, \code{NA}, incompatible values, incompatible columns) also raise an error. } \section{Additional arguments}{ The following arguments are not part of the \code{dbWriteTableArrow()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{overwrite} (default: \code{FALSE}) \item \code{append} (default: \code{FALSE}) \item \code{temporary} (default: \code{FALSE}) } They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage. } \section{Specification}{ The \code{name} argument is processed as follows, to support databases that allow non-syntactic names for their objects: \itemize{ \item If an unquoted table name as string: \code{dbWriteTableArrow()} will do the quoting, perhaps by calling \code{dbQuoteIdentifier(conn, x = name)} \item If the result of a call to \code{\link[=dbQuoteIdentifier]{dbQuoteIdentifier()}}: no more quoting is done } The \code{value} argument must be a data frame with a subset of the columns of the existing table if \code{append = TRUE}. The order of the columns does not matter with \code{append = TRUE}. If the \code{overwrite} argument is \code{TRUE}, an existing table of the same name will be overwritten. This argument doesn't change behavior if the table does not exist yet. If the \code{append} argument is \code{TRUE}, the rows in an existing table are preserved, and the new data are appended. If the table doesn't exist yet, it is created. If the \code{temporary} argument is \code{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, spaces, and other special characters such as newlines and tabs, can also be used in the data, and, if the database supports non-syntactic identifiers, also for table names and column names. The following data types must be supported at least, and be read identically with \code{\link[=dbReadTable]{dbReadTable()}}: \itemize{ \item integer \item numeric (the behavior for \code{Inf} and \code{NaN} is not specified) \item logical \item \code{NA} as NULL \item 64-bit values (using \code{"bigint"} as field type); the result can be \itemize{ \item converted to a numeric, which may lose precision, \item converted a character vector, which gives the full decimal representation \item written to another table and read again unchanged } \item character (in both UTF-8 and native encodings), supporting empty strings before and after a non-empty string \item factor (possibly returned as character) \item objects of type \link[blob:blob]{blob::blob} (if supported by the database) \item date (if supported by the database; returned as \code{Date}), also for dates prior to 1970 or 1900 or after 2038 \item time (if supported by the database; returned as objects that inherit from \code{difftime}) \item timestamp (if supported by the database; returned as \code{POSIXct} respecting the time zone but not necessarily preserving the input time zone), also for timestamps prior to 1970 or 1900 or after 2038 respecting the time zone but not necessarily preserving the input time zone) } Mixing column types in the same table is supported. } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTableArrow(con, "mtcars", nanoarrow::as_nanoarrow_array_stream(mtcars[1:5, ])) dbReadTable(con, "mtcars") dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()} } \concept{DBIConnection generics} DBI/man/dbGetQuery.Rd0000644000176200001440000001611214552712323013772 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbGetQuery.R \name{dbGetQuery} \alias{dbGetQuery} \title{Retrieve results from a query} \usage{ dbGetQuery(conn, statement, ...) } \arguments{ \item{conn}{A \linkS4class{DBIConnection} object, as returned by \code{\link[=dbConnect]{dbConnect()}}.} \item{statement}{a character string containing SQL.} \item{...}{Other parameters passed on to methods.} } \value{ \code{dbGetQuery()} always returns a \link{data.frame}, with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows. } \description{ Returns the result of a query as a data frame. \code{dbGetQuery()} comes with a default implementation (which should work with most backends) that calls \code{\link[=dbSendQuery]{dbSendQuery()}}, then \code{\link[=dbFetch]{dbFetch()}}, ensuring that the result is always freed by \code{\link[=dbClearResult]{dbClearResult()}}. For retrieving chunked/paged results or for passing query parameters, see \code{\link[=dbSendQuery]{dbSendQuery()}}, in particular the "The data retrieval flow" section. For retrieving results as an Arrow object, see \code{\link[=dbGetQueryArrow]{dbGetQueryArrow()}}. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbGetQuery")} } \details{ This method is for \code{SELECT} queries only (incl. other SQL statements that return a \code{SELECT}-alike result, e.g., execution of a stored procedure or data manipulation queries like \verb{INSERT INTO ... RETURNING ...}). To execute a stored procedure that does not return a result set, use \code{\link[=dbExecute]{dbExecute()}}. Some backends may support data manipulation statements through this method for compatibility reasons. However, callers are strongly advised to use \code{\link[=dbExecute]{dbExecute()}} for data manipulation statements. } \section{Implementation notes}{ Subclasses should override this method only if they provide some sort of performance optimization. } \section{Failure modes}{ An error is raised when issuing a query over a closed or invalid connection, if the syntax of the query is invalid, or if the query is not a non-\code{NA} string. If the \code{n} argument is not an atomic whole number greater or equal to -1 or Inf, an error is raised, but a subsequent call to \code{dbGetQuery()} with proper \code{n} argument succeeds. } \section{Additional arguments}{ The following arguments are not part of the \code{dbGetQuery()} generic (to improve compatibility across backends) but are part of the DBI specification: \itemize{ \item \code{n} (default: -1) \item \code{params} (default: \code{NULL}) \item \code{immediate} (default: \code{NULL}) } They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage. } \section{Specification}{ A column named \code{row_names} is treated like any other column. The \code{n} argument specifies the number of rows to be fetched. If omitted, fetching multi-row queries with one or more columns returns the entire result. A value of \link{Inf} for the \code{n} argument is supported and also returns the full result. If more rows than available are fetched (by passing a too large value for \code{n}), the result is returned in full without warning. If zero rows are requested, the columns of the data frame are still fully typed. Fetching fewer rows than available is permitted, no warning is issued. The \code{param} argument allows passing query parameters, see \code{\link[=dbBind]{dbBind()}} for details. } \section{Specification for the \code{immediate} argument}{ The \code{immediate} argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing \code{immediate = TRUE} leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default \code{NULL} means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct \code{immediate} argument. Examples for possible behaviors: \enumerate{ \item DBI backend defaults to \code{immediate = TRUE} internally \enumerate{ \item A query without parameters is passed: query is executed \item A query with parameters is passed: \enumerate{ \item \code{params} not given: rejected immediately by the database because of a syntax error in the query, the backend tries \code{immediate = FALSE} (and gives a message) \item \code{params} given: query is executed using \code{immediate = FALSE} } } \item DBI backend defaults to \code{immediate = FALSE} internally \enumerate{ \item A query without parameters is passed: \enumerate{ \item simple query: query is executed \item "special" query (such as setting a config options): fails, the backend tries \code{immediate = TRUE} (and gives a message) } \item A query with parameters is passed: \enumerate{ \item \code{params} not given: waiting for parameters via \code{\link[=dbBind]{dbBind()}} \item \code{params} given: query is executed } } } } \examples{ \dontshow{if (requireNamespace("RSQLite", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)(\{ # examplesIf} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) dbGetQuery(con, "SELECT * FROM mtcars") dbGetQuery(con, "SELECT * FROM mtcars", n = 6) # Pass values using the param argument: # (This query runs eight times, once for each different # parameter. The resulting rows are combined into a single # data frame.) dbGetQuery( con, "SELECT COUNT(*) FROM mtcars WHERE cyl = ?", params = list(1:8) ) dbDisconnect(con) \dontshow{\}) # examplesIf} } \seealso{ For updates: \code{\link[=dbSendStatement]{dbSendStatement()}} and \code{\link[=dbExecute]{dbExecute()}}. Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other data retrieval generics: \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbFetch}()}, \code{\link{dbFetchArrow}()}, \code{\link{dbFetchArrowChunk}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()} } \concept{DBIConnection generics} \concept{data retrieval generics} DBI/man/DBIDriver-class.Rd0000644000176200001440000000177114552712323014601 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/02-DBIDriver.R \docType{class} \name{DBIDriver-class} \alias{DBIDriver-class} \title{DBIDriver class} \description{ Base class for all DBMS drivers (e.g., RSQLite, MySQL, PostgreSQL). The virtual class \code{DBIDriver} defines the operations for creating connections and defining data type mappings. Actual driver classes, for instance \code{RPostgres}, \code{RMariaDB}, etc. implement these operations in a DBMS-specific manner. } \seealso{ Other DBI classes: \code{\link{DBIConnection-class}}, \code{\link{DBIConnector-class}}, \code{\link{DBIObject-class}}, \code{\link{DBIResult-class}}, \code{\link{DBIResultArrow-class}} Other DBIDriver generics: \code{\link{dbCanConnect}()}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbDriver}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsReadOnly}()}, \code{\link{dbIsValid}()}, \code{\link{dbListConnections}()} } \concept{DBI classes} \concept{DBIDriver generics} DBI/man/dbIsReadOnly.Rd0000644000176200001440000000464314552712323014244 0ustar liggesusers% Generated by roxygen2: do not edit by hand % Please edit documentation in R/dbIsReadOnly.R \name{dbIsReadOnly} \alias{dbIsReadOnly} \title{Is this DBMS object read only?} \usage{ dbIsReadOnly(dbObj, ...) } \arguments{ \item{dbObj}{An object inheriting from \linkS4class{DBIObject}, i.e. \linkS4class{DBIDriver}, \linkS4class{DBIConnection}, or a \linkS4class{DBIResult}} \item{...}{Other arguments to methods.} } \description{ This generic tests whether a database object is read only. \Sexpr[results=rd,stage=render]{DBI:::methods_as_rd("dbIsReadOnly")} } \examples{ dbIsReadOnly(ANSI()) } \seealso{ Other DBIDriver generics: \code{\link{DBIDriver-class}}, \code{\link{dbCanConnect}()}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbDriver}()}, \code{\link{dbGetInfo}()}, \code{\link{dbIsValid}()}, \code{\link{dbListConnections}()} Other DBIConnection generics: \code{\link{DBIConnection-class}}, \code{\link{dbAppendTable}()}, \code{\link{dbAppendTableArrow}()}, \code{\link{dbCreateTable}()}, \code{\link{dbCreateTableArrow}()}, \code{\link{dbDataType}()}, \code{\link{dbDisconnect}()}, \code{\link{dbExecute}()}, \code{\link{dbExistsTable}()}, \code{\link{dbGetException}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetQuery}()}, \code{\link{dbGetQueryArrow}()}, \code{\link{dbIsValid}()}, \code{\link{dbListFields}()}, \code{\link{dbListObjects}()}, \code{\link{dbListResults}()}, \code{\link{dbListTables}()}, \code{\link{dbQuoteIdentifier}()}, \code{\link{dbReadTable}()}, \code{\link{dbReadTableArrow}()}, \code{\link{dbRemoveTable}()}, \code{\link{dbSendQuery}()}, \code{\link{dbSendQueryArrow}()}, \code{\link{dbSendStatement}()}, \code{\link{dbUnquoteIdentifier}()}, \code{\link{dbWriteTable}()}, \code{\link{dbWriteTableArrow}()} Other DBIResult generics: \code{\link{DBIResult-class}}, \code{\link{dbBind}()}, \code{\link{dbClearResult}()}, \code{\link{dbColumnInfo}()}, \code{\link{dbFetch}()}, \code{\link{dbGetInfo}()}, \code{\link{dbGetRowCount}()}, \code{\link{dbGetRowsAffected}()}, \code{\link{dbGetStatement}()}, \code{\link{dbHasCompleted}()}, \code{\link{dbIsValid}()}, \code{\link{dbQuoteLiteral}()}, \code{\link{dbQuoteString}()} Other DBIConnector generics: \code{\link{DBIConnector-class}}, \code{\link{dbConnect}()}, \code{\link{dbDataType}()}, \code{\link{dbGetConnectArgs}()} } \concept{DBIConnection generics} \concept{DBIConnector generics} \concept{DBIDriver generics} \concept{DBIResult generics} DBI/DESCRIPTION0000644000176200001440000000347714563656122012403 0ustar liggesusersPackage: DBI Title: R Database Interface Version: 1.2.2 Date: 2024-02-09 Authors@R: c( person("R Special Interest Group on Databases (R-SIG-DB)", role = "aut"), person("Hadley", "Wickham", role = "aut"), person("Kirill", "Müller", , "kirill@cynkra.com", role = c("aut", "cre"), comment = c(ORCID = "0000-0002-1416-3412")), person("R Consortium", role = "fnd") ) Description: A database interface definition for communication between R and relational database management systems. All classes in this package are virtual and need to be extended by the various R/DBMS implementations. License: LGPL (>= 2.1) URL: https://dbi.r-dbi.org, https://github.com/r-dbi/DBI BugReports: https://github.com/r-dbi/DBI/issues Depends: methods, R (>= 3.0.0) Suggests: arrow, blob, covr, DBItest, dbplyr, downlit, dplyr, glue, hms, knitr, magrittr, nanoarrow (>= 0.3.0.1), RMariaDB, rmarkdown, rprojroot, RSQLite (>= 1.1-2), testthat (>= 3.0.0), vctrs, xml2 VignetteBuilder: knitr Config/autostyle/scope: line_breaks Config/autostyle/strict: false Config/Needs/check: r-dbi/DBItest Encoding: UTF-8 RoxygenNote: 7.3.0.9000 Config/Needs/website: r-dbi/DBItest, r-dbi/dbitemplate, adbi, AzureKusto, bigrquery, DatabaseConnector, dittodb, duckdb, implyr, lazysf, odbc, pool, RAthena, IMSMWU/RClickhouse, RH2, RJDBC, RMariaDB, RMySQL, RPostgres, RPostgreSQL, RPresto, RSQLite, sergeant, sparklyr, withr Config/testthat/edition: 3 NeedsCompilation: no Packaged: 2024-02-09 07:30:24 UTC; kirill Author: R Special Interest Group on Databases (R-SIG-DB) [aut], Hadley Wickham [aut], Kirill Müller [aut, cre] (), R Consortium [fnd] Maintainer: Kirill Müller Repository: CRAN Date/Publication: 2024-02-16 13:00:02 UTC DBI/build/0000755000176200001440000000000014561352217011755 5ustar liggesusersDBI/build/vignette.rds0000644000176200001440000000067714561352217014326 0ustar liggesusersSMS0  ?N֛pƟ"#A:I'2ٞMIJUIo}oBH@u" Ƴ=n'YdhIy"?*p)O HrUK ESG3f4|ggiUD *#i؋g}: SEz.*^&z}S?mj },I\ZT'ӴLFA,E<c[ v1>BԄ\> stream xڵXMoJW̲]4eJIܴV#Uv 1c 8;DR n—3sw>3i3kR0.pQLI#2 δGB0LHab2)Y`pQ,H02d&TLF (^3Jlhd 4 l\zC1xW AB0 ("g>/TP0!yqЇ@P)4*YH&q!~k }55\Ј{i5h]Cz`hqJyE Lr!!R5H ҅3g$F R#ʩTpEi|~GYRDXqAG+JTOH3i‘,E !ѐ#]ʗ|I!Ԁ#e*φRIȚ[E!' ::-!GG+A` 5@EkRԵ0 D}?".tѻw팽혽.lGl=W?d_8]C~/'R?;1 h7ۼNHtB7Oܸ?oԽrTEkS}u"Ϫ"ɖ'7MaنI3;ǡ8M8|›u`Żv^N{+,qp5pz(lĢ!>I~~ YK:U{Rn(+f'cjh~+_>sr)^7_|M endstream endobj 245 0 obj << /Length 957 /Filter /FlateDecode >> stream xڕVr8}W%Йݙztۗήk #`&p?,z q}cU1uth⠎p(@Dkܽ#FNQ8&ϡ Ԓ/i w n- W.->* #(\o'\i!1!%@Q (c/FT0R q(q02" wL{Һ ;M˽TnȢJ17?8o_6+9 \צcge(7p)Xi}[Ҹw}ԆL}b}ނiu{Ѝا>< LLՉ8+9oGFv '"2ixv3cۅbb Ze]OSDqț4Z.X , /5`hn?~m76@]rzGvY)vѾn= k;ԑ)h s4@OTXR375춈3avU ;ti6 o! zкU:::YUڞ-Lpi'l] !{UYƵy@ߏq.vLdlbe_0,ur\Dj⃐]mQL sgJy*Ճ^? 7lc׫TԾ+ \OI9\ݗ0*j !1j?پߦDd%7*\9y Of5G)=eYٜUFjs\'Ǜ]rQb^_ZE~DbD4=$w3L=> stream xYKo8W(͇{#ɦbh+W~IKDv=0 ڞ蛙#ZK Z7|0}+}k~o!|+![fcu XmS5*?${YlX8.NzlpKQH-cc.Od!\'Y/ARBϷ=E>0BpR wrD B]G4K7YVr!i3 =}Yz-&c׺ѢS ϪDJȢSe.*^n;S&ق .7,C&$H;$U>"J%mNQ~n}H9;:Û?_IUQngOǓn+S6n|;O˒nFI,dz#$x^rnjjb~LM]Ўov?4褡hy2wBhEʝ)_9>,J6tAO;Yj4oMD'"T@'OX:!)JD;?8+g\TB B9IUm~_8.AȠ}D}eO. þE_r&yk'1ȟA7 P^OSۍW}X0MEg3;\<$N< ?읃TH~JFk.bl|7$F3U &'*_^}pܴM )z5 endstream endobj 340 0 obj << /Length 1269 /Filter /FlateDecode >> stream xMw8,a$cqOLiMGBg*dmG{%އdpvG"M 1 "#ozw0\7q/gהnF EmXW ^Sq%S)~ͰAH8#uu "U)w!Wua^Qճ~C␟<kUUOAz紭1cd/{YFAƉS~ެ>嬑i"`&c܈F.V5ԙxSKq!rePz?ЉyY2YY\;u˭·5d;*g{/pc~ /24G| 1zo? 85/&\gA/na="TjQ|cˠfX@}gfԥN lu&T);'`okqas2;tO|1e 1GO,߮FSY4 |jg6}5b'xSMʴ@cS(T76]O8~m-M cڒ5ԹE`'ۺcYʉr3ɾ{f%iێs,͊ܛ[N%mjx9m ZJsf$_ v-aϕ .{H┣ۮ)Jr`fv0L}Bfx!:mKr>Yooԣ z8"1?_. oݚEbyclu~%>nn+ajYJ.v 5o $by!BcVa;߀ޞǷ'l?y؛-w_bμP=?wbaAD1jM= ߺEu_]!"6 SQKs*t.f;{ pBi#k$$4B$&Y-\ m%TN7]SO0Y۷_{i^Vڬ\,VE6&ѡy0GL9dVՓ+7BjTLBP׮P5 0F.H[I m6!dS;}j>Qe65FgWwu#;=to[$Q@@]3WTfKsTozTg ]ߨrQE endstream endobj 393 0 obj << /Length 1802 /Filter /FlateDecode >> stream xڥXYo8~ϯ0 D]44[u )LȒ!Iw,)ʁ, r43ߌL'7:8:ǓdqO櫉O) Y$0QJ01r-|D=5uǦAD{X\SRɪH03O fC}rēyK󜙇3Xܯe6tVgZ{'X}Գ3#Iچ51aQx6Be3"+L e㳖7lbñyUmJ8hn 3F'Y4bG teH؛)Yb'ꍡ4ȹjm~:R 9m m}]}[*1r)u|c"B#iF0D>{FAt_("> ܑcH,e<0 IaE&>͵AZ [>7_V[꼇UuŴepY)2 -ICoasgO'{_Sq2p1N ޫu-YZ0^xk;al,I'5f7<W`Es@{\G#xX`7 qڪ eAo9=5{q?GRBs endstream endobj 203 0 obj << /Type /ObjStm /N 100 /First 887 /Length 2415 /Filter /FlateDecode >> stream xڽZQs~@Gqg˝u@IWSTH:q}=BǓ#"̃vw8e3GFdz>( }Rϊ"9 3H̸f]T,(CVqk"eA%($[J ƙVY~p :IYb <0a%Ġlk["̉Ps\/ Qn*$Y\d0*2OSh)G,O1Cv%13g q(?18Bzt@Y`&g#'Jf6 XNqa<.+[?Jf9 8ԋ_?&Bys_nO͠D ke\ߠŻG7p~^,_Yg>oODΗ~}r |TzT/md?ks5&$FuKrr2W{¢ DMY}Z_! ?Y_>w"-X%ySA"Knrwtم7w= a{Za s;^r)uA’gVb9|d)`ŧ-dvv'' vZv?ޜ߳/]ws]?ÅL=Wz~tW]w{gr%5E]l> ȩ_V9k=f_~<4j7;־~+Mjȧr ,)ΐ0Ou?W=-rJuo/=˽މߺwnH:CI""<."X"/._z9pq` "oA,;:;;KR5 K@#b 6HF \k~`g=!2GCOć!F֏#6wN ֶQgl+=D9Qo=Oz K}@8;8 if-*Wc0pI0G +!X4'9!ǐ#f*ʵ6Z=CY0ʥBRj1pҡP~[X ePIj-,N'‘ވ~Qݚ'eѡFQ`_Hn ӱJ{0M?.|塀v@*gv($^jޖޕ/}(=>>~D"yȳE-lg<["ysE+\A>co|{eh*ۧ#&@ ,ўaW#8U }J8(Ckwه@Fdh1؁;\ r9UR< S @&:$⪶8I'J0P{ c<T0>C0:zpJ"c{hy;b=j=SrBԡ} A(@f nOg49MnO l ʇ @!U&<}`+Dw; c;[ٚ~kz1w>hz"~0S[l+A3? }q)ME֩V~j?x?P=GwJ,"wB{"@VdLK:Mrs:¦9 +A3TvP/ ^g6 e8a~(Xr=Ʌ endstream endobj 425 0 obj << /Length 1502 /Filter /FlateDecode >> stream xڵXmo6_!(&1KR$%致M.(dY#uw|lJ"o-@'/w=w4 'TxӅG0F^(0sﳏn>^KnLƄw1~QΫo8؁aBAa)#nGDY/FbozIFL @/4Bb~ 4S% kU%e"ؿǡUy"]~aHVq'*w* ^, Gν0:*Rա(US/UǶtC%z(:N?a;tfV]u\9:: ކ Q@ffZzeeJq?D,d]S/f@G`!{\^_'cY?RO:f I&-Q D,. &4 |: rC%a L]'%88"!7YO0R P٪%DrOn қeY!mIRK f++ɢ,2}.X0z+e~Q=bs[8SNr@ʾ??]_pJvMEzrZGZ@)hX>~y f> Sp]R*Im+x@SJwXJg.KR 5MjD M]hqۮ{8Н-E!"U@$CLYm TvB)|}_!EC˖[ajS/~M8jS[2]g;gf77"l> stream xڽY[۶~Ҍo:Nw&ܗ H|r}wxx|,v V`W?^}>IVɄ'aQJłvuߧh2&1CYnk4Ny}`ܭ)v?^U78Z`"eچE??0Xf˅\\oj}#5ݱ̏ԼtNEMed݉JC&re,(JTnƹgvnل0 45L1툧"\70^?mBSoٳ6L[ PX(Æn5°׽[axǔ,&Z Fk#X&T*3U ~c٪EQnrL'iGe1x=q?>i*YxkDAG4SCJAgV#)U0Mܖ&%QjXДad\m]w(<~gn H'h#dU\xڔqٓM"O2ӳ4 inq0ebغmXN[.Zh-Y7MۣfuOF:^~i\wm ^;s]󷦺@x+xDȧ֬u6.-rF6g<34s#9`jY*x`'I܋hCG6YAOKۗQuSom܈@nMan9DуSV,JY)7$գąȃ_g%L7an0hZu~/D iF^3#:GL K=x0~K 8>Bް5u|15c4EUAC MǶ :t4&q,͐?53ĐRM&N|z3&* ![$) !U*&bJkl ]tXN6-\`a!`@P:< mQSW}A"ƄE,zsp 'LfA<15LSZ_ b;'㡩ƨkq+ ǖg^:[qu+ IG"cer*OkDCP8GRȢ$x:m9xݭng h-H(G^ՆC:/ 1䐮=P"g |jx7_(aYrnZ'Sr5~".lJ>RL"<^y^4{,V({AGRO<&v_ZLؗ5p4.Yb}y n)r&p.{U &.Kh*$xݒGuܼ\5)mpw| XP:Ț؆ԛNp+OI8*Ma1nKfv9\ʆ_8IU\pB5Cxzז}ejG! ^OԳvG)Py~4R7rȗmFEQUS3x.Q͌cN:wvQԡoCR]qB\ts95<496GXt֎.ۧuAsp~7HX)~0=,i`(|YT#L߼(\a[hWv[hm"4z Ţ:cG?$QS~t"L`Sz{;,i@-%c;==O@/OQE%w ?:6\=8iؖ BOΠ?AC L,T2{_k endstream endobj 496 0 obj << /Length 2012 /Filter /FlateDecode >> stream xY[sۺ~䉚\xuۇ;iNۙVqRZ۳WYcaggΩ T(F:oYe8J$ |@W8o@: Iw̻=~!y4_fZ3燋 HHcN)x|~U2kUqP }jní/ep$|l~<ٗ)ǟ/7\>rma`uN|' Aj^kXFV&1eV|?+S̖eBe0l7nh>MӎIc>ˇlSF$L0:%8fDª*_hӻ汘 ~)n8fۑ8 ־sRQЅ _< (#P,9Dq|V!Z2eBAn.)~^r~[-q請$zxM]ӑKݵKUWi1Sģ1;Ӓ[U.o8c6Xē/+&޽Ȍ80n>}A(`)aQxЅ8OR_wnN;Osrd#^Ш}a* Hf/#0p{G"R7AJ6mk"hk"[@sa3)+$6J.8.ILёX;/N4_jN"k`IZ*Xf>%wBi[6,_8}HŘ7[['-_9loOY "KyBkӾKmhhq*Igw}k:r/CM5m۵ !;&iQ endstream endobj 528 0 obj << /Length 2387 /Filter /FlateDecode >> stream xڭYm۸_aKm f$Ræi[e(p)Zje'npHƛ+_gf2n~x˷QJYhu[|c"VqPmuluop4Qp41zJ>Uno-wnf=} a1vv{A}7Y>}6ƇA~¢dM]wG,ML?,Y?l떇뛿Le3l&4?k>s}"B?yǔ n)MliȄ^HKjyPwW_Ƨ&J0XeY:< 0n&)R , Flxه#XJjj-8xj h'ùCo~ꭳle֫>-;jߗZ=Sכh&ش@z|hÃzg\fO}#eqx1SYxK^*s'5X7%F>K|gM Þc sqjvUiP' nD:H ,ӟ>/[hlDɥaj,ţ'Z8V?T1 R>5AO`;eSM줏lJt]iתAhwrK&i˃1W,Bv6:el=v?FEMyQ*]6~shr}Em'#ǖ/o@+3!ĺigkE* VY/DLnP!Uv$)^^V~%/ ;%֛0;٩pZ]`!M%ËM],=pE.˂%^91~g M 5)쉡j=L#4Z>dݻ<= bad=ߕw]KpK??ƽʇEW; UZi}Ai/ϔͫsT {WRې# I`dGN=s󎞿8+!Ja͹{73 >=;`}[:\FynzV/ϣ(f>_E#tOtڻXܾ&I4jk@T59D]1 qs8Ԥ̎w W6EOS; $x#Q3#I\`EH 0G&Ǧʝ͢'x v'#)%fwu.G6kXQfAb멯kd PTB{-|mSz +C [ʤiB 7BpE"|tM<4?=j?7{[L pr`-Dٗn{zw'mY@L6msXzN.eQ.> stream xZr7}W1y0@wRJb[R%ҤBR{zHx5*3F(qJ2&p;dDc1P>A" D4i}cg+7 쟭&YsxtyX>olrn狟{> 3>#oS+`V_ 9Hoӗ *  wP^w*8)d`}rԎOƧv@0Y یU;0K4A t;Ns#2X)p?N?'ȿfp@/a_.ZE[m'Ϧ)sW/Z%^P!)3\TG111q}J4t0h#5 8+}(0.૎B9_gt⢝cIb pF,VpJP;;ΏLE rB19x5 g[ XMCܤfWP]!]|x>y J@u(\FͼrjV&'bHWB’϶(/:<xj©GŽ7{g25i$b"k;o%{>/ cCPOXy0JzY;NFO.S8䀅Tc1MJs@hhdmȣZ-~&T~*kC< PxiV^NAc AYC <5o3Đ|zi6``Cu`M]jKL|18 &BѮ8e`J0S ΀Z|f?iz/sasSv[}wp$P?a*,f0髰 M翌RR)Ttu+kuk5ZZŪ/V}KU_R՗T/U}FNzr՗\/W}U_.F_8Ňk|?ڹϨ ˝̴Eu֭ )ZmvYaۢxHL;k.A\}5mӷC:@Y2M T&ݸ^#9+$͡U0XLDP'r֭ I*IuY{h.CֺmR~|@$)ڨS e m]9 JQCro,G"Z1\*`0ݖ6@K?̦GkbҩhX|-/d\Ft1@դ%uXLJK!•|L zz@8]p"A:Whj%8;,y@fH;(y7: U`{N`~XfY^ t($훤^>@\hӇޜWUt_dAD x kkxOT,$xnʏ_vVh (W " Du|aPƂ|ZⓔyAq"]ab NZOQϗw 9D('(M"7ekU^'[>~Q;&AOk)q67voeSB|dnbzG^u#uG>QYo&KHqñ ͱmvxlٿ;96@#Ӄabd[J:6Qc(cQul! endstream endobj 570 0 obj << /Length 1935 /Filter /FlateDecode >> stream xn8=_!IbF$uIY(ih$%vlH`<б-|t>::xV"hbaAwG5J;;u; 'Z%G` iCHk!;.y^~qi35#Xnz5gb>U$!P`Ev9 P[ sA"V phs^ԀPYU\!YVg?c9uz a@SV}p(X546S@wRiB `AH)U9ǵ8 Sz*xEwCq lF6+t;/Fr[hɥB@Ṉ,(fHFr*8FK59AfFC ьWS63Zz;uE n!߉d_KQ\%`!$啤:.XI7Fʧa o? eϡboإ]q1j=YL7#LR?ZRwo$5}-Ax0KE.!uik2Uig&e l//)mGaW/P@׿>V˨Ȅ_MDZK`:Ɖ'DV!jc =; s13L7R7šǴVXphXf3ʂ:R!!Wh0t>X0렬pxah-gu g## 6 >rCo,e07RaP€TGpfPyZzJ6DEtz Dеu%[BmࢀNJG`##⑾ PgDIp-.򺒸WAֳj/BAԩ4<D~y۠}=ۗ2h2y} {`CNr廐ȇ3:I"9` }}=,Vdr8E74SʳDې{@?o:[{{oT.NU[둯9`sV(.oA^pX#/%bi)C}c*؄$/ !T=zP{ju WvE!^*?E(ڀ|S])CuըU#Ts @/,1-Mtj.ɺ궡X/psW MSjvHT|0ٿs-mO7m6-o2A];Hp[ܦN`Rq~tӱ"֣Z[.xOJˬۣzUH]l E.+z1 ȊI\yZT׳,x@iEI%1L=:݇{ťBdY\Un[ = w6U@16uvm^1g\ӄ\Xe|Пb!Y[s2S0h+zƝp% ^fD$9Kx% @o ظslh[QH+Vi Sp݌w6_/]N"׾*4Bb&cb0wq֔[r9J\S쥄-;(r,Gj@;]K L߃$Ӭ`PC>&:,zۣilb^غJq#NQgf 03:P tu_N%ϵ."9B 7xn/u%n t:4έľrtlK"c)+>Č+^ϫB+{}> stream xڥXYoF~ ]4ZN-!ÊZYD)Ra3;\[_|>F^XRE 7zHk7pDlj+^йK$,O챕&֭ʋfrp``XM"R˕D* VjMۺtCp,A|U٨ͫT@:oa/3%yick+}eA;-MÐ-p6^']UӤ9,$,j4Mo?\,>w?P[ M 4.t.8Fl?3 9x$D(O3Md D1i :3Cor;SFn۪(6*3l#Hۮ.g8{%Ғo%aå 2Cqά{ tЃ|K/t |z)!suN[#x+ f쨚Xpi`;mEcF3uu6\KD!;ՎR "q6KO8]9@cDd>p(I˹M@Gdl$;ӽ.ugFB2 {%]'8ӦHX"qSǬR6m)utcޠL p}u*tL}LXhܡ;lNI4-_H$C|"[HN 1 {/4,~&f hKa;g5t1iFGj0@*i *g?lpjd&caW@10O1@0ƬŀiO <}DPc ,zi2dB5&` Uljfʷf̢:o<]]hsN@}!h#>@Pۻ~[=Vr=NJu6;yй/Ğ|Z:sZmܟ;fAblj.0Jn[lN,M.᳜r6ܬ/m endstream endobj 601 0 obj << /Length 1815 /Filter /FlateDecode >> stream xڥk۶~‘$]V>DB'/N{vS;^23b\qVﶫwb7ːk{85ScofpOt^g~(|,ku={aGI^=n%=7g5:jcu]x]4R2Nr\}:)Q&ȹ7GGzR;W?wQ8]MC`B E9G8#}Ά nJZ-'U]y>xntWקJkZu}dkē,K4b$撝ĹOuRe&+F)lb۷(`Y]e5NwRn'o ]nھ XTwN ~~a\鷖Hwu|VXHa{g%]1۪* KC\u^BAc>\F !<E'"Jq w{hi#4XhTfrCx~G_8\-yDp! K7xZѿ;chnD3VMNa9D氤U% =b@a*K(+NDvNIl,#116\JA̩i0MCܽ B!`IKTǝbK ɓc3Y(|QE,2'UF݀t2rSZǭɂ"#bSlEq=1f%h|MVG63  U yzF_/zB.IǽIaHA\dlO7cS%cY }+ku0\`J9Ef Yo.U];#cOLI5t%$ ˒3\pD/tW,Ѱb6[o:?y#뵓َp ~D۰x&M0moY7`טl Klwi V&`16 ެŞ'0̛lw}wF) 8y*uz[=ݿa!8+ &RiUy|"9 w@ExxkxXv(XM 63/ax@R2*Isd]xөfrFOawPۙn;bDﯙmX}^0 O 8ԙuwR~2? cX0miG 1[&:tqLځ@z0С׊]Tz~Q;O>2!Ǔ-%:%!=WM{>&kΦ'ƍ݃Ec1ן"qyKu'']}E64XCm8թuf6Bn)2 endstream endobj 637 0 obj << /Length 2856 /Filter /FlateDecode >> stream xYmܶ_T dIEP8u[#/qQp%]I˝/3R+ʎz@Q8Rp^ە͋o*eiƫ*}ƣx%c n^qoH1ZɓE>}̚|{U9{.| ڄ0W?o{7{ބPvUsT]QDGt{d =}jϖNE/2[,wfBxlz)'X4ս׵jFUL$C٩Og[G [ t'u )ֲǿ:m Vie`H,DCNiJ: !Eиh7=YC4/>c(r]4q7d0=q뻾x>@?#իC,&dӄ~۾<<{Umhl W#6w#(]s*Gukzf^Q}W62qN]Qނ"`a )fLv`%=epLa7w78e~Zu`/ h͓\)xs_TvS_f$,gLafN/_ux@\e{ xֿױja`X~-AÙzN5z}5$? BE9|%rBD3LsR(9o#b~ȟǯ9)>8t6.X AҿCP~6 h.Y 峫/'he[KRC}o_}z hH%C7U?o!P4\ V/W"Y vYn}RܮbaZdն_De^ӖS/:/0O8j0NC^)`EV LxyS}D$''M?O Cx`U; )~Ϻ{g;S54\ài5 ]Z/%OQqǹ2Re1ܪ>Z1ǣeV 0d"9X-w!KNlC\C@r %nϰ9G]0kMR1Ywgmڳls]f J,Q5GFC%bQcݚ Pƶ^! ikB찼LiFȊᭆҾiǁg 7'W&>'b AUνeub!' SS%QorZCIs:]vB{ڝevj3T};;ځ+ma`7KlЍ"cِ%R+[.J ;Q:E(`-`B$hwkU9JctDHUN4B9d(nnJC{"8<ǹ58 ˔8(qeg=xƳxm߳} uqtNsP/) Pjyf3ul:1KmH1H iXoCHYDS=ɟԎtݼ7ι endstream endobj 534 0 obj << /Type /ObjStm /N 100 /First 895 /Length 2553 /Filter /FlateDecode >> stream xZms_ EɌ-Gg҉#M[(\I;:ǐ;-Ph_Њm1e#(=%&>2}49]#t!N6cfFw,x)񁔆gNa1^OAJ4`(HF0L`,$`B"`9`΁DÄ/,0l1bXDg8d8ә`A"Ct&Jӳ,u k) O<+3>~qQ):|oEEEnƠÀ+{ P"&`11g)K&b,~rNoHg–h*GM> LJ QIatpN%d=h<`3&:Qg}Z8K&sT0% 'g a1"Xʐ)=CbSbQb1%CuJI~5䨧:r*C|*@br1iϣ2Bi~ >\ֻٮadhw:^N>a2=w/b+l9u4o {h<0gfLN_jZ6oGG=X^Л{ݦ_| PdUq9%HHl R)ZoG=?b̻njmAbvVU6dgI%un6>;[v 9*t%X{6hs+H_ؼLBm,CWh @zbfNa` 6wq6"f 6a>Yvrdxqg'0qxz|P"Tr0 7}Y?f>˛tn2=ư-o?v}9ﶽ_/fL۰c3t  佼l1:PshsmIZm-Vj[qǕ_]&u]am'T~RI'T~_b+XŁF L|,nm/a\ o6zc8CՃͷ+GO f+XWt>۾vY%2b݉l~nq QGhD W& yzԆ V OwCzᾄ$Npt J!Cu|9:"MOzuꋳZ `a]`!k1ulz4`жJN`K-a"B.eeu^!ݡl>yW9~!N{QcF-<gnX$"#1k3H?H4E2I=ZpMJD=*_j:|uR[M ǐ ћk,N>w0 DuD{<6Aṇ#cqlK{l$tm1]Ј]ua,I_cDNoa fn1ÂRGd0Y$TlܵOnh8p`ݐQHz1gh}mCmRXT\ajzgh+?_W~_dW ML4D!Ɨg= FhQ7 A/ߑN4FR*i}R(hP- #OGhKQFj\g=/ӳ; #+ǎ[;,KIF^6)̓Yݖʝ`ty`y}R# OOF h^rl(uFO[A]^Y5>XZKdt(++JU޵!϶7oݮē7/fzu Do`nt!z$aUC:l/zew! mW84ls8~[^oݫns= endstream endobj 686 0 obj << /Length 2674 /Filter /FlateDecode >> stream xZK6W44zX,lm8")AbOk:zx뷊E5;؃abT,V}Ui_{o`$fϤ WQ@M62ކh9beqSV{2RL`jg/ūGy6hy3%C|N/뺺>efHrj-:m5SzԺ銖ڍj/u}H GsⴿzmDVDϴԳB gӆŢylL* /{Ah!l*Anh>oG Vr_^UB9[e※ZwZ[mUe`w(8`AMp5]4lӼlױHz_i5\c_/f~4cUEq/{ [xN\)/ommIkn̍V@DMV>vE ֹ̽u:^T px䐾`aLϦv Lۙ(\=rcӛyz&?|LJ>uӚ$ƌXR!*괤fw6Jb'A+hGC-sHK }jһ+5Hp[3RVIȒXY iQq+[!Q 6@7%wj'i0j U;j.!c]=[޷VmUٕumVcc(ԝslKJ?'ݷBaŋLt}˹ jl|Z'-O6׿ZMˏyҚHā=I~7η rr|_V]cY Kˏ"- `fO$b\s^4QvQֆB"9C6!ߤ B%e߲U6(͋CCMpx8KgZb#^BյJij7کj Ad92Ԫ.j~- ěDMwFEG8!JԪ+b SJ pGvo%cSٓIkɟa[P^҈G g-3/ + *Cg H BI40ŧ>j.H/hP@SԘz (}yvW4=e9BA5:Jq\Ms?[tKC& rj }8j; ke5uW6ȯ(K3[ @3x7^ e 6Y/#_{f#3ar9WOy(>dN }pߦ̲{0/( ~_|9C"]QɄ:(,yS P@C:`dɫR4Orcqs~p̒m ݶ^p>+1  -ۀ K*~?-1} ڹe)8W&O lo‰0N&6a+GU&fI nWjR8h싅~C䱀A<6BӷyL̇Δ[4d3LԘl_JEC5=K 3 \*b:e,2L#-viP]&=.?c/pb,CQɲ;:z(ܦ6?y \]Tĥ8Yٍ,~3܁r>g=`u_g] Ѳ/,B塘POB3"pbxw+'j-Zywy@H,> stream xڽZr8}WQ0@DO2T=[[5YܡHx۸)F/`ۻ7~B _l8 "b,n6?8<ޓ4&( (1l|{8hQB+I+-+ {bS7U_wvZm X@H!Ly+TuSي`)s:lyJk AQR[Jk-Du۹V準ګof$?IOp`hA!¯h?eβ36,jcRW!_}_e?djfA*`ANܧ/׏+ }wX X^,s3K1b swFCпgxފ8@.xQݜUylG G1 NS& 0( |~/띚 }d)DSXFΣ復̈/H퍻*{-f2.3,j#)ܪhv<"$LN#'97vy-^<# ny $6CQB{kV42 K@A:|y%ږNپ-!nͪ.VioqIv,mQ&,ޭRɽ.wv!^RdUTh3ѨMg- b::W.SnC vvT[y_z[C[-ɲ;lǶ, 7Aa>_ _-? LjxXg]oT9Ӫj@6 :C~]{nÁ7LXL=JqZBJ0|9|RuUI!wQ\O t9XkM{`_嬞8v/c|CY ~M&ME-豶>5Ca&r[1gA7| O[TP@dSP*ni鷱VpP}!|6ybfarY4q`{9|;JV ѥ"m'JB|#HͦpVTcx.-:qg*OP̔,-qk0Lw $Wݦn b1CN׃~4 |SMJYZ;*LYVXGXH]YӺ4%G|rBQ 9W54Walm0Zx6 <.R2$;QWuxE#x~\]Eyr+ly RQTH\~@"@GZ.b(u`@N0[7M[cV( #z`}ʮ@AHگqR.͖빇*Q9of)(˽CIdz+SuFb4A18 5 Zfv.Kl ҆fa,ƌ1֓yljڛ]衩] ԉ?\kS5dVN$Q9@ҠR\s7LM)0) a<2@ EՃua08(Ǯ6h FZ/`ByO#ƺ\Cuk;F!T-VRɺJJddoHp+LaD]-+ws_s6ꮞlMUDg0hȝY+, p87;ӵݗ#f2l|RN }x5eo&ℵ@/_t NXw=aF}sZ=q .3TKo!i//_ o* 0bQ8> stream xZ[o7~ׯcBCA\6ݭMXE*dI}oD9Iזf7#h:!q&K1>zՈ(xŤj&GxS<k@o@0P$VH5jJ%B(Uu& T!Uj\Et?S5f4TP(oY,ͺ?[r0Szd_&ӳbm^m|}L6R5XZOنX<~lfLήj{7@`TKA3R!5[Gh0~Vlj=<oS( 6]|y\,@s(ͫ rL׿M6@ Gx|P~q~{bH1T-ðQ.šƁkp\@&9hh(b f㟾r5E&5 D Aؼ z!4LO0ӗǵyRv)m-7p=6vu[wy={hzeO5YKpAP $e7lΘJH 11nFDۨ͘m,m|flrF/7zˍ^nFO=mFO=mk`z$7` jn N`ԌP;y< ;D1;[}?=6={v9yg/泛!xCX{}+qPu.aA ,# ͶjD>}/q,A dT?tJ0%ܮlVNyo!08ևra# OLp~z費V~c. eJȽ#&:`rsHRɶBHPw_>vnDA fh jIbK[ f]CƇr$h>۔=q|=[w ilC!wpkCP!BѼp:[VcdB6jke1ŲPcZlt6.p)~@eQ!R8ZT؇QK.B (CPhK IyB4'xDY1FۂA"l`N?iCr("> U: `)"Pil]I:s'8P,E3߱1B} cĦ"*J`K[x`ط_I qV}DBU ϖ$4mJ6=l1JP-(-Z)%FhU[+@oG0e"("(I<(lA\~eVg /ZgSWt?K.],"6q ̤5&3Q c#CI#`cG⥓ )N%'#+[5kR2{PZvp2~ѱ2s$ფ՛q-ľL6V}@u?$"b/-k$vo 1TKRi}8(Ksϑn˃0˷`m/TŪVy)ТŻj'rѸb (0W<)yYG_J+hw<"%'+e;Q@| -H|@w} J+6ʏףf%ضF> fYu!n}6Isy9X Lb`%vo71;6{0R}~1?b'XJ:T>_‰?r~~qZsN`nm|xXݝˎloK JoQ@?FX;8Z Y~$&[H, RG, NV+s2Ю+nw欛]x0iقA`=w endstream endobj 788 0 obj << /Length 983 /Filter /FlateDecode >> stream xWmO8ί=oޜ^Bjo۞I\]^8ۥo)MЮI+D$y<:uv;<TL,rM}[-OP>9e ~LQ%t`|T-Ҝ$J/!_cR`o1IiJ SHEӺ6 Vrrxa~Q;:C0V,;EO ~cǞ& 0^rNŗel? +讷C |{]J7'4ޅ;<v FYnT,wQe*!L> 4Z՞- uҶߪh'AC 1bOf3u#fݐ "hFozM0 T>m,A딬]!t0geהҌVbZ,K"4@$-_t5<K7Ɠ/áWaF={+wv "UdpnJn0&,j"6W$U"x޿e%Qr$0y? :Df*6BQW 'Ex:U0䍒.?PWRARtbU-[Y%LLH^ސly]Em7txP::"NrL|/JTkEm)uE`e&;%WU ?qS* ő|TwOO"-Xiy{fR#rrk|3$n-16Y£rVm;RR%5xyI-Cu/ȶ:qMMNH%! FIV2*{qU+ogٝxD9k&b6oAQtGזjO7 L?wc_:*=#nu j;9/~ ӣ>/O endstream endobj 806 0 obj << /Length 1478 /Filter /FlateDecode >> stream xڽXYs6~ׯ/L>'3dbyq3$Dʴ-;p{`rZG'E[b?&3s].ߚ֭oOI9D>`3Jxzah@HA9~6%uYF.\#ۥ{$RM#dG5ńNK˼N29@X3rm'#(\ۘ%3E/G\Yj=4GVy$ cc{0MKгbE5z>RcߵƎ6ܘWBsSGj3W Vw{U\4)H?EԉW_ d|IӴSaWK@h_ R5 Ř4#VzS$_u- Iln0\#^i_ǙoSޏu)$51ZVsD(ZrlrI5|!ܸkjL!cw0iHFU%lCih]Kn&X!1Pg.ټ\KL%!Aǥc`P܁$lϙz[.υgA6(s$ $s xUWq":#I77yY})fկBl@w ߏ_ {y$_Am+ <,nS3 8'B7 | q_K8þE)Ê =æRň^`-ٲGz|Պ mWlMRtNpVcfdWjbS/K=KCZmomP; ;etd_1Sl0t}\k鱅?yKd// endstream endobj 836 0 obj << /Length 2330 /Filter /FlateDecode >> stream xڭYQ6~_Aꘪ"˕>{'  l~u%Xf}RwY<潹zy}4 \x7^XK {{߽e˶?ZK1 40%W̞ /sĩW>μ=LywfɋC3`\{~xlB^ GL6䓷yg3ƼMyn%h@)ҝάA?ʶչT31bۆ앾RmCkh٪^NKX̂-;Nlho[UVE']̰ 6ۄG<ӈ$?aE=o Ƃ[Z$dO]Kv]Q5 >̨`]A<"%K}~1Ohn<^pn89C=ɦ[srqA`uN[CAn#0ʏmq0 "ki1\ pu gЛnWԁӿT@zѸ€q: | }2~|vk܍<֪ !~xj0[m-^ Ft\uߓj.F QPD'9$d/(.fƉ0riiidɚ isO ̡R5E-dx]]4*8+:jU@$gbnRbAv[ٙV}Ub[4H) kdu1/]GGwԪ? h/$K`'_jVg>E+i@p\Ӷsr>੦&5g#RC&t2Waȡ\f2)2G<~A'>`|cW&Y@S%H|"Xo7k4;ǒw1Tq(Q{6Oojkq8K.`ԍ d,%3qAТhӮ(W: iѺ84)q:Ѻ?5o&8Rd6ojːi"C%`)N%p B jFgb*isozb:('OFHlN?E "ipR"yD1 ε*z?w鑨=-!Oä9dm>+ $sŖD#YY[x6T.q`񳲕6x1!Y6nWNvM"%CNr~I+ۻ*t;q>'-6݁lHzޫDO]d}ߙ:a@ EaO7t;)ːJ&ii`}Q6Îl ^sbߛwVڀuyNs-=} ( Gmݣ- B&&-F*MLT ˍر\쨲do`<mEBNi `7g"πJ0g"d>Mx!<v^][&} 2W@x /6vvA){YcX%rx$>E3T?nexEd*F|Dɦ]RocfT첀/棂p'gLsOUR endstream endobj 893 0 obj << /Length 2386 /Filter /FlateDecode >> stream xZo_!}]~-Es.R}}E,6qܿ3;KAZ~.~zp;qz\px|q-~X?J/p^. 7RE_P6pmkvuWM^uj\aD`@h$ `‰]#EdJb>_d%|h%4 HU_rgh٘Mq4t}_NT}暾>N$ʲQV3Hn3A@Rn%w 73Ӓkde +3զj%zTThlWWZ70=+/y- $h͒&1i͒Y%D1]sۊjm,0?*pbP ]rcݦ/})*KROshF6)>|NM]g$m$L,\ hv]>,ѱ(m*P2H@})!.=X wIlpo(;w3a-PV[I 37<1ǪXJi"&ߝlP8!Vf>w7?_͘K&:fA f"J|?j}4,jÂClNpG5;ۻ$a8x E{ {5xgUU&;pMMp\̳&n̥HR(59CbX1XDğ0 [0?2q]r .Jψdejep62ZXu'T1yaƑü!ljJGmݮdmT6[(N#xПUN&vC:T#w>qT*e%xmH8أPcIIvG_*Aw1 Ԕ/>iZVL dt |M߲"C'%VAi\Gp-4[&IPHY$,e֦i[z00CP &0:C׍90v_UƜ.sEC'(*5?ȁz̐1@pE&ײ>θ9Q',m}.W{V7TUchƅ$ cVC )”J 8$^zo0e8NZ52( T!Q>) +zCɨ7Uo~0*#5IzBAy'雹3p 9 78?,=n׍]A|k!8G0j_k,L))r߻K=vѰB|s< a4.d/ݖ:x;|1:;{]Cr']wAY1\W]Vmٜ3ڤ ;hNtkuȋqӉLҜ)_&E~,u姶j䇼P_6 ;~@ ɣy?7yF CvI:,hQ_=&а'~i/9pЗGA>y>ئϼQRk|e3&;UqF!^0|˹3|*O`JgIeO'Пy8%)w}Oս~+̏U΍_L V߯7ۇ*? k7;'3"'vͯR4,͟m~Kqs 3 v/r[ՏO09cpuyG6:Atg͘ج/k|lcҽ> stream xZn[7}W}HA޴ۦyPF#Igr6 |H_CgxfJWsp1g%(˙Pc)([jbPQ)I- ~mRT"p]Xc@T*h#&7y2 pЋKY!1Ă]:8 rbџ>eIhR[pTtt̕$'jfLZL$FB.'̩EJeZ).׈A[uY207q 08&9aPf]PQPA6Tл&|pM$DP$BW-h 'Į,`օVȕ &Rt( JZW2$ce~]%&Vt@g`+F^mt ;2arT` oU(Э"-! 7>  64%r-Dk _ȵMFJ EN0k/1Z#EnAkY00HXbHK1=f k15-k;>ɣG?bLWo6''yz`ѫ3tg*q:?OP%򪝘sHh=z䦧nM7' 槫{>t'?$;<9OP@<|xpWS Q9~[_]nV|~.gKW]cW]vxp24&+|Q i9{/xhb`F)dzOwn0GobM-@}!8[-qmO_!XX-(U-*M/ -./_-1 7:q~ ΰA9W)ccvŦ_öӊ36g <ړX-N;hM_?uӗ݇{}[/fuF5Oju֭{>ww>=Y~pf` Ɓ% ʫҪmXmF+ږde,V<6yz$"xjp# L*kR~)C{CNn^~8HIp#'8B8FYO`-AQQK;!܁nUsD( { L,#+Ux8?Yd+M^2y%GaN0DvCˇDmкa=KӤ__Ms0Ȃ(_N<?kz ay>5!U"w,ӓ|W+782a<Gv,8Ҙf@ĶSgwyaTU ~g(6V %p#T[QjX@+A[c-R"%m#a8pmfFa|,DΝ{yn12q8#~Ԧ1e 6MK+MSiQsb ^̪?L62bM =; n0o}Q`"N^s|`݇um]Lλn7~iLA_S?㚔߶_ k^xXc.h\ڰ1ԁ3)e6P0U6.5ahc'Ji` ëmVx#" $0ɠLlRbbbbbbbbRL=@b+&b+&jɫ&jɫ&jLr[<1ybg"&OL^5|T`xE/Aߦf^T}-u(\>qb6'QfWb QYÒP4e^_ʡ}uYH]Q?|Xa}u}`L5pD߰yR*DpaA_Z׸/cTvܗfF_>Q0ɨ/'wĨ> l endstream endobj 924 0 obj << /Length 2697 /Filter /FlateDecode >> stream xڭZێ8}0<E.LXd'KvT;."%Eʗj'qoէLıS>;%t@W9wfɉX4ЮW]#D%Q~%y~q>?_L< ap>ɾj>}WڡމUPwVY{IxQ3%kד$)RuFѦ#.+Ȝ}sm9^+GwI?ʞZ`GE3.Ǵ7> Jv{p*ιܥ;C]R(w~ˣ%oy Jp=X-:nwa8QR+ƨ/CU5'9 F > N.M 8NG /4}Zu MvaPp&}6+L߽N黯*ue.a5iZ\xp7MՀU}nO"2G:ьz;氅wB=bO `'x1F Yvb׷{R-;or2]iR,8]+g ٴQ"1(>p<'IdדCjIN^  '+* CXY+R^ ͂`ct>ڃTZ F %XLB1$YW@xB+7?zIÖQeQxRX[e0W4b ٛ4zmK>*Unay~] 2,|hƄ̂{?hPlE+A4ze4^bV89],Nem@?cKE^&Ƌ6.Ux69n(7 Zf`߅)-1^\,Rˢp[as6Gj}|-4mO=P4`$U@`u"K= X"kø V w JᎣ4TZqlH )o9aTZ `LPWcL/hMGsZxlNv%E@>W{=)^eSrY@F.C9e0,0^!9SŨpЩFWM9@0J7'yjVB19\rjWk?{60`Hcfl8vN>컀mYPqYֲtoIcߋ"f\ֺXGZ%Yg(c_Ṁ DF*=?][ flyA)Ƿb㯃,~ǐ)bF^+yCKη9GxQ:ѵ/@Y9?CHOmiA86:qIj83/{ō"̃ԼN,6Bb}XMyCj3 $@V*]MoaH ᠹc3i(I:A,9h|J gƳw0I(@jiۮ2z{PNJl<3F̩zݜ~JS%Ăyt\CC V{T@3-an$ap;di4Vp#(18gݚ '[Zqe 1vFgeHY'y8ϲ{리F(-6jHp.xFZ!}@c[ҧ}]M?]JJMFt/۴۩DU~u%r˪_X[y |gߋVӣi0e  &iX_zO'f٭VRsܔ2/Ez*S@s8/h"B>($EU6UYZVr @SKE[@Cߦ%O)f%cUx|qB> stream xr6]_5!/lrd: Ih(B@+.J$C˖I#{/v~:Y uG }Ϻ/?:[~V Şp.$1{̤94b^HYxl7_N-7Ղ@9ӗ{p\\a;Һ*|ץp04S;?@e|Jכ&"~?~}UN q?y F(Tgo_YIJ mM~GfPJ#?T'wX$Stڭfҏko,}Bʻ5x:D*^u9Tvvdž)۝j Ttg*ne#q^z8130^wyޡ:f5o%ܗx]K`ڀG\1o[zc H&V"(d$ltU'׭/(pO Qyǻ83ec?em4"ٺt ;}ya\!O\@{#Ql^R5IHj25̊zՉ͆ #JijJ5qQ3{F*uJ({$+K*z]U6(84:`N1 =RC5I5$V@M="I#u˥ ZOl"Zljy$vARf`@4W\[c8H!d: os\H5ܐW82hE2v2zz jn" E H3#oMy@?I],2R*bӐw[ypU ~;=hxg7-2stØqWIy\27 "jL%~~{<;ɮ`& MȽI_*[OO"jJ~d݄naTФЉ#b}Tg`J1\5ӿ.q*ӎ((t"Uj((+'&%p1Z/aI󢞾QxC7g%Ǯ0.{ܞ.9F B/A1zG6@,YR 拼 ߷\?E%͛`کev׵ۇA N~s)AiL endstream endobj 905 0 obj << /Type /ObjStm /N 100 /First 901 /Length 2363 /Filter /FlateDecode >> stream xZmo7_3LHKKpwi>(1J$_gVrҞ-R8\Fyrj*.#QWq5'1a$ adW(b_]U1&Gqɳ fb#)\LV*3ւvL%: qY-ؒ}Uu"cQ]LV.fV 5h uVE8qŶmfIb(8/Mx0`k ~joԥ q!j#)F<0 %N5DN$#.CuIͬ.V)OްbBb93DEr.Fdթ@j4Օic%29LQGF0K!bFB7 GLMO n&qF%{F7BT{~BxR f6Ghʦfa$ejWPf'!_Thfd{f5*A0;-6MJ!cʡ$/5 8۷.B #S٣G_roﮗ?OVn*RWϻ˭{%Q|Ct CbBs=vzrK[^}ۭ} :X ] >@=$U`.r;MãD_19{=}lb_,6`EE{X1{<^^MC/#D`Gqnn^>_]MF8G[P8Y|7!<$z*n;-OF 1 1ԛag)4{#sϦ68obnBfM0!\tnB(9BE,bnr2մ| ҽ6OݫU_sтDEjqۛR;bA©8KFb8W.F4"kn%N6ÔK#/r&b.c1n{Vmϲv왝>dSQS_W_<}/[S~ϰl~nYݮ/M4ܿ{wuxzO *T S8eGۉAXqNw# #cF4|4G|4|TG"۹{B_,O"<LIvY/vk;kt9EėG{JZ.;T(?IO;H~8m8& j Y$\Nk<5 aqDFKOKL1!al70P-;mNgldz#[aĭݽ|:KJ=T8NwC\]&CR/TLzQu[B$"uە8CWBcO^Z _xdy]}v/nޙՄplW P3䈃յY-}zR8[; ȝw믾vZ|B"#g%J#1 ։Soߛ*Km#\3+bnlv[g;\kd3)REmȗ$Q#1=ӂR棂dSILJCRCRCeo0q(]d(]d(]d(]doتс)㤥н2JdŸ{ck8X#!$L 8ŬӏeJ58o `I,}#Y"ih@}㵖վ17Z}c4o4A:bƈgl8#}0#o$ y߾dx̑7F(}a(mxn߰lUҧ\b],'?Fh@_}Jb*@I`>]_['K(oF`Yϟ57Xth^|L{g1Ŀ endstream endobj 985 0 obj << /Length 2025 /Filter /FlateDecode >> stream xr۸_>To!7;nDBx=8ɔ"i; sCaL_Y\z&u`=>Y_mY*gZջ eaI+>9,/OeS}؍X10,A.ٜTYOQHW%btVJhQj9u8b fsb>foWrUv')7sD5Hse[6"KdLzmWRY˥MY& x{YxjWȁ%~0<6pUKUDVzxB6 + ,Nݪ49EGUxhUYUr5\A>MZ@T􏚑?}̉\ y {xt'٨"2zbUy9>HMMvY;-FUyMv3bm lu<#QcۦHΛcj5s|^C&b Z6 3=ދ$fV&B0:`6:mE eqNV=JJHZҧT:A 7p! 7Y1)0, Z]#Zk`]7!s8msƔQk+ɲ> 8Bs(\a35uEμPƾ^nԦO=:ށ\8Q6}dLa.[FfBLڮp]i.Y^u:ȳޕ4Mz$FVZ:a[쳓$D'k[l)amU In7MLQh-\5K.dL lqHgޞU;h8{as&NOX&K؁'UtwG^DZ{ӟ.8FGbR1[Q>,R,]=PNs}{CG;yʍn endstream endobj 1011 0 obj << /Length 2169 /Filter /FlateDecode >> stream xڭY[o6~ϯRY)&Rtڸ{iAiG,,ͿMeő(LQy{;~9{<{u͘-}̋h@2#dݫV4@<ưZY-ERd əoZ};k}wgb]Ͼ{x΃W1ҽb0qݞ}l*E° O⁐r5A1o{[΃h&/OQ47Swfbۤҧt㧨EGŢfu)ui;Jvʺ>sĸz)U1 s 6Y8dÄ?bٯ>?_9gE 1د+6ue!;?2/(ݨ=qSJsh܊GcDKwnIEݩB4\"FG~Q)In+R Xoboޙ =j}' 2BpUz܈=uYnSm*2#0*{LGg۫^kh /JIf/:qMb< sbHXy_.ܼ=,̂b7<7.o)F?OɝQҏ_}]Kc ( | cDzy{oI(,'X܊[K|lZl BRrEbP.Yd@x*)k׭ Ġ"jӘJ_Fyb.)u-JXe!ɿI] _,ІCkHڡBB0Vw/F Z8!TTP4Ojȏ7)^$q*s] 1M=&үOO5#-qBňZNYG؋_z|kz{8q2n\Euqa' *)o|0&1rR 5i%G)bOjrʊәKP NO8:'@gL'^ѿ>?:LTwgؚR2y@4rH8r]~pc9=0υZ|K@Wem܉ XiJos(ųw"ky0G1H5ԏ fC+[/Vj*:LEbqv-iD2=hr#6B Ũ^T;b'rQ&5KSz7":\K8f͑M9n-jlNKDZb:pԯܪҙ> stream xYo6_aIbԷ!m!CТ={%:&K(';%Kn`ɻ>)툏xfE,m4qQs9hZm%ZN!Y.O|;].XW}vp+nޮ<ё4,|<=SnW YԪǭõ@پC wr0́W7lmE<p8 èt.ඵX)ċ k&-KeJXX "2Eu# B&'7}O0>2W(J&QyY9u:=G)YEӕo%38Lpowl pCfSfSRX,H417A"%0pEK,VҜiBQ., ȧ߷ArPSsV@C ZZzAJ[QT]A #ၶ~tpY趁9 JK͝U du/-t&1*grE}L'e 3YIY# Ӏ`4JSM Z<+ E3kL. / Yz'g ,5x(r)_gPa %)(`Cde!M͒am5א`O\kLΚɭ89O >78i+43eOWTMĵ} 1 "L >CRffF]P1"Hm[{̙P: cXpK%li޷ aoA32z *n9V t*!\2Cy#*-.G|\؉ac.bfclLe@# !i)-PD+NIY0Ekfܼ28SJ*'\w4n2'dXgNUAy]S/;dh{IJ=:}Xy|%TiaӖXk]*LpQn d&.woG%y8ArBkwh/bA?L}p; xɪ>Q/1˝?sqoy>qY$ZIz|boD!XZ"_@]/q/`+S+ &)񑾒GS `yLܡcĉ|Evm88@ρ¢/Tn;4m}_ yTআ6S,:Q lL EA~\ _UV?+^6#aWxΪFZCS!1|S'&4ۄZsT~vFc)m=9[@pW볓'HBў^NΪL?pGÆ8?yes;?/48P endstream endobj 1068 0 obj << /Length 2132 /Filter /FlateDecode >> stream xڥY[o8~ϯ6pDRԥyHtڸ) Ymʒ+!y[ DQw.{]~z^BjQ'<([ _V>ń1kZ\-c yUՒŽ{7ogGX@|xo|Jb,{$ 8 Cwi8 !G'a@I 1j2:VX}[/yۗLP8ÉK}YZ H[ ?BJ(̉r(Ł1-@uONyXH[;RC!5D?" īSt^(\wձ*-.Ң쇞dݩ~L;,>S!菋="HiV#h+'w8UZ$Bp,!wpH|@JXhS{Irj)&YT>t<YU,%iqtcBZ?TuZ?_w7XyZ yt?k 6)\=cgw׷oL)Xe{;u^1&no?K"z|/]#8hU.̃ƢyNBH$X6Q%S$= `f`w wՕ zUz2_eZVR޼QF_ )FJ!G@@8 .?kuh iyq}Bv2;K|a\8rt{eF&T cInjdr2 nj/V}lf5|)IA%hh0y9DpAsSU!w(} $ηIeFֿU6Na+ aWa:U.;D[L[x+y+Ҏwgr0Ԗzڵ0xcO]UYQuO #BKDH`w4at3`fyHgioYLU&*_P, ocY6r`ͱhEUeU^6Դ^ twq`o*csGSG^Z}&3 {ADDM?ZޥEԓo(ޛδPm`:34;wDj3 J+fq0/XxPYoS6҅YZ쥞 f@ ) TP o N%f ;~e%mmW+6͵ P]W*"8Z@fu4޷{u J.ij%]AsIT@r]>AE?QLT9yg|nyTN[O5e4BzS<"rl|jX8ݩ8nA7)G6iN V08K7xKJqs;UcZi!{hF {QߏHffu7! endstream endobj 965 0 obj << /Type /ObjStm /N 100 /First 963 /Length 2611 /Filter /FlateDecode >> stream xZr7}Wq*Wl)*[%JʤCR{PIǐ/"fiitcJqH0\LqD2~bp,SµXE;*(:Oy7^2IX# %,2a `tN4K:*XXlHtT E`q%{C ;@/9 sƠS0.s;lXxǭ]X X‬h sЙ/,^GdDr/0#)Dd (uL$   aA/4`dBtǽ( `TH+"' #\R|9uB "aø1HwTzW*wc5,|Du%uMV ɉyQʙS3/eoli,./_}ݭ9Uc-C]&2/®>xܚ1̖c , i M+ M~Z.[L~:yl&fΗ ,Gfuoj:-V Y%V!Bx7r5*$o~{_? 'wyi7hJ#ww>@y49:Mֳ{9 ([%lKs6J"oa䙙D[&谻ydx9فˊ+k k 㺢_WX B6Hm{V T@PGȁA"ĪbQL7\[#zI53;jۓFlzy J1f׫:ͩymW2o,Q0eugXL[t:$ϮV{jѓj) E1{*AK}Ӎz"HCDuWb2QTHZ7g?t2-S ,}l `sT[MA) ut{ٿ^:%zCrIیNn ߖ7ͲneN{}O[`.z"0|8yOj(}cvT&-(F G7$iOaì} ᮍ(g<741ZA9K5CF$(u6q7R. (i#Bfk4gA4g ƝsUY$*%@:o2zW#mA[2*MޤxoFo_.נPa%7?֋)600Ĉj[)4ޟ|d#lFf؈nۢnÞįyIk$Ik$H Nlwbk-Z[k)${A\^O*-tW$J{8!sw*zX?dKLZE RJY ! ?A6`3 R?KgRȆR9δ?=gB5f;ECc_ endstream endobj 1110 0 obj << /Length 2093 /Filter /FlateDecode >> stream x]o8= ĪH}mȡ"],hugK^JN3Ra"v~?uvSR7x4-F\?Fq乡G|E#fsv9s*'RAǑi*M t84h &ʪԻYSdfn)`4S7 #s0$֛,S+T9bz4nDk{NBs.(HQR-V@V*֍*9Qk|3AzgVbɋb"ryexZ>Q`6R-ư6ߑxcF}FX S7=WvH(B,IB NJf1<a@LBGzjͤE2Е?7)DIkdo&tѽHiF A1O|u V ڼ*f?p4-;zikԙs򔉌婷P 1w,\(+.b#X) K>Z~YdK4Χ.x@#`su T?kΖr-h uc1zƀ5pvCalx3!~Ϗчp†i3b(Asg:} ݖRܡ.D jj ʩ 'bL@zώt XވLg<8U]QOSwHY͚b8 XKꙆ ^eء'%Rծq^(#k9iA,^hTEfIx{H'J yLJN;b1U:7=E܎"{w^oLaq #G@O_NAf(Aip"KNsWw\M|\XT7!'oZKq˅-VE bC L|ϏHZWވw1+9rF4Ƨl>?Kݜѡ(x -Jrn ;6lh摁2L]8O ?|+2xN;҄uUi =A9[wL^y ֛èTYK0 +f W:uLk g}:rzNkpn;O F?t r+%Lc4_2tZ jr"\~`FSz(y|1ڢ3wk縟?Qsdt!ף<+5W'm7, ؈s)%8-Q6RR}Lի {e!;vyʏх9zdp nٯ3UlN}Vii$&qȨOO5ɹ 0.#EZctU A|dk~F1TX$4P+0 l8VYlX}4AߢJG6dwʲJ/ff֔W{˺9bZzXWwX84NoyaVgCgS& c*N8M5X}/MMD*\wW-c0M})hw'eKDfH5-eg$ͬ),ESpaHxg"< endstream endobj 1171 0 obj << /Length 2314 /Filter /FlateDecode >> stream xYIs:Wr,TK2,Σ @n,bJ]@lݰ;/'g'h:iDl1\hGd4G?${ϏWqؚGCQsl5'" vة)]wٮߏWA8M<( |u4t1߶ǁAO[U8۝6+Vr~"V/ФIby6P̲ZjDQ՝^2?' W7o~Y/D1! Ltt0xF缪@Wy`j,zy+QNOqo7Q#ãYSsUQ1# H 0J0R]k*%ˍeUW<B@FiQҽ=\Ζ+?M9\l%ʏRwzEz;rD*6`߱^6=5&o]`441˥Z+6hb0[ .4rD{]< j? w I /zJh{LM֗-YmAֲH^M-z˴S.w[WwWQ},+daь\jz}yyVV՜}zՔu@P݀1 O^%ND뵎/>n\W ^^}z ~^-20l&Qs54Kz}j:5RKE&)rÞCO^;n"+ئQʞċ {ey5G5r\ub+τ>O3ZZ՟sZ׏b $ B v(p-5;OWL=p}M+,=\.b6 ŒUe@{? Wrc/2q{&v[h OˏeѡK?w &3 Ťf?Ex5f4|7qHvn6FI'hŜfcdH2j;Y;ȾAdK8"`KwjBfWRBeCQ7͖Hi*>@a{$, 6(a8CW$q¤DZHM|W1 xP{rE{WiZ4Zp};!Ux1 lkͯ"4P}x%+2t^NxpL:B90GP}&Vn4: c§OЦ|> #J4ɩ2#z0!^rG8X~N`NB(לjjU IWf@R* }zQ $K^T['B '5ʗN 4-"~I*tPzDb\ lQh2D!sΖ_ ~6f)KۏRO hTYLrݯ0gFeFي$J{NS~&;~4-o$RTգ R )+kK,gL|'m緗gK T?LuvɺyZ0y0`^5\7PMjN7f&9C|Am^tUuC~:{Ii11Ug%(9 @ r-9咵N⽂/-L^0_m^>4_?%@"C'H{dZFy1ͦ (g?TLب%L~i`%ąSS\0-/rD Ye!},mh' :zN> L\>`;-J"z';B4G' &y\N^CeK"ὼU\C*¿ׅ7g{~k wNmxͮs8*!wsG endstream endobj 1075 0 obj << /Type /ObjStm /N 100 /First 999 /Length 2642 /Filter /FlateDecode >> stream x[[s[~ׯcz<8L:qdI"l4T~ 5L8zdjyb Y2ʚ^Q78DcY> "|腰cXeMd8p*$Y d'DI(p,2JVDV(R6B"k,n"r$׀S4(䄊B{( TƳ9Ql|<+2Ã{d WsnPY8gƔgI9)d @Z e Pi kX(a$(TgjR.WW7 /jfan燋zzx3_Z}~>.%a9 b:Z^^x ă. J~?M1v؜|Аjr`4X+mW !m5{*n\m3A`w?Y.6e7a g04,~îoX27`>zZN '5zzD6]}:~5΁:.@/^ޮ&z˵*볇QWSR>DxkܿDNU;"JJP%sS+\99WιrΕss+,rGJP%[/;9&KSeZHh!$nN^o=̗f{L&T(IFl%cL9aII!%;dqfX&$ {p x5l&(HˆR!v-B= 7"{ 7ùpO@.8=@Yʏrnn6Q4I3:(<ܶ^Q8FwMY'NKDs |yXޑxR6o` oe ɭ-9ghK$z/rճa{A(x,p|)!,dŋ6B_b?-M0('*{X!hsG`MNj3SE tMo(i Pb.q($.vHx~dǑGl HEbgGn!L aÒjӹ2S'): Et{Ip[H%Zv~S4}9uhXt=3rR怉axQL'죤rbsY1sOҬrdsCP9SLC Y+'(}BaO=҄o$GS*r7A=-A%;E$XQt9~I&px^f32Mh:'՞Ѧ.|~5o١!kMhM :Mo}_d9OAKC9oΑ'h}hur(mv%> stream xڽWs8DfbU-[fB4Ms dڙV`i+[߮KؚZغ|w}5~q=0bƱuߋ'4Q~}׻OWq1A>a#lD`Lj[RO+5¦^ފ0[0#[x. ̹<v*쁔s <@ gD[}PK4Ylkztӯdezva`HFyH6@\| dm"0C"d OE&yk?; 8(SK#&]|~,SZfV"2Tp:sVY7י@0==RDnT0T:O_۬6b Cyw8 ը^v(]# f0G 0>?`:GSo.&-#Z>Q7ṽpPs RQU?fB[ooG endstream endobj 1231 0 obj << /Length 2015 /Filter /FlateDecode >> stream xY[o8~ϯ$c %m"A:,y-:֎,4iCR+ R)΅ƏԹuU9E|x?8$3Oo.K&*{3$mtqcⅮ\6geSnb3p押}gqBYܒeYrYIC w Y[v+Y7U̴>%^泯{_&SR7+&uT&Qr =OjBWdySMĕfMJu@!Cnvr1aO<ꊪȊ[LLF]fv T q+Msg֎߯eaFD;A+vlgV2BJCV˦E#_OA0u`S{]Lu"[Q|l-EQw[KU#'܈:C9NZqxV\۪U7fYeHqQMuОDWR#ӬCOY Y[f7n0Oq7EQ朘 >k P>L}sGY_X;NF~ ]ʱ@K#װǺ[q7OZ }.1뤝u2},"oxWS5V~| תOzH|&U,:ܩ`v_ש,lA15"=ځl0vol؏=:@^ G*A4~5?䦆o:'V_OvF4y>3O>~ɠ?O.]~*ً%%ctẅ́v%^+CJ_nom9L}sߴk0whS.gc$0\4J. }:[ͧZMFoM<6{.om;E4^ ;И:=ְ$&󆙧}@?e Řf쑄CO_}f彺X>kʂtAJP*tjx~Ej6[UR~\<b}vRT>EAACz;CA#ȿBF;Qe,<](0hnEy'IzZlb`f޶)7:tDxp}3M+5v{?9/`A3y],߄CZmyAn[/?.XM+y2 =r|_[}7E> Y? 7DaPb<$>E ,_R 55M6"WZdE q,g`JdV{۰UM2U{uPj~ WG?&fGߠ@TVjܓ#|ictB] Ge\URM%͐(8 UYmC Xc:tHOBnTTB{V#4tN?aq'mIj8O_НOP1 L[qwƶ.ܒ ,-z[S)w:@_~3esLjtɅ=c O79 3Bbkv9:t y8[[>1A{S_:s UK 5 endstream endobj 1246 0 obj << /Length 2040 /Filter /FlateDecode >> stream xYK8W}XCQ{`A"eZۜCJbQ=Nc_XRTWU [=Wo^}>W'dɒ( kƩ ?c:D'kt;Y?ԇrNzc8Nہ֞YڟmQ c<qRZ]šSݞB:{tPUװ]|ɭMZSHZ(^:FeLGbD=NSKE{QֽR:b{YMa&y/V9B|u&/1*مx$S_bl $Bbxn6,p,s 0p?Át̼Hأ/{(vmU.߁$l ;Y:x!3}bT!oᮮHJm}l۪JuGwBiCh+_М)Uɚxk(1sq9iVA0? wp 3?J, *,-1jq)na `~MBF`Ru-K%{<Ϝ c?g9cEī{7H$ʤFD~Q),>KI/mᆻȹ#!tRwb G⊿ K%x73%^.KPY8*ap.2CFJ~> 6zLd~cڦ-ߦm*Z/xV@F[hDA7 7T#]#8;EAHvlJGp,D?<`̝M=FiNl\@ѸI>g>B~RgOg1|njD3app0g%Cjg>9|RK i%7ZbY3ٴv,u 6 BQX&~1N'zo{Q5N4~AȮswXM';w0GiQDh‹lXq `It.ϲ_ & \wKEѢ;uTgGyہ,In8=/Khtw endstream endobj 1305 0 obj << /Length 1585 /Filter /FlateDecode >> stream xYs8_LP$N6M}h; cay$8M'"K߾56&6>> k痶mxȳm m86F̤005L1a&c0>rNp} y6lF\,a-׶-AbyEnt,)-/))-"ǵ&a$UL< y֌rTQd_;[oh,cln jb?Kl:Z'>?X,Z$&OaSw!n\|}L☏a QuIV;.1m"?˞4-/>;\6Xuf3pe C_Ux'M xTuZw%c,c9?/9^ */l\pu}#LF37RVqg2TP@ XًIu墫F 5hye_( Z(Rx?C]< ߿~uӽ":p"^y8߮dW=PW=}>M~괳TE}EoEMs8M!ަx.Y#q߿8 %{aC5`ny8JSq?V?hqܝѲk-|*5ˎO_#U{s[?y:1ToT!$CCܶqc#Kџ6T8qk$a`,ujןm5=SS)TtٮRBF,iڑfu| cz,l \m]\qg\~Nq}'% D> stream xZr#}W1yƭQ*)J9JdrCR4Ȗf, gspF_0ޗj>W33F&TlrI"TþCD﮲Hx?WOsq2jnzl"$Cp6sj0U\ ڙzC%kPR<$,@(`Q 5dB`cBqP cLGmfG09g"ɛ ;21IpHDQdb&e<#H_* MTRI2e3c"TɞHdMJ&Gߞ&1V+a(r)^ւțBEy#L]IDєQ2e T`=ˆ IplB07 &d8,<^kSφK$4n Am&b2ӨbTbSc  f0F L~$4Aj(xZ<ȸʮ=!ڞ<ި*cc16$ #6|22YDdbΥ/&ͅ ifq~w{ob6/^ VK=vSHȜm.@F&K.1q:L~|}b&oksû?L&00_1lX-Wjޟ⽹.&KX r}K@f@/6[j[V`VNT*$9+rVdV|rݮhr Oɫ .dRm -lPb%Z(Yx2ۢw7 E.φv,8T8 v^+frx|R Xl]~Yoyv,j$l 09泟xDpeJٚ>\F^&`c8 "uBl.>z>ոb6s`st:77rDہd{NUnN[ެG7m2[ 3cӗ %$Z!{]MJ_"́Xڳt/{u;]F?0c-5lv%6E*X 5tPnXo/qr"eDLeYq'ӕČ{;e_6!1\dR;Lf1? %Y*Pd,j_1?$}`#B'9ʚ!:B xmψfIk22?ofeS_R<5'VSUs٪lfRnT*$ EVA"{E+Wd^"{E&E&E&E&E&E&E&E&E&3GyjL5؀ v%;%h3"EmvyHبQ+1s5G09lbxe>}|N׋dgT'Ge=P^|g}[рp{OuAY;V6 XۛJ@2X}r3VcxS{6Mw@xZF ]Zb9|OG2iijGJ e-l~:TJmIjӚm9%ԁ2:\Yhy.3+#m40:PYhy7v̽9P[ N 5+!5& {RfnR6+6ff]#~bUDOoF[𷂅#leĚO 3\)my'Wt cY0C;輼1"Tz3!G}̔ǬĴǼ)S=-W=O\di-*bg*6ک[ܠO;DZDCh_-@RgTV|*4cQSҦg ^IlIwU Al;lD>aC&THn@#%=> stream xYO:_QrSxc;1m0q4v5ĥJ.I8vҦh BȎs;NfG}{DRP1LGc11FܣI<'IYq:U'?bc#Z&y-fT $<_o5?(wc`5v)N)vܒ F6Ϡ cQk89d[ZTLf]R͌L ~-Jf1b8]ʬZic컪W. dLs;&Qyi\APKyd~ 2Nq3Slx0tĐ HCp0_,Vd8s0V==CzoC[_]1",@Je\33fy\ZÊͰp%C!ͷN.U/ַ&hFg1͹ m|)k4+T,2G!o@fa1f91 &&_Oz8R( Q25\L40 t(;T.TX^jL'#h@XyN6PrDuFЪgyN^ȓ-Uv AYYb1dQ}|aڜ Ԍr$U놴vLv6R5jZg$]ֶs-N?j;joBcpNQh{L:ZKTIYz~7SP$1լ!6fSsR񬩢4oj^%mKĖ02U *[Z0L˺|Ɣz'5|)5 ,EuՌ` kY|} Y O*v)nGkE̋.*iՂ׌si\t"'PuU{(έ43+XnR,\U%aOq @s+6 %Zluo,ř &n5x {`s,s0$}SSASL +M6y )Hcڅ.M.Z+QS@F)Yq 2X}@,wQYH{-csv`DxS-$beul Llk"G[u7nT$j3.HΡnB˾;8xPYƽRCnh`yO}@\zkz Vo\A74xWtzͷ!E++6{" ޯunv@SaQ>/G.F梉i;JkFXuyuqА!A# ICzxw^__2d3IFT endstream endobj 1369 0 obj << /Length 2282 /Filter /FlateDecode >> stream xڭXK6ϯ`@UEyHmٛT%ij89P$4"e>f,F|h8ƫnpۛ׷7߼c/ei,bv3ƞ9n /yHR!c78忿x@{KǛp=VSEHхF+ÅQHNwy[L,"A"؈1p#MSO(a*I5XlX+}uo!Gm6":hx@iC[S܍u+>c6;jf#MB&ۊqam?]vW1|R/0Fj7ۈ>c ނC5.ωܿV;_p¥s{e}mٗ hEk<_8_*y'wg<_ˉq㐩Hbb xM1KtIׁy>^&үNnmڐd}}[j{tnMғkmz g0cP}(Puk+J p:t`@i9 <Ϫ . Dю.'b <ͺϚ QK=IeV96jYGjfb/}a%VDdzlY9?i6=*q!eH%r!ʪ{"ج%d^% N$cN5ɜJ@>ِ0kwefi 1iΛh5oq 'f} tsV5p3gcK֏+ltB蘕HE(~lbVQWp5WC@S` *8.rԚ𯔠]n dQtIXuE& &/Fo9XDDŽXNCpQftǗ֮V'aҾa4![ 7Hbkv> 2GA>ٲ8lL j/s.(J-SG;jU&$zMU 0vB-JfD;me(/)PWmQlPuC(L,ǡVQN6KW<DokORb Р7MV$>|.H ͌#B],Ŧ i,R J^[q(ɂI -*b˛%O ɖE[]e+`i8ORwVuJ9K˻Z=6U+Yqչ.z" `<M"遍?pwXcbŢr$62+pP_L`f8[A7.aKTXrIb͓/P+#)K:2i Y} LO/"}b_H]GcQXFhRk@`CהP9{V\# P4a#BEG93<`7+<#e~T>uia:z={\g*f(]}sq(re-v!dz YGؒ Xڦ]ͲB% endstream endobj 1311 0 obj << /Type /ObjStm /N 100 /First 1011 /Length 2580 /Filter /FlateDecode >> stream x[Ys~ׯcݍʵU>7rjm9]~QD&j} ލavFJF_3b2>%(F$H΄\ odrNGt^#; D{RR(g}- rNߐ!/32DEgd6$J)w~ ;Wf>ԹŰ~oo8N-l8GE_vE%AQTL+lR Ed] o*Ire/`J%PlpYd UL%; `fN2馰UD(ѝ &Fs}41:.X*$Mr|1ɫĘvr&V3^bLlR ^)1);XflRd}l 91corN"S\]%^0S$o)(gN$3bɹR`lJPΩT@+'~dRR2ޤpԱlU+tYWr]l^ȕ['_yp]jRI ަS"r:/ /͉61MUW[Ϟ<9sg&OlryqS_<<[fñ>L~79<䢻ژ$F± YZv*qO͓'fri&/-¾xv|X|f^|zh Uw{Ǡ>>[M?t렊 K8 jpfV3[zd +;nK'K? 1nālpT= (6,Beښڀs/%.yGѼ7ug[n ?m$>nppdph/BflPFx^Pv` Q +O2y[#(EM|}Mg?,n&3B|6=bG #?5ռt &; X~h~pr AȉBz¹ַ7CA"h`SAfs MΖG8oo|-6y^%ٚ$8bHV"R Oh7,H,)X>oۄ!BcΧ忇5iP#}\":U!ǷN?Bu8<YC!?rlk'Y5 v?,53tF=O qiqAnnK'#Y%R5Jx'wH!+${R88qojE#p$I= 2X~z} Flh=24CU N5hMZfQ}9 4tZUl*3~G tZԌT7 km@+M~q3fՔbR`︸޹hajbT&=Gk⮕L^-+"F*i"=6C|V[off+3yṁuoְtzyۺvl>}3UBzdAQOo+0z5mW]AjbGp#eGkoDL358SL358s̍378s̍378s̍48vP6@v ORʑ_}=dޑ!Y6m}}Q: @cC+ǰ|PV Gc֮zH/^}^8N*BJk#Gu(Z<8X]~ZUじOzo0?s endstream endobj 1402 0 obj << /Length 2867 /Filter /FlateDecode >> stream xڵZY۸~[8x9O^z3)g7UZ'.FR#ɯO7%j'"h/n~~D*aI(~}Ig7o}퟿#vsŰY^vu\mdj#"p~}h%?jởAZFK~'厘Ja[7"; ڃ&.ۼZ7]Ҹw0iڏVDW1˼j-a gp& X%A@"WFB/o?UMo MJu5~5HY X bb &ʘBS1 O@AB$VS nx IbA<$ =Lyk2v]M1,v BCmt`wUew>i^Z.uOQL+;±ޒ}CNu} HiM|= 7sx|L4Z1Ad6 K A-` $ByYAN7H9!4\x7@$\1l"/r g$``52^=!VAjDV{SA ]CV#lMJ:ٖ6f=n!icqzH6U>eRX~!%q4q]C|>4D6nl.ӉCv&|>=q70+I^*o%79ΗibXb}mΝhH-$9̣Whq6*ؠ&/8ay!*iW {#Jأ5x1O:IQ &/0$nqt@n0pιŀHQxs~NF$Rw 5!~pvxi0z Msb].hLO[%ia7Mp>yFz(Lz Fu+Q9.qy_&'l.(Cdorw<4Db+ -8J%éL)%K'튉}?|Vz9 \2>S$!?  %KLRf ufo>2 rIRcfVFS!G˰/IZbZ8㞲 SyK%"*x*lϪUtKy$A-j*C ~*{G/c|;zBSoxlBJ}[lj Nq+CZ %BzZ!E -1PH V<`#/(o!?n0^xG-);|EU58|fFT_IH 5ҥ#L#d+7EomF16*$Kѳ^8_ƒ4k%&*V6OO"wS]60MMڨZ&z2s}ٍ.q\x'TႄE E DtxD!}z86/_'x^ϙj0LHa.bVa|oXce2o;g,FPY_AQW$_=/LÈibIpF8Q'RV2|Nd5 l3D4 EUf7 faqWDK01 [8`X9V@pH1,5iTn}rW:XNF8&>6*̾M>^ߝpF]֏6 _F07CHbѷ&(fYRaZ?+'Vy8c [AjF+8pH /kP8yȋjtϟn_] endstream endobj 1443 0 obj << /Length 1732 /Filter /FlateDecode >> stream xr8_e_,,Y20M <\GI8vlBfg}.vl7&[$+:Ωk-zu٩[|[3 .oG˩ue{tͳӀunzCahԕ),Fk p21 @iCB^BoB#uUNjzN;+ȸ0^4p 6L8bW:שm ОRSK0FYQĘ wk%כWu\ך[ "oY՝s5* aaQ|EF!aka8vp͂cRUZU57Fid'(xkߤq[O-\:Y(a *Q95$ C&s{NLd0]>aҀ;ܠU|$}C9{ L"7z%/ĸL6./oD9E#ZYXWz6̚@T 4x֡6֬}ID}[ *yVJz@کy*w:+s =6 3%QEq\ZԺ!*ŎU!>w&?8X*IGBƈlgb<ѽBp&>8y]Tm jX& (LçʝMG橠v_q^GZ1ǭmc~Z!]Nj:EQU'|@ĂCkEP+ CUi~]tD"ӥ{,(v6(7,>m,jpQ5o;zLEsIۿkO>4r> stream xڽYY8~ϯ0֌CG,v6, %v[Yϯ*)Kj'FETUX`qo_}&Vw0"__tUW\-~MA-/yq>y\ߚk'_ϟ/oKqEΙ#& Zq,LѸ6):% _~޴}M4HF제,R=_0U4{d[~IʢHz lum%/V!RO;]?wH:M۵S;ݶ^ t:o3X B/uٛYDqTϦK4Gxu}SM6MVKC+[siv譙Y]},#DP-N02v1YY+wUk4(i . pf-!xpȲVtoAMhZlM"`iP$my!.^Kϖ-0);:@̚]{`znA7pimze5N-k8:x{5=X *i $j+B%/mGO,xn+< r_Qt!jt&k'?lk Cdf`@G)2@YnDC\7[oE 8UiږFmЌN#ƒ˦˪f4$c,p;YmAʐ61}k*}:S 'I ̡}>P沺;?Hii&X#c W .Bd"VDf|!9PKzJ N[uU!SP(Lз .B]u|Pl2'm.:?P? f1d 18,BvPnZgᓹrTNV<l>[AH[y*;ʎp2մpGަ@3%P) gfv4iU7֟g fٚz݆LpJ0a ~GOxl"%lIVpR>K TepSM/-p)X)x8Y@OcK3X ,I XbinoM˼oȽ`,&wM pn sbky`cY7[ ¡QWYt2f q|N{ܙT's6U7;\}l@*4S43|Z({*X]EiԶn;8܍++t4sitњYIHF|w}ؙUdzM^,V4?0[Ok{5e`yI0){@Xtۡ)<Rt dL#V >3k?d57b(We;-ZlY3C]}BYuhdV5Jt}ۏG) ⚨, SX55=<+_ (g'cǮJD6`VHs)w;0(<%8bRʚڝg\ ) 5uU;8ieW;׻ RXp^ҟ&obeʵ0!V!~"F!9SG@-ȕXf8M\?LevTEY{}Fx ᷢ ոN<^BΣCb~2_T ѼVcbzPZ] J*RΛrN>e0e*_keqCT(cohWAR7Z9P_Z|%nw+>bha!O''3ϛ@1a?Nf endstream endobj 1380 0 obj << /Type /ObjStm /N 100 /First 991 /Length 2714 /Filter /FlateDecode >> stream x[]}_EZ*X*nBv,{lӪ"L)=զAImrR'bmB:6IX㝠-p*VY1lγY?؎o(_3+KJhQ=$Ed 8%9$J\)DP£Caj' \U*쳰gN=%h)P0@0N,]E=BBg8޳Aa6*$h= ':C X\xLQghU!>!^qPr}"bJIE"C**֞{A 0Y2DŒ_OmΫ$瀖AHQPJk-Y UaNGlhZH1DT*->ko`vO*Kpi:r7*P0BS(0xq Fjb>`LQ%zϩ g%xUvά_[⥦ڴL :ËhS&ULV}ĵH:q iv5lZB]YDĵXgO?=R/,קQgj+v$N dz7<ݭcg$ݳ5dL^!X0^ZÆ4]X|:ak-9k8m{1lTcXc/ soV08f7z6]wKB=zFϻKywwb;t[NFgbv7+WW?U/x#W`:xx%XXx0Π*V "+!&H\|SyTjBnBY 4i.MsiK\44e#V;u2:{Ooݼy9idt &͠ V;h8{>Sήnyq=t0 !"&|v04|tv[vCҥ8%2:1v9t9 nV1f( F)mE3̀8fa?Y^ݻ쮺pprẚhӘtM/ϗew 0 xRr} Lh |n> 8@f)jDam7dL ay"u0m7'ӫ܉ 9|u"9qZL@3~/`0,b$@rq Y{-m2+?(|k|ZCHkxXo߷B*4FC#~hC4Ǧ96ͱin[mhZhcӜ495ͩiNMsjSQ.H,’,q?0Ec &vHǗv`Dfn\VQ܎hv-{raL$\-;1{С&#%ـ dBX Sv07=~byu,~6IQ΂t ۀ#@vx*2ףbb-0 "x\З1< x#ڋym%d[5!Wcfx XR;H4㉛sF 6\6nj\b8Qñ>eN9!mrp6Q7njdvDt6l67w*-n|;j{36#oT1G*MVC [9ؼ4np ז86 u48,S:)=cTia\+> stream xڭX[s۸~ׯ}:+$^2t6;C6 [l(R!H;_sp@䬝d\xw>syx^"'eiD=0rc:w>᪅gςWv ].ݾTzU: ,ByEIH{eu\ s6߼JeooTKjq HN'Q8q,S}m`ZnJNL6i6!!c;ʲNtW_{,)jf7w9f \tzM<֏j‰%2 R\6rgL1  dyudsmn{?o7Ύ>n/\/>/|X9"XN[|99|MOYrf2m)p(!R&?I)&~BWXz !m:ZQnDYUYm\m [h=E@tʺV4R=pes ϭ7/}5\?<5V X /bI7JgMo: # WMSU+ˏtHċ 6W#`2D(37]tDZَk5 ֞` 0XnjTv;h9oʊݸ dpK{3 }TᜆIw ~i<,1b?y[qXܲ*l~V&++olDa-fevkw @ՍR2w+{'=N܋ՠ^Lȃ>iզ0Uz*8~㢢֔ܗ á +Vhalݜi<.%q_46TRA9jl|dO6Sp:ЮlPmS0dLk+B<-m&wjli\a鑆-L"8~ykfkXmPϿ(](z[%D,En lUk3+7HLa?zw+ꑅlPL{\k41z4UL@Ծ%Fm5M2'ɥ`4*U!JX$nq.N}ʉp?Ǐw}Z9ѣy^ endstream endobj 1544 0 obj << /Length 1777 /Filter /FlateDecode >> stream xXo6_!t/Peli:u!-YcmRSߑGʒd[`0;wG[Z/ϞΞ]8pk+ (]ǚe֍_, ՈE}*:{=Hj%gT2_kqoPn魶n>oxRƎOzɑX% ݍK!jH& r!j; |{Zc8B^DV%g.#ˌbœjE?R\^F\)R lA:h7qF"Q{Aʌ"KFGo1(fkE)%q1>JZr睼(ȡߖ֊"{ys ^KpYd!'z*3TfkӴ*YS-ΠO*aT@׵>_ v[J:Oet/5 e\Y5?^H\m7Vdwy&/xu9d֨ T@m\IV} VqiiS0 1c~r\I7JUd]f\ #XF$d!v^h뚯7FrDMVZO*40>D䂛\i}c54H&u^w%5@8) r%&K@,8+ɭ9PijօMU2 nkeS hs)@/M \VN;_oV|͋Z]XLC&r!8 ]Ϸh>RY@"hu` )]< p^Siy&YRR l!HKxb8g R$EHa'DOxN 2H.b^`8y@H֦&eYsm !/_c\ZVEMBx>(Qp Sר?-/ br{.{'ߍSHcWK9-&#>Dy ?PDط8!yEә"á|AvL!_%⢔AX 9i#gw o*?8Hڡ Ȩ:8Tt1w]H`2`E;GuPDžŸ jd84NNh7"D5/cmw}2%'p~t59dxmJ$c+ i_RM߽k>>9T#p:?ToWj3p3{uT:\Cj&y-F(xNt*1Ԭo@חo./fGp׮|Hxu9D2j1~Ə׻0}v&ׇ,dmou_= ㇭_"9m&}9;|Xt l>D &P«}-(۠Aje]{ K:x) X:.PSWH8]40ojm#$P{J`_EP#:j"ͩiHMVRs.t^eNF-Ax>k;r޴ $PM87/d)U;K-.m ԦXH)d_ cֶM1MlUo`N?Ց>ԑ:Lg1zBp+M'(k27rnٜ!ˡWZ`^"??{i*T_tP_~M_9BȽ3_@r@ endstream endobj 1571 0 obj << /Length 1409 /Filter /FlateDecode >> stream xX[S6~ϯ`eɒiز0teh_؝c+MmʿNdIv: ؖ;G& ɻ3Ƽ,dAegHd픈ٗߝhM-e{Q.+E: wL~բa=g8ޭWl}|wF6XX ~j߶3|2(Vo2m{^~u^ $Z5WVS*KRՎzPxŜX!)7Z*49"GA!DʑGA iluie.6ʦ[O;Y:i>dJ^6L2Q-Sh$W=?  8 ds4busBtF۶YOFf6J 2ϕlVYf>U)y#='Ibj 1̺\'ES̑a"wkp<X/OHs/$H>eisc=_+EQ@7%Ǫf BoL6O6yU_4WAerz Uw/xuLDF`69) yQ:#mM¦*ޚG1o|nmF@`c˜?qDy*lQ&+lWrUOs@T>?VuPuwmnd 5oeqYZj%w E;6j];Y7&X;a.t5xlVDb=jҕGr'^ =C3=8 ǧ;|!>Eu/}aM2ȼ"-fhD5bn+l:W{%:GSt#DzW3X*(]X':z62 3.J69 KnIid.7:0T/`H @bϩ$fΜ^Sƥ,|J4GKBlQBGcCF:pg8Ts˔q?4/F]׼0/ SKٱk A&EzIX~ʼNL'LˆE=>d i5jqdPdԫWLAls'MbADPۛDվ a> caޖ7;DXD d1 Iwnd-Laa|{ Ŏx!]hsD"` @ROﴪ^g>٘`y! endstream endobj 1493 0 obj << /Type /ObjStm /N 100 /First 989 /Length 2419 /Filter /FlateDecode >> stream xZ[o[7~cBs% $1EN4J|֕ I&~D1rdE 9~C(9?l rT/섲5iJP䊪5?#tA+Wku-mbDS GmU`=*HbcdH=Ԁ妪@MNd8IkG)VuEmȀdq =BG롁s( uBk%Ǚt5C%q报J Z?شDB֪hԕfi  [Q!6c]T9lrNE>ZےH۸.Rq)ַ1` DlPLL.e2pTڊ1#;'7, +ܸ,ao hKlVY&&u *+ktE 2Tu1DK"C=5k6jlxrUlbMStTbNB3Q LA,CjnbBihϫh ?>fOhݦ}ףtX~={ۗ~Pa P(zU8ᇈa/!=~f륛N>,g|u2/7߻~8¿oÉ}Sw84at@$zy'H OV>^,~R#`y1UnAŰ2c~xُLIN* Ftwf,r|3V߆ (H/>%[5X-ݲ:OS/ vRvQG3*/ ⭀"τ$Ƙ`ĺ$D:lb."jZ퇍I@ڃ$K5x˵;@JR{Gj x3$ْ|,{ j +Q`{rS%oZ[i4a&~UZcq+5UiFJ[F:v#JŃҊܧc$,35z@X!V6*%{{cvR7:ENHRꄔ:!]u=pܩ.w5s]3w5s]I-#B/Z\C>bӥD%~}t#&AĞ+]{E> m>=:> _ W9!vd *X)8ܲ-6Gkrq~KP >J;Q@`}Hm(:}b;%oG(=AN; [Iގa_0p!"~1d1rpQcv!lml,J|0X-Q4bٔP}7+~#*CnӺ/_]'p0i3ُ07` WpxfkU"L]aݡn9. }Bsc276!`W;@vCЁRLEޭ# ƆSte-+w3Ҟ`$"';ٗp+؝+-W::路 18ƻwZQ:$-J"J#$NR)[=4NZ1)֑$Ƨ2N:"T*kgS9~YeR\{^ok۩WwOOOO]sS\kHaf{ "pC} K@b1­Žc֖S.DiL0VG"]sEr3)cŵA8 o3cm9܁Ykٙ endstream endobj 1650 0 obj << /Length 2369 /Filter /FlateDecode >> stream xMs۶_I`|doi&zHz%+E7$Er*J<%].tt?_ݞ_j5H`t1JH(GS~Z_/BRFtsSEShMєk\'\u_JtHd|yr zCU~Lnnd [.+<.VO_'LM1tCєiB>t?ntGϝzaТ9mT 1*V_j0˳2N2>tHT ckbMޜh%ꉳ|g&+ r|Q?[\3H)\ƥ}\TB"!Mf]ZKgӹ5&0[6fēBMD͜0w弘LY$ vig)#@kPnwWƮӲ_%! t*[_϶HDfEauYOa 14A T^SOMl N4p5~Jwpƻbnt4DGʖp|y~F$duxHkک[jJ%R.#9Qܘl d[Bt( 4 3VF l]]p*I4j C`޽Ԝ;E#:zzSsxtD4eW J4""|]Q$ (J䜂AZ˜ykO SΖ4|0jX#Gb,rُӬ_a?~ʮCut;މ,zBkR~- f/ /Z8ֶ-|T}Aw{(=uVο WXx-AKy, b=?T^Yq\_$z](`NeWq26!u8 hx!a?7Cb;.2 FDqg^!u\&.b󑌱aTY[^VqGwJǴ :M\IBXMPٲXPqlI=Xʚ|/Z3NN>,@B,/ c!vc@+S.}3@'%vdA6 mR?($#` w\X3 ycDޘ*Ax| > h!E['Z|o2p&IE;ji;s8*8ȳ {|'-":]ofjش@ ;$@N'EA$Q;a&oCe7NPaۿc4<@Q=-$lnzme o _u,sh_k2$(;{OIϋ@@Jh!ߋpNi";)#.NNᔞa eOqS #֏ 8<8[6}#bdB7o CQ=q!E1/w0_LL:TJJ"jT|5'㯄 jijiwHE x {a@@T$11ʿVTHN!p瑀^g*9#d{EFY$CL ȇ䇒uo #Ѿk=/.oEQ%ِ@D$Tp`tʰ~ܞ=1]~:寀VDM]$YKttsY-{b#?' ;. bv]{DƳ8M^ HЮ% Sɜ\hVxdv]4]wB[+^D`b= Lp#fEa/zk<7M&S%ғb]?7[3'&- u*]̗xZNWeq4؁oz֘!u},C{7DdN]Ypm=lG۬~Joϳt†seT#g{"Uߪ+-jvpov! a]CU`~b@w endstream endobj 1661 0 obj << /Length 2392 /Filter /FlateDecode >> stream xڽYYoH~DQͻ-Y/ &dȖ]Tx!bu|u].ŧwWQPBE^XouD8rE{u |w~@%pYo>^7馕ݵbt~m? )pLD9Y]UǷOGB%=/"Y4_?],Zy|p+'z|4otN{"‘|77t<0kV zP$aL[.4,L.mҬ uۮ)[.-DYď4,! k֊i]M_XVϕVD a]]im=w'|'ضn[0O|){" Xh>{j2UVWS3`CAftt):޴0=A'cIb=%d v4c{ X( Cվ4Vz62t~dWRMvuZCSg:+iNjiU2OlP/7_r߇7jf_\4?.0GΙ^&$R9k4Wb1!:viGlEUMqnvTQ2|طEh˟Wb (Tv E)zO٤ɰ[A4Ct!\'p^pEkvg;=GM#8jSEg\?cӶV K/t4a,NQdiYIQ@[3( b/SQ"<_ڭ #򁻌^"(njA'w .esLyH$cu{it$D-EĹ+WQ1BRvYܹazlgil7Q[gW<溞.s9̘(8o(g6 (y<?;K^]FM˻g)P`eԯnMVbҒ]ݗ9kd ~SFrAS`!㇖a |V?D|spR 'Aаcq|A7`CW싿ů+#!O_Ű+$ ThN¢m{pJcMbFLɔ&Ӥ3T!< f߰'t'1<,ep9R$$j #ǹՉ@F&U'#!)@."ϮN B.=5B`Fŏ}ݮ.5;NHdg& o) {`>& 0sԸoi&eg] H6Kbn.X.338އq=L(O@eAq$?g 64?'XO8A>˴~$ }hsxZCd4 ! )KyRpFnKL0 ad LtSq{"|w+92wEoT`PYS-/yNM !U35 ~f/t6@C seж(y!r5qD@s%Ħ&'P"ZL=z8/|| gE=* 慝=u^=L ld(1v߷42fr1a|+sZ<3opS '6C\~RbD i߷68c^pd9 {Mdtsjt%߸}RKl`UIeHWTY?,~MoxN@cm "4)$92OL0d@Fr>0c*V|* ٚG0Bɣf3 %pnxdLΒiX.T єdK%O`= }'Gp+[!( L9cٴZLhl{AkXayG0MLOO)pESkפ"k|>mrrf9nc \NAd561 lM}8j[$MũCR3ckd+ncܒAkRrVOT|T+e He4]ݰ}]a wp9W[FqR SPV+LV (̵GH0Q dž ' Hz@c? qNUxڰz;_i" j2Q" 1PTs hiIozvp endstream endobj 1580 0 obj << /Type /ObjStm /N 100 /First 1007 /Length 2640 /Filter /FlateDecode >> stream x[]s[7} EL3SN[;Ƀl]u$%ʛn#]R΋+Q 3>$1Mp2笟㳨 q B6L!#)ϊ Ls`PDM^d`֋[LJDJDgu"HD gV y+R,]kMj!1I"`MJ~L*NߗN/pud-Ó$$dXW`J]*u#&E +0Js3Q\`shpάv b!I5zS`woRI}^<.ƠU*&eu(ЌUT(\ͦS{)UP@LuxMwKqU/Fm?2S!/Ơb]|2"݁1&A A(gg vî4j?vTKg_|qd+`q%eIFsV7 [xђ-vшC7H.yL.dv?@hTvXW%n|\ojys5l3兙>l~׿lrif_<\fXo~a6X~0ot\b Jo?_,P0j n4!4!6!5a44ͥi.MsiK\Ӭ!}'&P ҄Є؄Ԅ܄7;iMo}f47;ifjifjifni榙fni榙fniYfiixou>3_lb ɫ_ԭo!|Afbʖa)BT x2\ÞMxe&_-_/ 6.oWw{97w׺mb kM5b!> kv}5,f_,YM&|a HF7(! lBj\mRG<݂"Fn9 r+X%)sn n v䭗hoogC䃷  ^B`ϗ ]$0 9ٳ9v>Z<`> OGNE n˧|)V"C j.! b\<MO4="XVBX:kv}>]-#ljhPZ%*#J"JVCy9Lu,TQO9P~J |J@< Ѡ\$֗t# 6VݣA/ӻyNcaowEO(jq.T*AMgYO!CωbFFj1(T=mv{뻞̐HVhc |Z#YvY>0tzfâQya8Ph(djPH)K PڛErcVǏBẍ́\ 17{ #C C"ӹ>',LfC$QGc齳Q;_HiS (4 豎전~ b>w=5'P(^*SCI(8ۣ+0qY< FT n8c?1~^͆f~;YCz .ؒ@ ~- `1X:@R.! (D?&TdQ$nDăct^( ya+瑀Np<99wQ+l)v՟>V'j I,1w/dK/fy޻NAads `R4P°QTE#Ie^q~7LW[ ,r=ljpy8˻wWeݎ0(6`Dj%ܡascG3?4 (BWL4{,\C0 ZE3 )w5Mã~\9ͽHdRfءW\ > W1LzYہvPPXm<oVӻn!Pǖ#sj'Q.`JHM̆PLă' Bg܃% #tzT4~^$ħΘ${}=Qk}5ҮE8O']ڔ[6'/%; n|A9ZյAjhs$kڋFOu)~ܘ-5&~ԲأK1R R]Yk[ֶW}_垽i,5 nM"T@?ݟzt&| nY;®X/%▔/aJgaNXAጝNħa[jI;y@3LjYҶ''N׳9ڷҧVO&?m\{mpr/t|'@aS^FP{Ǝ[BќH9r.)WN endstream endobj 1712 0 obj << /Length 2264 /Filter /FlateDecode >> stream xZSF߿ŽK`v<$0Ƕ.hɒ-XK*4z{~32z/C8pps8gzaﹽ{2O+U<g/1Cp3Aw &%!>)wK5N2ɳyA7\`!̢Щ'$-"dU8vxZl)Piqb2TɉTjy-b*EJ/pz\E'.lJ.D1RRMB#z% ZBM㕦7qT;Ԯ7B;h+}=+ ;~,1? he xRkT_B@mHB"JN4[tmpCj`(ѐ AUyYLD^+BD FPDp'S˄¬&Dc)!U*\(fJ1WS Bcr T)zBC-w@[h?-wSʍݶm4q:0,7 gT% _XdNN.%Z媺 WIcVzC+רNgR#<ȅW5 [kFVBvRTfgH]{֭S $5=drőhcv[쟁6yz x7T`Aj>$Ad?VƍL_tE j^E U wIE:?f45_bѻh--HvI` ;K?; |YtcEыGya_05V&މ\߲nԆ)c!E5>g.Ϸ!nb{\,.:p'n\*&%tgw @pڋvdCӐlG, õ]M(X9U9 mؔ<ˠ2u|4S*>sH[Lsǂdw[lH %nhoosns_T{h,pTh1 D'zL{сXc0lCKZ7"Ǣx+Ӑ@l.7]UrrmF^%2M&okHDAYpK= 5Ǥo$`ΫCU^ 4vj2B}!7^0?6Vbob"Vn ϶wVo^ 03?gÊP>ŝ~+;o' mC-ڌ UzE%}б^"yJdARb`RrMoj:WٟఽB\k-sk,yG[_߫8w߬pL߫p 5?i_ AhQ,r<5#0> stream xڭX[o۸~ϯjV$uݷn`Ey#ӱNeKIM_3RT') ëg2 0x{U9mÐ( $dz|\DbiWi<)e(u[}yxeL']S/(`v䙝).Ig,_MM]뢃1!~ 3€'i$OaNX< }q Hà輴#xȒI$?{O g#w;S%_r%pa2]趯fŋfO5E1ƩJPNjs_ E|Zd9 I8B[{”l W`;珗ڔ{]wDF71O 8tanI0:- mqHliŌ0 L,cYyENMq6V2Yr=xE-J[,+A,vXM u㒍B=Ml7mGmtilSI$Xo~"2p7iF2,gHnFAki8paxetWV$Y*""J7e}5Io(-Ba׶5ZoH}8k< וV~MI' QcHja;d2Aם6-#>/di+CsT+R3#ᗵ`Fu 12W[lDXm;վdB"`Gɷ y6SᴶAA9 ?9ir4"q`BxP0;l՝>\[2@3",Tg9c#v 5|eGz>#fI/L |w)U7b׋+-@Y4>fbj ȑ'}m4.*aܮٴ'*H;Ѱ괵3w6@&ɾ L {sG HHݺM]=TE(7/!a0;9_tK 2oڲcTYJJheW.B/E>u`iP,4c^Dz)Syh3S,m)7ڍ4TգWuy`v\m@+'`%Ѱwo. - ח?߿{#b\##0)!3Z D=FOĺtn1M0=13bHBoV90p P96#MT˧8 m84 lv[L| [ol/Jc\ajd-wAG,wnyN{</2]oXF4U<Ч31_ 4H69[4V;>4$Ơ. mo5$lVZ} Zu;ɻЕ_Xkv{F)Gi\LLFrKAQǸ Yoq|Գ8`'Xgf+7mQa:lx]@Xhju<!C q րj2-1#,"nApm n]/+a_٣(l`7J<9 `QDvn`ٶMDYQ{–1ԩ_ _i hՉ$a>y|sKm ;O((76JgN8vs( +p[PPW'rB-N%#EJ-;^KKpWg2> G3UmCҭPn>;D1U(_Uy}& <$a)[)p/ ?F/2<8'vjq¦[yGd)[{mAEKw+UBZF1h⦔ޓΞXW<=Rtq:w endstream endobj 1794 0 obj << /Length 2295 /Filter /FlateDecode >> stream xYKs8W|" ^|jNƞVj2dYܡH ACQ[[ t7u7D':ۛW?]$&qb(%B0|rL/EYu󏟮URF{K^Q vL)nHJ\eSSOz+ӣ֡ڕY8@7K 8Ei~kxM Pe0QK3C3 I#V:IU'$9$3N ؖro1y33['L2 X?һ֎z ήs6{g8c.4pQ8JY$pJt|Sۦ%7Fj,fO`8=P2(*}6A ,N4zti^#Ѥ.ϏY! w<- d̲dn<_;[ZsZ3vRH+⽝/dXϷj%k.Vv\ T^:ƒ)S= +`TEtvō=U+\vAbט|Yl2\@ɻF1X4Ǎ _W@ V,UplnoRJS͋ҺPLʃ >pV {ZgI5T,sR2[ZfN2 AYTdꏩO;gc|Մ`dDx\9w yP[v] :*|88 ʰ_w,e9# SՀCF{ NN;#9\{ T4|>d'O†jR:H`OyV_vR6$.P!,C1yU9 [~b]V4l+wn#^T)o;LG"IE' R\buZ-vb|Jhp7w_.R0 8wK Efcn,ӭU6k( tS` *P6\D!a-kA@sCty_+NVPB{,I]xsS{K =y$A[>$>bK(Q{zy  J8v~MHfJ B0?JᏋ371c Xf?yEX9 SS)9;Wozs]dcx>/'i{|*gc>>U&ϥqr~,1S Nxgj0]PIp'*ul̍E4]"]kϠ<VŷslW0t6>/^K4?k(%PddU]qZ]L?E{u)cm :Jm_Eo%[BDe'hR2JL^ϏW/GDT|Ǻɩz&sl<=#Pr/\̻^}?ou(=Ϝy]]޼f endstream endobj 1729 0 obj << /Type /ObjStm /N 100 /First 1006 /Length 2594 /Filter /FlateDecode >> stream x[[S7~_EݺTq U + 6k{k큰þ@'K.Kp\ H*$W?!W7ؒJEmvTO qS_R,[T\">*ER]vd\Ku-Q>jsji%9mQm4qXѲXTTǜuh9B_ :ORU[`QD ;G*e'9"YuR@j.>7w,%)Q [ͱ@ʊӔ9>ȬVRpY~ } }C:G(}9IGGhn}60u}FA{F]I-(8d~ȥV\i]Zs5uT]iiJfV3AfHP&-iO̐ k!VF# 5Bkc~itv\ BQVHjVEGW,JwÎ݀+N(cS#W-JU5X\ɧdɝ;' nxdv Z4! Nju6ܟa8[u]k{~]+(qQ0b ϶aae'$6AL& m'T\Ms54W\Ms54W\Ms347Ls347Ls3mYN&$6AL& [O2{rbxdvo:V} Gb~qH VVC]< /T+uw7~tfW/Ž &âdcO|3ANqײC; 绷f zW 8y\k$q\?A#f_'_}tr™>`081sMnjׄfG'XS-@S*y"x~b^ =x~q0$/`kb6){lO#\϶61S\O AF3yB>iP$+\7xR9 8CUtу7߀a۳ s@4<'lZਜ਼sO\[\]^>d¶5$:&:IB&7Z0Z.ulk̉Dl 2-m 6Dc['qm:55VHEσƮ%cNhj/k. fw4{7HlCjydvKnؘ>aް.NNNNNNNN춊äKNUڐ a+}Drvvo)6E{4"a4GiQ$O "%VZv#<'=h5dJ6::e0/z 'ce#cG`ESYPE=WP{5{iT5hAPUWEx^oL'BDMч&Z0Wp; UP{%["'9~bXյfWO/Hw]ZoV/_GĒ-tײNAF?ASk.sC)hfGN`t:"߁|E}@>T'D)}̯kJRt+JUcR1)1&%ƤĘcRbLJI1l-liΦ9liΦ9f*V_UX}UbU꫊W*V_UX}UbU꫊W*V_UX}Uz A/h)!Kz/ܬJ:" }" UQ%䈍򗫢2@2xVFwBZ9leT)D(2hVFuڑ˨ Q qX ePǦV UQ͑ Qt*:%T{,`VAeHjPKW;tfu*cTʠxDֺ1P>OCXQ;l0gO$Fv߄ endstream endobj 1834 0 obj << /Length 1597 /Filter /FlateDecode >> stream xڽX[o6~yYQ$u qC>6h%fٯߡHJv[A <#{w7y81?pV;{"4pCj|t)~ZzIB)pgwB.ǫΥ2 ҿ;g~<{HEup9N93 py41sB"n%+^gYz):J4a,Ҭ6EO:3lWEcby>B? /請LdEtJ-w_%[)2Hw3elϦQ2ӥ2iiyj7?|qG&զ3z56޾YH4@Q܁ؔxt n!MN@uaCzUeۼmŶMj0}x>FY8(ƕmUQA R]Og0T>ɥPXtW E~n@0Q%.hĘ5U1$qN*ބ C@T%(*c)mO.|l|m6!ؚhtk:NCWHIŠQe&cLK5t1CA :F- Z @IQH,*,]uPnU+MoO=%fz ;)I`?p &褋XY1gPoJ+% *,,V|ԳSMOg_րGUe"smکvBr Է?Msјs%S"*Ha5A>2SuM>kZRsLh`%&ai SGB:ϙ4zI=DggS~`쓮l i]|6(8 R\U5S~#E|uqF`(idpIa:"诽9Yb~{@ #Ob*.gHN6_i78CvD_!|Fb|B B P> stream xڭXYs6~ׯjK 8i'i&>$ DB"yXq~}X%t<\=],ek6^/ffD$o,Vc|#m\j,㓙,ߊ榜SfꋕW"nD2յxC+NIe&h ;lsQO= YCYqY-f, ۏF(I7bSVgrSj7Z!tn_nx7M̫L/q5ؠdbz_[Q$[Q=IzwuO8\|x?䱲$˲-O($g_k)imiW'n(r((En!=\Fm<֛#]-fw38l鳌ѐ5H7 ")0ύǣRaʠ9 ,£t JyE,Erc5 rqWs'{Qb?T)7ú1 {Lt:JSN{:?y%3VВ6j[GD|}/j<&[q$Ncx8$c誴yΥ!ЬhmmzBk}9:񨗡RR[^ PKLB"셍I>_ V vY>GzwaKqIBa/-Em*ZQsj,m'Y>G@H|ןV*jPgC> stream xYYo6~ϯ>@%%RGТfm-8aZm::w(R$ۉ)@M f瓏ӓ׎cw,ǘ 1cF̶ih|33kkuVE2S gEy_R$"-4ma=clrN!6f_ yF.UÉKiW0i 'fI@0E.Lhe6A.or5K5URMfE'xpLǛ"ׁFc035,J䑨c0|j46S!B5ǒϕlDCe5:DQ}|'N^=΁9DŽ1 xY[~*,q4ry&yz,J8psRzB>x'B.i9^y[ܵ!ګrmc'=%]q">{ׁG`M[pR20& 옼/̒U,$?b"xx+ۤ]?,ﾤ8 |SUY)DDC5`_5b2_C|ٻ&U/*%>&)Iđ>K"GsX{Ln^?wVW\zs< ж wE+>%[)Si i]Mdg#ZzzFz٦XmG|כ[7)Uu@C֭ʸqCڡJ\Onr8bnR})w}|oG`8Z0l R;iml7rAr/l#EĠ.^'w;]S9ǐc/׮nuF/ST=Hۘz횃~ff,=D3UPЩKyQyT_eLDYͭ.][ZհKEWŲa}$W^{]BFcW}ѠwH_ nc^QhAkI+E.$yr|t K7_vېjh}0ϳ> stream xZ]s[7}cB N3n=v3̓b]7*RWeIXڙ8$x. 8 }8S*xC dX`$F$TB23Lb!CĬj,q[0䜨Ćv(\FCu IohYgMJb6H)& \X0FvQ,A?D R0!rP!cP{`aLI?ac y1B0o!=<1Jp&R2\DǀRN4 U|h";-h\e"s&h-)HLtlHD UK21f&_G0H|)0#£ 0 E""#$ZCvZIT;H8`KyFam_$}`UbZ`fڗگ 91B,+#L=#.bWlSљ+64. % BߢGU;WC['QQ"όͥM=wU#Ń&>r=^'oGlX?w܋ɏs_&'_O6y[Ra:4!|)a򑬋҃zz3xo!1+ CY$ M`39/m9+ ̾ndbJ9w:Nk|E`rWm߻ruh*g?ضlF ? jnAz$5m dY-͗1V^ӿKHlMi8\ .`j7 NAhs4l^."+e2$՚X6c(#Frt ȱlzTf?vӡ"r(r.&r>~GJGSJ8'f𸔂ebⓍAvn_kb}mboa?ݺQo-q%v}C.VBWl`uޯ !B_<Ҥ^3j&ll BrZnK%A^vݎ6woe *&O׫g&OɳּЛN& yF-i7Pof[S\X-e$YJwVjR&&&&K\| M354SLM35494%d$Z 0nTxL$)_m$TG$Ǐw=M7bZx N kZ1r60EVn6蒁y83?XdY+RTN VklEy}[ydžAL$Зq;/vܨ7*ƍqbܨ7*yLuEsA&bvഠ _=ND_!^ UoP-fi0{,j#K=H0*d=&DHY,G=cD,~ͩ7U.sgZQf%V%|)f}p>oL<qfPY쒔*Akz,RonBL endstream endobj 1928 0 obj << /Length 1504 /Filter /FlateDecode >> stream xڽXIs6Wp|:&O/c餓4Jdv(R 7r$;A{ l,l]M}n(\Zm-1̳|#N]k[_x[T^TT"~[fyY |9dۗ>=4t(`fc}0({Q-{UaGF`50 QEVNa-lGQVE.]ZY`J2 + nCUHغx{w(RdG޷^_C`M37?G,F$$C6;&9` h2z%P0xIO]nGIZS`Qc{Ǣm3d{!i r9BPȽ\T3@0%&N3U`ɋ:Qlst t~T!0yBD,}<7×D=c7Q;_4NAJ|L*QD1◊T}G #gq0JXcq Kmr8J9~eG$VZJ?z^A0oS55s&* K YLJŧ?B.IyJPt6fnV&Di ;[7l D4 5pLnZNnz^4tC.#pS؜w3D`SfNgˬQ:4SxcUe>@5mH0]"y{QzAWVwjF =:Ef঱#Nq{7%}&fGȖfK4 TwdeqbãU(r0E0J!@ugUhGYr_*#iz:_hzfKz0}.8==WC][Q܁: ̮>s|̌ߐJ3(F#FuuI tQ)~:]S9P%pcAuOSn6Դz_vW^ɱK=D/(daMo.@ZVR{.b^f. -(<f%@m*,8(2a搷BAKQ]$Am͟.OQfd5xQ؂OSD# C% u1V2iGOpz$^С t#d"˼iO*E^(H=P/"mX> _JSJy<J9$`h#%VIN?`{ endstream endobj 1978 0 obj << /Length 2703 /Filter /FlateDecode >> stream xZ[o~ϯ0J,s!"I7i-}E$64%93I)]1ܗ08ۙ9\j{^﴾JY#}uaȄW@&w2bJ Yo}i:/BGH.ec'ݙ2RaκZ͂', >/xd% Ǝ ɥYȅUAk+zQqx!݋:kw|vn0uSg-e.X&zC3~ 0벎ZݡV( 2k3%,UIi`nٽi;ӲaYDnH{@YŴ ^.RJKnMjdv<+ˢH"?\5(Aj^ 2e sй7E5T!΍5@ p$#tJuՒ*-od@KuT-qz8XKPc1~-y8t*eqGbw vW%-i2ߠAQ^٩JӶ~{j[S6|Jƴ}ٹޢgF t^HWKw ⃦3 ,{4 L )~^4G慝n3=vㅰ1}kbL,;6wݘ1n479`uU9T:a /vgyV{"At49~)\/1ELɐ`me ֫b?gUnys؎"ȯ'TkC5uݱuT!Y"l/Kϭ9"dR TMMMqr9j5տA\qk 맇+ⴿpM[NٖL'3$>QIG" VRޖYcCKkiv p ?1pi< 裩j9T@Oq7!\0M(s5?ߗYnvu&n)TH0Ą)cƖ= *6*]ѳuo,&Kl= 8hazY7΍#5U -_^dV Mn{h57M@ֹ־nbU*+؉`;kӥW#f(j`4Y^Mij3SJN Ȇҍt> DNM7k!Nà}m hΡt!( TӲ̂g;Gp8kvrvgB lichU8"bu#o1$4INϱNCSZLT*+Q5:"5Rz% Ȑ^ 7!$蠪lw?`J o5CeseF77΂̻AyJ#vNt!af 3!Ȼ&k(r<˽%z$ƨf<$%)vRIU2$UC-sUM5%miAPb"p$QIYդ fi"0B$eQaJcVCzd Vl^}Ct`,. :Mpl[׎17@CEQMYب+fݙWDQ(j`yjm693<2U{v2*ڃ}9HfVRV\U|%P9br#\<:;"=.izmڋꔮ&;W@aoR+h$0CtY׷4FG>7@Z^E3BXW#Ċ?%f֟V@ADc$S4Ti_*@XϤ`RӲsA<}2 +?Tir짞?vHiʰz\iFy=Ҍ⑤S)dOvW"'Fr9:,0~dT ko(\C4_eW?BU%,k?mē~XOI_*DS|37&hgE^(nv/ endstream endobj 1904 0 obj << /Type /ObjStm /N 100 /First 999 /Length 2446 /Filter /FlateDecode >> stream x[o/<ܮg Tx'e&9۝ìx ֍wpXf a,?-1g 1A$?nvOWa{~=BkTF8hVMs^ hyC6g" z- Q'X0">qp84gpqf<,: THΆI$~,q4`ѣ:ai~g_cbc+,ᝊK8jϳ5<{b板>oPϐJNzgol1aЗ/NF{͈bWgGfkޘri4bSak @.$332mv .&AǩHTD 7s,d4o0%7[n.z[>ܛ'o)1jJ˩b3vGΦT(b`Ѿ=/Ϸ0bq?qGĆq}AC>>H}}-n9v˱[2u˴f)P@q|m2׈ED<Q0!"G.mvRh{p,N**9f,I-RU;alQyԞ%_k{c$?RC!NPI) (jUI6hKf퇏Wseg h"@>\mrx;log<ۨ5J#= XzZ/گ/遒}$^>j) a*N'YN{ pp2Jq,&!%IP;.O!u xu a< J1## ǣ ΂ܡt 0e%K.%? %Uu N{񈭨o6{շ00M8Z9ciJep pZG?@ endstream endobj 2027 0 obj << /Length 1273 /Filter /FlateDecode >> stream xX[s6~Wxr^ɖoL_rNNyPlcl"\}WMlIL(L',[ɸu4pmGc: #:`d[1i$<Ȣ41sq*z7Zt]UsZĦ˚рRav."u M:]] o 6]]DSM?9KzS>Ms@M*kkJ=KܘĹ0,`B`۾V#䲍#Ws.ӱ~E?ח_ o mC xFm,b92i̙rg=d"0,}6Ȃ!6ňb֏GP,3S~F.`\i\!Pbئ7iXtHIȚtkڸbBwx{*(3[:e Yn*/pj]!~D6g~o:-xl;x1ba% ',L?N$KLOD!6VԊH;|N4 =9@2 ?mJLg_j,('\lה%l§<)$Tf%ȢF(ѵKt^aPHid/Yo-Ů0yp=QBTи*wj #9J{ dKRQD"Ywt^h]Jcn%$P{6n9y|<{YS5<9U~"[3=.ow?5Ϫ||,D>*"W5&<4I5bdB]x6#fjvek4H6^ ǧ>|ބSYCm$5+6 Y@ 26~5#u;ny?`5r6߷L*y Ft:&G8Uz;mr~C—MQx[,L禄Q "ruKKr+#t#wz=N!ppn#|`tt ٧(״;yݬp[ٷ0qQ (Lm[{_Wయ ?:F$.2)oLEG,oUêW)Ek? ~qAwՋ@ _~H3= GLe6^% J`wp.n~pW=]J/jBE endstream endobj 2061 0 obj << /Length 1523 /Filter /FlateDecode >> stream xڵX[o6~XRwCҤE]{芁[,i~ɢ,N/rx9< vv.WoPw(c'1Yg7/$шPG\^܏܇9\>vB3lD^-f Cv|e/)`[Q+viU&$Q'lPuS,>%ؚY,@l=?ä}q!?}}:4DhGF&r^]Ԗ;CG2>&ns7O[1~PoΜϊ0cM foYզ`zkJ;&^<+CnxeiX;i⁇M@$4qn%GV EF¢Jlacr?7hGxHNkWXBo"$c!6lS==2aQbA .n^$fd}WkbWr@ MH,ŔA{P~- Gզ,YǧI"D2oYg/1)f($2@)h1y%oG&(H%q=oM-P =+t7?s@F%+b`f[j-9EtwZQ5Պcf(akZ{ 5_/HMI?`6F.j.Vc2#5I'/Mm  gd6X!8xN|*X g!dqU4=^4o)/ C+Ud]dHR^}kv} s"8 H] endstream endobj 2076 0 obj << /Length 1603 /Filter /FlateDecode >> stream xn6_!/2DR%M"E7`hHtMG hB? M}--.ym$py2#G$SUzuQ.RF";se.Z}g(b?b3 Ylʟc#aBI}cavi)nTE>$B6N~q *g#)$ӧ00g.J9VnW!A?5*gR:q5jm !LCU>O !"hp>)vSޛoI09MPC[d"h?ɖO_|'u&΍9tX:fݥs>~C7N>u:NA_5&6 f4&:43DcO$TD#=%āUԝ a,Rc03 h}+%el: c%RXׅjDRL@B_k+q1i,4\[tͅ2%E+sUUJ*Hȣέ(6> HQowQK4lh[D k[5Ktodzύo`#uBX,SkwXvW l ժ,1;g#&$Q #h^Rͧdib";1jL H@(y&4t9 dOZ{r "׼^rڰiJ*N_6:a%!Prd#+MAU&& l^cGl3ĻC|?&P}yCnc>n_Yr :8|B[ڄS)ֻJKX[GLH vH) `E;"r(1>QTXŔcx 6:ީEUF#Jsv\&PUA!o #DO?Y}T-ifuXvQVyZyD4$poB3D*p¢dgL2wd8T z\ vl=z5pЗYYtoKn0 i >'췄 z`R-x9L4j|`fp\zN/ 0tZ64 1aQuVP\]u03m,*+Tpla`U'Ba_h0Җw׌u)_+S>p2EҤpt?zPulxJbQ{ 7Ŏ Eeء'D񨆾|ogJM T=qȈ5j cR48,lccXt w endstream endobj 1991 0 obj << /Type /ObjStm /N 100 /First 998 /Length 2470 /Filter /FlateDecode >> stream xZ]o[7} Erf袩 76{WTMbћdC] pxfx}b%F9LȢB6 HdəX d֟R0%'x}fHjh$f>msTH%|$2 C?20SmG#@Hfq&xT*\ ȄTVRƶbȍϢ}dN xEi=,;g(>0,*RîpI&\İk4O %éT=L{[`]PW!*#\3nbE壉.yᓉ_$r1Qb XU&VBԹ@&TgM 0JLH(.0FX0{Fp$ AL,ƙؕ,B/l~$&c%14jTlrdmYȩ"ZeaxkUwVt,ΟOHcĨ3t8J]Ƚӕ_ˌ_+`x2̥DP T!NrT :fNPzX:^M|:yd.mbj}=9D|_Nf<KT!Y]2/F!=43ntefg/zp^vv7ߜmh EY#AHoB! ჷIQly %b9%l8fȃ8NorlcIyS؆0e.XOlTߝMv 44Pp0oq[gurD o `=†%HLX!y㡐hГay=ca89Ôk ul#(% yIet6Œ0ӎѩzp>mɌʽ1^`I9a좌Pܩ-*ӦB!0DWmus nlu@/8c/J/01{^]=f̞o[dvvlS߬nWfdٟꍩEXeQGl.kQ.H~o_ª'p + n4!6!5!7YͲo}e,f7˾YͲoC,f9Oy,,6#@d7|2^=#,aa+{u3l&9[2]Jt;[/~F"@1*z^ 9"H'kYHi*X0zɻ8b#-&Pbx_ItfЭ#{à 8Ss`P ^0ta)j΄j@=$1MC:oRlB8bs5F)#.YpupRʻViz,6y';8u考7Wb~G9p3hEa S:],_&DPvA8 _wmLet߃_p;]l.˛Sixtivh4))wǑlwƃzz9.ND+`JHkJ V Φȝpjz0E|x[/zJ^&HzWw𬐽%@,7o6aey="@שyh(M#Zبn; P>@Nk!\9wzI{kzOŒ޴yzR;ecm-z @e$W֋s*rXyB|/4+Wכrʇ菡̅m̽8aB6!dϝA:~EO},3I|J|J|J|J|ʭ|ʭ|ʭ|ʭ|2˔uT,u U#FHk+=F rN1q]$t@( E81(EFv.B6Od-}P.%pJ odGN3 %p{a)o {`4<;X.oV7ǎko6}7",G͜+ ј)Z/PhHHH@2} "ީxʱ5I#vxݧ~eAQcbuj_\[BʽR>>Ͻ?Ec3KCΗ97Ǎqcx4'Icx4';J,Ͳ4˱='JJ4|󞇤!,V_Gv('Ҁ1Bw]SvT"ʍXI) I ǯCzCdmVەT!v}k{LNuJėFDHt endstream endobj 2116 0 obj << /Length 1235 /Filter /FlateDecode >> stream xX[o8~W'˴Ѯ)h_}0ĔlC8I=f2[Ujwރ٨2 =xHCo4g71 |b˧AS(yL[YTiyTޣAwٟ(vxGoE5M杻{Ń&yKu1BЀPNajͯX/8@nqXxp."/X4B J!f$ز aHwNbEY5F^pR~4K p? O*+#-(nl0,gU"(E)-Z쑠]xjzq1\fnqE?oh@A`)})JI7˳1T>\N+б5>J(TbZr&!zi򸚘U\̞ 0mPݥTҖTۧrRZ'mR Sԍ+LSkDz2+2,'3 PzimhP%gkf`$uQԅy^֞NlQ{rDbA8,ܞY^␃tʼnv)+beM&ؠ4URI4] I.jbR6\|vv`:<`OOkT|ՊYӥ9,SIHsMusa_JP(Gf纭T[xTɤi!u O"?dn;t(ԃWo6A:mi=~re EH_rODN`qNAp6_Unө}vw8w`JvG8u{O^]Jd.:h X{HxSp7D_KE5nCG"193{?~>Ƿ!5CC^Rr2mÑw endstream endobj 2187 0 obj << /Length 1447 /Filter /FlateDecode >> stream xZ[s8~m홢J肴/;sYw4vw}FI`H';N" 8߹HGظ3q;_PH K[`(-02v96R7 dK iJޏ!6ȚEҘ/z_aÅ x񔽺07&+zUE  F  .{_>fL~rO|ξy@x d([")T3)6C A*g\{H0 f8" (DyaJ;ț8)ursę9JI-if xnTLٱ$b6;wzr=!Wb1#`a4 B]|oxa0'J'*{ZD ^w(\I#3Uu~6ΉT({HT,7xq@xaN( `kn(Ej R\p6O^]B&1Lz\WC#0 x+Pu.ia@.آl1V6]xnU89Gs߉:c^*sg#'(|0iPW-DoAjG>:@ж Fŭ"-8` I:p˯;8 ۪+F;'$jEFSl@nlK&dEd5_gxNj☮4|xЁ;uf~蚋^FQԂP: *ZJx38GP_%DwR? LMh/w[zL1 dHQFi2K Oȷps} Ney&zλZ‡v Wm W޷buR/!OULkw;%Si>e`@o#C$h/X)'{ۺICi,Q3 ϼMq@;m9x|"hYvބtDt}"$Rv)Ao§Q /F9x|L!v\UHy 2!*`Q̯*U*NZK-05A$?nZ O{'~KA:`fM] 2q b&uxk endstream endobj 2083 0 obj << /Type /ObjStm /N 100 /First 1004 /Length 2609 /Filter /FlateDecode >> stream x[]oSI}ϯݗvwUF0 &"Lrld;3̿Sm|YH(8]U/("5(NbVQrq%D5͵*V.R3X䢰Bv10BS୘Js2FRF:ŭaJbcpLRY~D98(J C s4rW"qKM$4PB}+U$9ZsZЭI>E.) XqTK\_+$~Ky7]ZQg1L}]1G$SR.> "A ,WrGԵ1Vx6XY+CK ORWD{]*Ԕ>^X=FpJ]OWČZUxJ۽W\Mu`&H~}S-vMDc-xADBʀk5C:  Go# j }輈57& [@9fE+&MU8&N,{cu{t"n=L(Ib,\}K?> np\mf/nl_fVa* ׳gOgblv1\n+WG H߰2a݃n~X\cKz۰3H)^{"q"? ۧ˷eḴ4$g<\ 󫟖LH42W1d>^\MDŽR!oTT6q*jbL8Ies|=i`8$ԂZhZHq[板o&tvgdD525j}f\O*24 Z]< - _w{ZI Zz{ZHIM_+8OQ{8 Ъ]?/C-o_r0 nRS9: IFghpǍz76q1F?Y-ݵO0]?DuU "&/Xxf?qǭ{}7Bfaݨy f}9lv곿j1z&**8Q6=`~PZP7Ռ7Z0#Afb!7Cn 7d!f$3Ōj!GC 9_OY|6d|(>Mg(>F͊xj.>̊fQ|~zo@H^S;g毬=_a/y*%,3Zb9L'ڵ8zw4axK H >x=rZ݀w`Zd'ݔ]B>R8dAT]"TTwa9u_~?_,S]fqʞ*by-p)wtv4Hηa||o9Q38ک138}Deq{13?;5 bV=ңvEӒfIU&DY'Qxp&iGyFȁNQGr #Zj6_飙 PRq> {.>VێUVOz8wgէWO2:mǥS{h&L$26v4MXƮ N];;-O5#xk~MQw-8VY+G#k屵Zyl<&!22222r2dɐ!'CN 9r2dِ!gCΆ 9r6lِ!C.\ r1bŐ!C.\ÔWKcK}tZU-͗1N*Y r#ޮ6>s֩S[:&&/n+#C'}XQVj^nii|d|wFX|e {SIFPy,BZ({~T J(ig}qOAQ!I>gmUU/ګBc 蛶g RzÇayrzEI+җљl2]#pQs]0/aDžjDL:L)q"zW>*}Nq&Kò>5'cv-v3G8 foW8g!$f)>v8piL\@ R:0H>u&? S>hz@E>LݾVi|rz?gri!9ކ6ROeb:#9rKP7'K{2G[%tt'#7Je@cT>Ť'rJSQ ۧ) Τ$.8.'R c0C귻?z endstream endobj 2261 0 obj << /Length 2087 /Filter /FlateDecode >> stream xZ[s~ϯp]4K&TMM1'Z0K qT*ZO- !x^ɴ,Zݻ755FW߭:!ޗġgTeoKe>y\ 6ŻguOo!Mp88q$:,XIO|[A2%*KSP%=d[xH$87wX'̋cB k 0q\Jjv23ϕ,YT C63*P\M ]cQ4XEm%D.uΔ106<8yJ08JE\؎ )0IkcN&yuI "jj= C<٧ZbV'OI zXoA-A/B`k3e̓(VBmq\HfnWF0j_ QAhpd;mLЀ li Xs>6]d}^|[0bIOK\UCBЖ7)Icx$Al o.hΒ>Kc/~S @4`q2VK A_)d>8h_u)O?bø:"]Cl1NdF w |w}#}=r \EX&Qqa #.R8WfNo묔Lxʅ*Qs?l'!^_ -%z{{ +ԇ}ea)|\_/EAqhx_*!wm)k:Q54D^c1Nq(|ϒ*홌Nݨ;>GD ?ﲧlE\wG@!_UzLdm(Xty?|K@g_ ar9؆/[(QƓTR Ilt> stream xśێ7)x{C*#퉓==gڎve+iv@P2kXUdWjI`od|@C 9!⤭dwVf uGO" e.Jߩh}QϞ.w*#A4 Hzٙ@ ň&:{B:@!>D&DC(@UXj`Bڟ*B*'ʘX' 3˹FS Q0>#da gD;g$s)xwĺޱ-1Q=%&YV{ '2IM,` \&e)]s*&RMP[# 0Y KR1|0lX <~McdJr:>RMb` :H|VmX%>4JESZvImTU 0ؾ\" ?cFǩ=Oua81C1~[t'`}|l 6zj)]ﷇ8wn7v-CT61P߭ݫu7`i</؈l0HVrp_pC'W~}wv''"t~YOV 1$aC=~[34~fd$ G]\mm,kfg!.ptYwyBm vs=8@RMP>O&` GD4g;un(v SNn `Anfgy~\n?|\wOSbEwH#fjz5%HJc$fI^j X['Yx*Yessح6'A{dYsm3Hu*h>n6fA,ҿ쭯xL#D VP'#P.=em#p&?nǻ-%r8f '@hETeSv&#Xp7GS+an<7^_\.͘%қjKBγPm,rٳKw:BCuۨoxt0hxq,^u{}w)z1Tu+Nr/jd# C&$DwHbj2)Vd5o5rk. j 555bkȭє)SSLM25ejԔ)SSM7eߔ}SM7eߔ}SM7ДCSM94ДCSM94ДCSM27enܔ)sSMY4eiҔ)KS,MYo~&sr2Xf[˩ Cbg<`1@]Vt3 zz+FlX}t\m7҈̀TŠ^",ӄ Nܘ|AA[ʏn;m^Uzˋutpԑ"&ʹV3@b+H|E Ak%H5ŧ %k%ڹw_d|-bF k{>Fe5z9DR08zZB^H,8,篾fz/a:6mLaJ%oLV_:Xz Oca鏡9@RJchFaDAPyOĽkT%QE(rh#d۶2d@ Pbrw?mSjD <0WCKj<׎pNDuDshwo`1k>ͧy8B"_3{9XX7Ʈ[NJZ`g =0sy9D~`a5i2CϡX`.LÔd+{zaEPSq7-- LmQ <&h3gP55J oq(SxQ-ebԿ=4G^6gWD٪[MbR8Ϡo3DG`GO{S_ Cj}8̸`&.FƉL˹Jq$NlIctWp&g&* i1,SyiJ^' 9 el4CUY:P9dFԪ:GXY0:TuqUg:CZӴ/3jNŒyUg:PVc Ug9q83Vuh PՉ5iUg9l$s ʌU=P9gΪi4gUg3Tu噷SRġ&!O%-2e+{uiCM֊03UvꚈx4&cy&/ıF33R>_ߩi~ʧK;q§V.=e$A 4wV؃ endstream endobj 2306 0 obj << /Length 1650 /Filter /FlateDecode >> stream xڝXKo8W ,z,t)(xlѶR;CRe+]3߼>FgWב < fˀQJ (D ̲8:EVO޿ý=2pV EF_v61b0۝aL7d>$& Ep;ԝwߚ P 0*MIo3'IZcpdfQ]atSLD4֛I煶&$, B%c]/L~Uٳwgwχ,(dnglMml<puOjNMhqMESRcl)*)8QwuC88REUY^N:#Ů̄jeS?Sy7&s[B6Z(80~~7 X߼ Ta1cA{РPUa6#-O$n+9]3"rta@ߝl}8Os@b#7DH̵9DBad* >oS^p$ICcCfY7&/Wn7k7E7G8R>ds0]wb㨄DQłJ+B&E>éRvJd8Z_̺nsQmV>mQNe&p(rVʓ\|,ݢ0t|B7O8Z(`f'P&.~8I lj?V|C cH$/hŧ-qBa-?ȭ$"z?b[CG4z "eW;LD19D$K7*ݬƍt ĤFT9?6/ݲx{ oE׵ɴwS)$=0Se%FC}4yɑ~D\B ,]iעVzQo4TFXG;rHh  .9DDQ?0yRқ*< n5U4* LU4OmTQyc,l kCLC2"r"My|o/p{=ZNN2̨I-<XY/.9cuǗLIA&,qv '5 7c0c7_`N3nBqŁ.W9E vCqpk`1nW:}ծ(=SNz W߼Pbzr$I>JhL\7U9~Q'I{Ȼ>-[ݽO&U$4OAw3 {d4- HvN~9||GUݔTHgxB; |/E&ef(u{a~Znpv> stream xYo8_ad `!mE+ŁXwI!)YrNA  㘎nFt/`8h1J/QP"}>G_=ˇP(})I$|ch泏iUW'u'  &ZKgU1|?J2~4iȚU~/϶o?w[ ҍ^:%WQu6M, ge h{]`ҍu&ՙSMs$TU=X@ "ikϧj8xٷ ?/ x&`w H,eqV~%C?Uxj59\I/ :G@=_ŝNmÙ%$C~M&moK#SD#@EGxqViT.T{KpTJJ_'aQA3l5=oVٛV}8Aʃ vU'޸0 NKɇ/ͻW`ݗbz턙cd]SC@猏׿h/)htkHW#F6>s2æF" я"a< rD6zvorM60XURv/JMW ~ rnRY5]3QI*@wLʢYԑK'c gS-5Վ%@`޴R-&wK{idܜA^*S{j_ƜzMm'yQ[evUJJ7=!W=:uZu4I; @Cڕի2U0@wpc=U.NP"V5X lǡ9-0y;{W`sz^G4$b$=շ} ;'XV^N'=I3y%]GU[lrG=c.[G(,іQ^)qR_J dp2#LM5+#Ƕ%bn.B yH#umc Dwuh 946 4S6aXp,ҘISOs/oܷˢU/$QR{戬Ar8MJ}G;udJ4U1JËc^)q宭R/;;}Ǐ-!du=/14* ?`.?Ve =#eGa6?">\:2l3-!Oiya?S#\ Qp)~K(ε7ec)=Wz:'? } cm]n·!YwuFPX\ʺM!L~@h2qL8Tt 6x>\d9 { K,F5܇4 {i!i$;c՚ &J:DG'I/wK_LeBBXvnMX/q-k|e"[&»Ɋb9,i]umB@GP% )|nR,{/'] endstream endobj 2364 0 obj << /Length 2206 /Filter /FlateDecode >> stream xZKs8Wr" \gbTleڢH8D*$~%Qh-ﯻɷ | 2QYަzݎI^l{>MN̼m1e± V'j]A0I jgY@E-sjuSDiYn8ZTzZU<ўx7 5DGQUjyy6&٨8R7𝧈2`QAB1ͦP9'e8_mנ$z ]Se$D_j 'z\AWOz*.0 K c "{kGP8[ uws Li^F[fA#1k&n ]UrnOU[/WWaȈF@Ⲏ|_%dD+"`"X4#fu`^oZ3湮w0t@W=2qoG(򭥋a,3&w6-TBj=V?Nc @mfnQ"8\]bTYJGPj~e\"e7"ڍXʚ!&D@B_QEX|ۮCm!\ 3Lv[*>ԅW]n>'%[葐Ɏ{ۭЖpa+i+i`~o`чVMz]ơK)ZJqT 1l4y\pqha#u#"!hm/g O! Ѷnn;sH`P;5~?fC3ƲČ̭-pu}{ܥ< nn4 ?lhq@pUg)mll_;dI|x[Xo*SE#R'ؕuJoљN.V~F:G|[8l $9r)3hFp u'o+CI/w'NKۨ |*VKWPn<J ׋:fo6@=Q _fX{W?PU+8|Mzl }OVQ)[=B] RX^jcϗ_뮽|Dnļw6?$T;A hJAOz_TVk:7P'<2pSA~@@Fjݽ]l֍҅$e@c\^%~{y~7'f&&`Ep=kVoASScf~?01u} x?=55o7kMw3|@) x)rtU{k/s}n`g Ff͗.OM' > stream xZ]S9}ϯ_ 陖X t;x;!a,Jp/Pݴ]>|\}c2Al|"Á $ob_R0&$B4dLj.RT ܤj7 YTe2) %nR0s ULT#aOXJx N$RCEٲ| Y$< dmEfx59ykp>N aej/ mǛ UR{LȱId&TdnaYfNkd891oɆsۃӗᕝ)ɫV21;ܤ`b,[A֨Ē3֨$G$J~g^j˺S,b+G&eE&~ &;b?ƶ'1'~9 Ul%sfȥ:%54CI5#8<68aE l޽0e/Re> H5 L|Fa2=.X@d@io3 3ate'//vᢛϻbWwr8M`‰,{i|u^o84Db{ZP-E W_Ch,T8;!8<\~]<'P*uLp&5`\^/?9ۍf7:%}GG~FcOWm˩8v*`Y$DjP1}^]^t>>95ӧۭy>Lbn݈[M2_vn^_v]Xj_ޚٱb mxya7e[X-T  A16 $3FmE^LO̳ҞgWr1l;'l 1(4a+Flafm(OWl\zϐmQ6e|O: [ɹBRS1ZM.<҇-$l <+ԐƄHd[d>Et GWO/-?zuI%{{'+9[ @s4(,b|t42fst hD[?@w a8%%H_0Nyq*G =I!h+Š! 梚j.檚j檚j,^  {rBT!U(C}Κ T٥Zdk>Z\^-_ 8 K9NP1mwy\Ղ”PbF M`N>8TJo/7t>ʤ3pHuW$R;X!yrݭ$yx@ aP2RJx2R=mλb@0nفl c$W̡K= ~pvwAmpBHm'ql D&cmf@IV} ɉ)$$BP-e`%bJ?׫߆PY1{0 CF~CGgb5$BI(kGD\RLVQL?/_o }̃KPnMnr~ֺo'x򟡝ǥ݄cF&e},F:J8g6m:xC!7l+Cbp)~EzJtwG~ttr-=Gs F- z쬴@z*]:\kϾNeu_zY-ߖ.c Aow zv7nݠY5jf̪U3fVͬY5j9樚j9樚j9椚qY+}HAʯW++ZZM!1í!11"'>lHocT/6Lb*j#=ڃbd5 L:ln%q>7ralWBLӖ BBӖ1h#\\g SNmZrZ. F[.w3RE1i8Z.ereĖ̾rh-->Pk0JLz'r\6]zP H]ŢmXFj.wQ4xfKFׁ<اjWb>hD3B:.{8ۭM?8w^ h8P8;/l1PD> stream xYKs:W0]ᙠemNt&]]PbZ Mb{LI !HOlY28E КZ.B+ 1"gM3MgiIFSXGd7˪a+'Ť֪@O{c;^$"xr:vgA6;7FalfUYW95I, 5zbn9^[#cюy"{&- ?[G'XM^uWo<fͲ.Yz7=z>"l.Bk9hGQ|Au E3IIYjn!hm*Ղܬ8 H`|SNvf \{KmS;QM:F ݿcذ'7QOI"=Xfz=b?41%0- AthEeV;2~`?p"a }yd`!fvR3e QTjDlcbO?-,ԫ\l^MP;ۺ+1is@!/A7=)qJN8+ɋ%ϫɤ[dkAL|0cZ0ÿH33*)EIFI90@PRt]!i'|h'ٻ_+Yd@b(;΢NZ@ٗg8:\-d7o 8Y,X+ze{U (d NC;0\_2jbD endstream endobj 2452 0 obj << /Length 2424 /Filter /FlateDecode >> stream xZs6Bpҍ^?(MZ7~hon HB~I3e{d b@F#kIbN0/Ge1 Fa`1uFt8]|J"?-; RϲYj#Ɂ9mTOhɬYoߝx^[hȎXĴQRy{[0`qIghT :1u|kS$UVtw/<.-EUHkq{o$Lo f)vLgf-GuhɊ<jbc('5>zX_>*|xi}s4UA7p@Yо;b=^[gʨԣjh˥4Xud߈jUixRX}$v|]A/D޾DF]q,9 yN׽DMx!@!ϯ-47uw\,(6|{k_V+-4F:ԶAںj:,L# &؊Ͷn\e&o0UڴyQdJPZ 8aOPk+-ΦHNg:c,ʮ%ϚĒ-A4CT/ qQ|E^ *4ŐU-M*/ذmY^W[ ;C^/>:s!lѮ8$/(oScϬ%MD.|l68D q,Dyq|2!K.LҏqNoJJ(u)QDC0]YƯl2 K{5sRMN$0X3=%&L* \T|z0KP0WʀVrʒzUq@ 3Cߊ9='Fsbv؜kt gſ99?z ]Ş۹nl3wTEJRJT&7&}q*9[.˺ZgP,E٤eY4;c oAȟCaL*hcoaT I6ߡ{/"b^L :ohhw &;ӄjUk%ΩC6ujEݚNٹvenɊ5n]ֵ&X.*A}SckV%Jq4,1u1U^#dE=.ujVD`9f(-f`)Ip*\ZR=T+4,nGT7F-Rz-JUczx% i`Ӝh@PGKOWr7VvYgi29LN"PSMU V.r0q8&PWU]0K>ca7 ^NW .B +'T.A/TjRq=ޝvi:N7Az8z<[ˆf-\-搭EnB΋2AC8f.!D!o')"|!oޏY/: A搧C7z> l{Ιk!n>b{P$b;~~~}4_{M oXs3Lp7]^1$T{GgM4\zVUo;D.ivxH$;?꭪ (  ~ ࢂ*O1Wz]@+z݀y0eGN;C`=simAu5KA=TGzjTWs ozFL=EU#V!6 8v0XvÃ!uQi@^h#R+&f[Ng)6f[d%6|HY&I"5%r"L=Vz; ;UعRKc-2__[=h> stream x͛moSeGrOq*Elm~qҭʝ{wJoP;t{ͮ͝!9@3b4ɄRDȆC&{))w'(5@Jn24DO3o;ڳ+C#&zȄA$l"Ain9P}{rIՐ "j7Y-`p}2$#+guGK%H.j2 +pr:ù[RLt$3VKP>j4S{6fDl֤͕֮3@N"y `:>%KI+D1,ebMjdG"I$~ѬJ<%ڳɎ I7c9729:`L.ɵlwM_1%P뵚֚->bKngkǦ:YD ,RjR65z3SSlR55Wy@Glz$`w\pEF]n'EUHp{ܦ[Fvx̲|pDE,\d+z W'ONoؙz?Y\WW,mn@pZ.⬻ܛw3Z-,fO͓'fqnlnه]]uut櫯Nm(i1D?n~ӄ848Ll chλMy: 3عǀLPy"9r~~xԒEO }w+\}ZOH `Wml&~f>WFؙ3oǡk Y;f}s}8[딃u8G85'o q7Y7d\&s7/7}[r-³igEnOm&..%}y0/^޼klN-Nn,ϋM67nwܭ6L3Xf ΪRa^[(}oޠ`5gHV!T*j/j.梚j.梚j檚j檚j­G[RĖZ/;޻_<;jg{y&u<O8̈́(8J  wC:T#XVPϟX8:IӃVSHъW:- ݚ_^u׫ݔwvi Ho/ -n\1HH7Idg%18L7s%8R "Emc L~er ˉ1DC4_.Si4yf\h.rJ2͗˔[3H%eJ\2C͙TeC3uMNji]_SWMR5`Xz qd>Hn\( y\kQk"BQz&+{RwwNש[ߒq쓤R7BQAsAsAs! * QTsPA5j<3fRͤI5j&̪U3fVͬY5jf̪_;m[V0MB!r. ڄ A^@Vӽ$o^My١_0#|AN'J7WPَ+/~ҠlE+H=X>9_jM`^\m'Z F 9e|/Bg\B28j{(T(*\P-T3OzPA!ษUP-T3SBPqiB(3*PqfBhb | K|?jBhb< EB( ʢ,3*PqhBhb < PdחH B8 q8*G"inZK2& eP`8%fQrxyT /i endstream endobj 2482 0 obj << /Length 2084 /Filter /FlateDecode >> stream xڽY[s۶~ׯ/R'BH vOXJf@$$Hgo2+[N ^vƲwɛk߷8>rloMKelO}{y˛V&a@A^>y%oJ"U'9͵Y!l=qT@I_EL M87̪d7 ٜv+CjPp'D9?6)qVdIi.e*羐_pyJ%e}mGkLk̛\-'_&k[N9h7l[1|ňC^>86i|^I|F,"e^FްT~ XwY44'ѣTfj[vnLB5H}] N4Nn_pd,X<qĹH"3tV&Dg4Z6d XwJ*x#[t:k-$(ZО۳wvsoe:)bTjgàcw7lUC8omO6QvH0&xKR܀Ocv ds nv72$y.=&kQ K(\c6%q:|V: -ՂTr[dq3ԗ8Ale8v7m@Tm螾OsF'ޘ-bˡLm+IkC,_Aq-~HqGIt>{f?#DRʆFLՒE26eQmH-8ߨBTYUtQقwN5J1Fqrl!ۮ 4l:j4HnMvظWF9FAc~}hy4lpì'$NE4PiȣY#A.z SQ)K/Wz <5q H6`U8(X<*̂'2qY%N(kEF WD=lשr6յ%dU>ӧ :}iM2.Pߖ; h+F@)an먼Qp|䂤Ԍzʳ,69+:Ɉ2TՎVXy*DVZ熝 Kՙ˘,> u<2 kX A}@UHfO l w6F?q_??_]u7 |* hvT"Wtӥ{! JZ~gVMo1IT u.Z~8~)8"}I߾N.;e*Ea|!/e7:?l>w9nF`Wײg()/#vƙoyA=Xv!<3/*>~|?2Sy/>^? 1o;)Yz87uou8qjta' endstream endobj 2499 0 obj << /Length 1562 /Filter /FlateDecode >> stream xڭXYs6~ׯf,IN:>DAAǿ.HZ,oOжlћeX KB7fK˱m6 <ך-禬u-b56evâ4*AMwl O{<4}+á.tEx)"Fj!^-5yVK.2+ lŗBϖԓFȉc$H4oį=\s!km #%=> ekOz6;3Y^O&' ${N wBtϴ*dKuXD=8'EZLCV9/ޙ{",JH y}!qv֗닗wzr+ҺQeL Ϫx$#w~GAtāw6d,՚6l[.~Lp/b>DtQvMQ3Ϙa6c#5/j/)͎zIY6(*[*?Em.fږ6?XEV}f[ 01/;%|)Gpuu0 }򃐅vtt:@N,Sթ 0 I4}(vN8D}lP{ޔٶbT֠G>c %mD.[q% 5W\9gFMd5WA+p+zt;JC2tMcbs݆;mDCԸEk/i8{(=Ef T'HI _A:+zO<+!tk~pzGXmı]8禜ӁHDFgN##fAS2'lkd wӌhhSL]yaߑ\M~rIlxn!Ic 6D MǦ_t.|5GUg]>>Zzz 0a4CO9Miz74oBԳ[oٳhnU_'Oיu?)b.`ʀ'`6ǽޗ6cQMI0ڑ=R}Qhq'<+1BVfy(AAz06L%ݹGqrWq@{*"GPlY%:(%\{ތ/a endstream endobj 2528 0 obj << /Length 2076 /Filter /FlateDecode >> stream xڽ]s6ݿB{(ձP$AqZw")wNQ+E*]HV%7$XP~aw9$fu]|r[ٯ?g@F,)a:bI?q-`>8'G,ot-DTiwηtD#ꇆ^GN)M˅! u)B["49s{djԢseosDb6yqB ~G€0kY>yF[ˢ.i5ϲZJ*b뜞u1)*94C'oo/=ݯ6rZt!*mUHQx|GF@9%=ednyIȋ"wy%\ip$T٣ԩļ,*M2i}`]=Ԣ=4?j"5by|^X\$2L^ 5[OoB=J OW"8wH|n0H Y&:a07&di`(ZJ.2mJ@X iת w/̊\g +ϘK6>YdA+"AeU!+y^r ]·̚G~rЃԤYҀjjjWDPƂE^Jbː+(ZVSi3UdAyw~5q;2Mԏ$s<$J'a7Ƒ[y M |ݓ=H!l/2)Jù;_f_<&y_*?BҰ$pNwP{|Γ{r)̵  ^ƻrvdDi{dur,Gxq4xԨ91>)DwV@':ĞY"4f2J̅ytl/@~Pڣ y j3\e#a8e~7b:Һ:W`@.)$տ% ڙHi{H.қ\~9R{~A ~Fv!&<cby NeSw>)yD;(jwexȴ#7%Us+so®HhP?, wC;Iĝ> stream xY[o6~ϯEubwuq&}iFxH]=md{}Y)"yn]ݯWo_}& W1'V.B[moNSI]KIvZsӷo}ES^fۮ6^,t"fp2&taǮ&EA2U{ɁXF@On?l4L^=TSUmsP{PwEH]R\S5erTqrj,n҃:&8&bXY4od:Wik1[cCA^F@H*`h*/mjhAiv>3!7we(j4j5=F] gq2:W:{}c]tҬRM !Y{҃6%+?l{RYDvF+svHiDN+joR}85|_!6f^`L,>?lx/3qLf|27Ve^s>bt |ZaOCyK i8U zȁyЧ\HKLFG3x2LFh%;m) QP9 8L7)SS%= )tMa}]>?+4g3HImr6`ƬMf.MX %QO&[` jҗ+, X>^tKH%e3g lDUi! PJA33AKjNGڨ{VXe꫊mB!T(fg옳F{н ^̋z y,>81R1R#Ƿ ntL(kOfL0׋%+IJfd sPF85]V^Hl$,15•j$+cGJPEQTИ4vL؃)MOph Oo@.ܓL |JU#k]+]A??B#:j]^ *_HdZW] ˗;,-!Iѳ>;"#LuWՕǥبnxxlŸ~BTP\`xsxc5` fu9zeoى8qPy5ɽb{}_Q.o endstream endobj 2589 0 obj << /Length 1812 /Filter /FlateDecode >> stream xYO8篈xV"^ۉ{`w=!{UH )MIm@ &|1,jyq|ዔV@ɥ5qIJíĺHwx=OltHXKqBЧ&Qy f$욆=)]UGagiԾeP TĮ9#i838' VIa>dn1Si99wq<"UjAh^fIG?(3R,,7T&aބ2iX:rf],282@\k8#c$E/*a?Ũ <\sќte J@wa"Jw8(82@w*(Il&5 XKp^৛%΍lC43I4ܜkO' mr-g8h(j%Wjߕ]ltQCxUHJca1Akffg5I|4 B6u(ptW m 3r#B IOy%\O, Ȟ#H珧#:TT8ZLObto$,ugA͎sbhHXy.2} ".h\z' 6? "|-fQ^+]s OT({ 6kpx+]!ʓHͷj'){&`f}w_?p>_|_>$}y9BNgi|;- xg\}+ޗX%ϰ~F3 wb^ܮUa[jA\~r;a.,^%|}{E಄ZA>N@p`dϋgk, ]\y8p,9.T2{_ ~|qc]aa^wعP@A8®ź\u+{Xե I+nﯻk> stream xZ]o[7YE}ŀ6E&w z'f;P1fIs"1}LQ("y"GL&&LS_HjBB?3 aNޤ,RR0%OxWPl| /Tl *BIUs"} *cKk"`(sdUJԞaXm,VQŐK WC `I T4āf!4$-(JIL])%9-PuMta: c+HMe5踍M!LX&c .Uds0s.o[ew؁4Eh A!(6IV3"#(r ,e$EXWO$= ;LóI%gɤ -&{bAv! 6/ Z,#xs[e7[*2GZ|[$992g,2b,$8+% 2b["Y'%P!#_K{Iʱc޷Y|R5`*r 2GUel-$Ti Y,V9 myF2|Xw^LY6{ŋ9z_d%1ZߍaX{rsrflX?nXM~?d.FℷaI؝~_hu+}ryVncׇf|1S[&v Gn\w+ОMgW?͙< p8m0d!x0rXBٕXn R"*J$%E%SB%gUrVY%gUrV[eC?m Mfhjvnh|pQ9To 0" -\ ^]>1KS¾~uX@l=OȆL&'fS;Mo %mU͖## hqaop8\ Cm') AـkYtL j8&b Ix(Tlm!ul@Gt$"WhCu9pY?ɦݨ_ӁNZaq0&+ 'N[8D=,Gph' WaCv@H' C;Ͱ S`bH$Jp"v(7ˋ 4(83bd@:L6nH!C,IxwGm;@cs>&x\>5|62hEPW&"P^.7f5[9(-d%U!Fu?ܸ#~ R_ٸ;p@}eSqԓ[?3y:4n$n7Rzb}qW,Geqҭ,jU5תkU͵*# %<* c_G)0ͣvAGzr ˣWN_#(S) R7S^RH}A4sݵ#dÍP0!DMؼˍ[1 =$ZPv~Pn[>nUREm!Lj[+ %J*٫dJ*9@:y``3> J]v`WeC|5.T*;( -;ƱײѲC8+;p'ɶ( d[v؍coek$۲C/(+;(-;DzBҲC/H{,;(-;Ƴײ'aĴZv` y(~ѲC0{*;( of'!- ND $Hn/.Nϻ5=Lyx1zF(ߐ1*0wAGwmĺle):.f73G Gwtygt'w zz2K{y7 #ܰ|WNn$3Kv<1]mzi]; ?ɡ(WȢ&GlNѐWDPY6ّ %¡0ƧzS@q?=%!FGRM_^(B@ =#HVCEigcLp9rD@ YL>vC^JlHb D}~I.䵄k zo'[8 S|ە̟ZԗWCɍ?+~_b;;p);k%Zbq:VY}>gq% j j j j j j j j j j j j j j j j j jUrQE%\TrBK SYDd؃Lln9ZLSZ.> endstream endobj 2631 0 obj << /Length 1672 /Filter /FlateDecode >> stream xY[o6~ϯ0yYۀ4M&^AX,y;$dvRj(<\H}ޟ^HB{Ѵ(%|ѤŚoE4jETKk=>~2@\o\";X59($-Zʈ$,)3k23-)ʥSk%t>G%\Xӡ>s-!K!)27yD%2 !)g'fxpa]e3.(ˏ#PJ_O3- ˗!Q#A)m]eHhoR1_ՔyPec?1A@l{07Pc'$..vF@Z q),Py>r-H,7TR0naI.pGB1)Jch}fzlf"36t9E9qPb:{HYէ2aFL:yvXtLe ;9qX 8jӍѪ ǢЭ0ʡq=YL! B u$L/>˳Adu%--D|Ǒ.{4;|:a=밎Zq`MFyb@SK\,rTTG]\h:vAp]3B 5T [18`zn#`rnz_tf,ľZ_t~,-J ;WI8ݿ6s}9 OS:aBI Y !gv6VF<>[*`9~41 L/l Po;λhΩ\.q@CC%QvU MLLpZ a@Ri6n2,ֻue0S"20|< 6AFE^!.mBd&6Pd=dC|uXwݶuΔm'B'2DATjEyѾNs/E,; >ݗ }p7pLl'X,کx#lՑo;  Ndw]|' ,wtRt?<^4?(x.; sn9Ram;O^v1}2+S9wu͹ZywN`y&]-] m/v7~A(HCsG4ˤ{}D ~>`h.)'6[Hg31ss&3Cs_r5R&iò^o)T_|JۻOáyV 6K_ %j&kj，#YW řoMMwl}Z)wn=T! 5 endstream endobj 2650 0 obj << /Length 1871 /Filter /FlateDecode >> stream xڥX[o6~ϯ2Y"u)tm݊6,ю6YJE)YyHYPC>u6;{<{yNLrxK|8aSg9_gA0|2=I"q9Z&[}jٽO,;KVP[\sُ30tﮓ{yТ[y ¹>ԝ717sI<'t9qW^,#n FzH4ѝ݋r?}9jkntL"IS@@ <"Al}#dZwM^Sw&# r^L"mn]R#0rW 9ǯi-Fdeht$rcb0zW73uy# bݭt8`,"s*A}FL¹ШPTfUYrugefHS'UUnڭ(TS<p _G]WZuA]JhUCYb(Il!onqsW %oo^~mH5@t&8Z^7j r؀v`L]Fb6Q2nUvG"HtggZmR u[8&EuE4=NvqZVl% !Y hwW}q/VCh,q<6$|kG*$,C_)o,)34RsGi-Z1'=KJf&㨚nFSNR̷dW%Mʋy44NҺM$G!*L^9tDkHfZXÁ&i6b Y@Orȹ UuR?N B]2-|50=]^|;6O|=Zj m&_ls)U,'vTK!X?]H^3lOtU&TaU1pYQ@=z=@{csg@{?xSK5^Xkm::7C.UbYPOoP`&;8Tmm0\z%U"Ueb- &hҺ.`¢ 5Uv#XuSmjMN$or>*j3(D@Ns٦w y喼*g+og endstream endobj 2596 0 obj << /Type /ObjStm /N 100 /First 1009 /Length 2365 /Filter /FlateDecode >> stream xZn}Wc+`,z#ڒs5@DL:$}N5Yz `QOu8C1E!MH&*B67]*W@"yHԤ`|vh|?%ku)mT Qnw`qC!aIv {dlӒV&EÔHp Q>b8v.Q(pMcB&PW؄8Bj&l n豬@PI6PVs@]W#$Xd`ԌR_\\䚍',9g @&EyyɑI TjlR4x?Ed2q9{ѷkdU(y2ŕ&)$ϛ`‚/hJ'H>ھ[rmw9nuYq* e(#65&SsgIje+ ~%VŻp,B bbA ۶ "ҮʂD ɣćf9 9y yr'Fq H䜸R(tN?!=A,bÂDL'^q0j{2;~m_\.y2{Z/~7;=}ۏp5o8[>χ(VB/:Xn/W P.<$B(&th]P^]G &V8Yș& 0z>(0_ݝe%۳|w{q5ߌZŲm3=0dq ΡcCr.h[*lv6>!JMLZn?j.D zh's2hKQ;nO^|4Ed,gA-LΌXfy}u޹PbHR%ԫ;8f5Gs5G0`L2m3LVhl˪L?d:%?|r8Efs3{=|ښ_:߆byi۬f7Hm~?,.OVLsX%.)Jn} oCrf;f 'lU XBT!U(*fj٫fj٫fj<3fRͤI5Nۑ(>d?aM|cܾ_??$J5Yr:w.݉e2Ó4O݄sJo?@ǫpf$f9HǛAMUy pȢH^J#Th E].ǠML(]gE\ivOJ(]g"E1)rtb.P&]`q4. Ei(.Ѿ ]к&z0E(҅gE(e"E(ҏe"hO4%hvA3 "S8REǹ@QڥdQڥdQڥTQ8iBML$' ;}GŖoX(O:L04P)aKJkyٻ.ںzt etOHj~XjO5%ht"^ǭݣ/))sq,Թ8rb#W})fo~9|{0Wlwن#[Pv7 : : : : : qAPNbEmSm٤78e"'۳xQ8X<,1hx2|ٱx2D{8 ;4陿-p:x!#x_K(]: `QY٬\|P.Њ<Մ7RjT]K!t?M endstream endobj 2697 0 obj << /Length 2090 /Filter /FlateDecode >> stream x]O_Q 7F݇}H*u:q:ϱ4 -41BDZ}?|tr?N;p&w ^0 J|O7' }Yjs>\AgG #8O B\rB-X=~jOysfJwJyy){;ta28E$ SSNf0J,S;?̢yB8 )ԧv$`U %u"6J$byq`^+G?$T 3A(aaL|C' Q]J4I3\36#1IKd6+T̶H]>V arnv0l]]|!5*r:.sP.ᾓ*W)L(!ʗK^lD]JqeRJ:vf(" CV SG%K;PD @e̕0_K}yK;H U̞VD8헾Q}vX*6C4P b*r)YH­9Hb9a^+J0RH]GSO`y*s'(J̓:Ù_zS]"9vAr6N[`W^FyO'%`5{s}:8-G:kc]֚v ?HTUW?% #Z䵞!/ (+-6 "Y)i1{R`7,فy; C>ExF?ǿF 0Nxčӭ!VBx3 >nEܗ(=l ,V:qY)ID9 |Fda@2>6?l}RTy!`JUޡӴH:ogGݭ. L[@#!SUU> ƣ?CS~#:bDz>B۬Cvo:W6\v_>t]"doA㦞0fCKԗX=#m~=#pzF$gYl~]&EM= {7sEǯ6)~_ r1TKW\4n?m {<#x+!>zCJGආTOWF:>CjG =Nq)]3W=QrҸ|LkԨEpbWD왳RVy $ȈOy6/ܛ75cY^ yFFAmL۵ϾxG{8fS^bŌ˻'L+k el.OC'|CuA/]NCI1=W?t_-M\'4¸wut @?4${_B뷶f-g pǰD8$ Pi-#Z<[^QbrGj=[`ndJYUP` QױQ>jbk7++,jE 6;tyK]s@C]OqFܠuwElh$'XS2e|<4#,Lﶰ SrmucҕqxpAb֑!J/$<2iZTc?YnaYK#]p=yc T&?hxXh{$ZQ)s0os)|hGxݭ(l:Łs֢d!jA퉶9t Mw9kYKR,˦pI6FV)́0^fiW5F9 o_ZzPmC:%,{J%4x\n\]墧O4OkȮl }{7{qx7H `ޠ ޾B-r.*T\!|>U|9xgcM38Kk]1%>NAdtИ!>a/Hlv^ea([$ՄmveI.wϣfyJd[RlhAhjU*o,MSdA endstream endobj 2724 0 obj << /Length 2870 /Filter /FlateDecode >> stream xڭZY6~h D 䗅f>ڨ%x뷊U5cTxhos6?>{uwBl276a$68 67#o~]O8XY<_˦W/2?x :jg4ng'6Pbzs. }$UIDҴ(Ldvo V CO3$/a+bwI҂}{,?Z]NSTλJ5gWmv`D'h/Qq洱@!'7B0[մydOjν~H<9Su-uKs-vĭ;inkh̲)T[ɻmo%/qӍz<>lƽ1XB gQ /Ԫߜ ڏ3>]fǧ90YP  PLOs@e|d^H@H&P(` tP޼!*Ďi+a_s@}Ҁ?u5-u&gQ3["ͲAFv+./rw,~^<ʩ_uԿsfANi ߞ)/gADxBomD&Jn [mH,RW4XگgQHe )Q_`ndk-}? }Op@ܾ0&n2:bJ!O`ȳ; ^$[@%PT Gs꒤NQ2WL1ud.JFIm͜Nɒ`?T6@,A._ijJ#k|E"eӪEpdFԼo"tβ /E +9^Br}M@HD#S}h7B:XMEEADĭ obo'ge̥Ĺ$2 ,vniH ޠ-($qf-O`|0JS7% HUA؅Lh&?6%KV⒛Ύ2;S$TuN?#[)$Tae:y^C+g!,nI,[k*|BٸdIuIlp;$i2h`ܲD["FHV 5[۵ϊ-M 8Ьn nK )6$W5g(Ci1!H*]hFXD@"Ȑ\v%"*;݋pE{;)p祐6. I`]9״w` rxeEh<+ھs;m=~f/h? mOy3e~)pE#>]SHrC-K9 &E9>Y NC F&dhf1HJg4X>%$Dmj(zMHdz%Ps /. &=Ģ|ƚcU5kѓL \|j\. a~%ED*ŋRCẠdC%Q2v.vj!^z)Hy  JU/V&@…ǦmEm0OųΰR늗+χU1.kLDfmT[ n "xC$ăM2d"˄ϑs}ղ2.Y؆$dg"մ@Bx9 > stream xZs6_5 3}pҤ̵ׇ(yG*AX"eږOr7]o`zg?y|H"-73sp@̖/[]2GcH(~vn7IC 7y!"ђ,˛*b{i=wnu٘ס>0c卞/86UQTsۼ&2{䦗UC]ZQg,֥ ODp?a0f\RદqW_p]mwi"o/Jȗ`%Jt]WƐ9W?hPPX:kq]:¹Xf~8eB|BȊ1a?A5f  Es> dӧ > aꏷH"uCU ۭS@fOXs0W !۶ߏ&Jy3e%R4N*6_({WZKAj9gD6zMUӲL7i^8jUx |kk͜1F Bf(q~xUu b"jnkzٖZVv{os]xh*7EYU@̆4H@@8 G+x9sXN$[EA#2aF+ޣDRpz2,W%G0pvkagHqvn23\M|Ƚg ))]\#,wp.*3qK̰B/1nWXxuUD;j~@}q!.aꙖS'McO[-9/CYydR*EEH$rI?xZq6͍6=@+AuH[kLC1q'&"_Át ,AvYrʇB=OݐQ4!ڢ8 !<I|]9Uuc(6GT]k}<qB9л̎ |_,p .ł$\6tMz>cD#OUQ=tBM;?@!&\rӀP [iβ 9W6pps䌦]ziMe-ј?6CvBHo  XHUpumW[ (b' %%LCKYH>L%'d[HW3POss ѝnR,{&US&!G-N)H Jq2B*8&_zk!Q1ѮINE;ǜj1}HD=c~Vz q7[d":qe ×ש u p3spX0>B@Uwo w> 1\RyəRxm@iZ`Hz=uRs%!{ GBEsCu>lë)qɽ~ uܗMzG$]ה f8aUq}eC=HDlxj*cՙNЂα)=RM-C/?q? >@P T*=c b};dÆ`Q ǀOX_ 2La'^æB^:zu𽦡tz@5-vZ [ѾA5 , ňK&hٶx (G8uiX0IK{};u<78axgg8Kw|ꪙGpaEa|ͲWڝ;? :(\ 0׎C4!pgwT%&MJ~4oOlQ{˵$}")}.S'b%S|ো> stream xZ[s[~ׯc-ɌoJUqK; MqJ(Z< Yd1PkkBA)$p&k⊓7dyFoVXP0X8@S3L|lq7AA5a`H($ "ċ.FOKr_෢5 K1l9r1_R cYkRAЭ.(`>a~ޭK3ɥnfw10tJt:nY^wMG[RP-Jmx &Yp>_ˍ;Xn-QDrJx%+PI9'圔sVY9g圕sVY9g圕sVY9\sQE9\sQE9\sUU9W\7wM7w/FIl^==~9kh`=$ d c '==l܌YXWovjbz֭'NjYܙ㪅yz 4g84>ɳIZ bfM`7n9 $VTbn&[{=<;D;+BcmA~}7 |xHD,N\y\.~P d2V$lxn⟍ &bQp!TJ֥\a'XK) zcj*3aA0''mw}Ү#2J$h5)NpHJl4t맷{qgE|g7$g SB>XɻzA[61!bz!t= # $l@0|o٢AlP/4Ϧ PTEH/l2d:XaMRob.Am p22 5lH82# Wq'SwɷfU4{}sdYu%3-)q,Ѿ P,|8VC`\+2DAUy [i8fj&瞈!F0>T$:=3sj9qKA!I0+BR!$EC@CG("KJ[_P{r,4-I't dzn܄!zi!2Kڜ1$95-VZrkrV:(?B8CG Ljx=vb ^j q&I}{Рo_Ӈ}m3Y.M]MC:Ar{o5\[-X;zcH|jw?Kνȝ;W!ݘ{{{-J%wry%A RB9{앳W^9{sC1lSTز?$b9* 9UJm+WJQ9Ÿϥm"iٮ;rq 61SІL qIڠFN%|_DUPr32LdnXM!])ՊmqkfjM`pDIY'/ GqaBgBA6")wlv\B%b; aIpއػ !B`BUNDk /iL[ؒԯu.=q J]&רpi^I>P. g7vEYY&dZzM3F IenR8Dvzx~֭![ұlEoH1~pƔ\xMjV$#cu2W 7oAt":HB:]]~դ{-/_Ɉ["E'WG)k|:[_${z[3]8\-b^Io_ž =v_Ak>6]SӦ!-H!rb-X -Ban2n%sTQ9GsTQ94hU =J,nM7R ճUiAG  >6}"ج/ U6HiK)g!v'b^F1qDdN|faK!)3Ny8T 8.\}Sh:wډ'N4ivS@V 8pG9b ØN7Xp=pnf;w&Nr 8T v/i\"m endstream endobj 2809 0 obj << /Length 1531 /Filter /FlateDecode >> stream xr8_d_NP7teMN>#bHN#pg[]]"j, j^L<I1Ϙ Rp=J\btmw;&__,Xb(!s;uj@5- F>| 9o ۩ZW5DDlᄵԥÖ,^H|'<':)u=K!">S[/y)"+y"x98 nn6 ]fRDq>jϠ-muz0'2 [W|vx IN z5O6^|1 ]|.' ph:E%(ѲCjQ!THJ^/Jqz!2Q$39:yHq=:<;! \x=KET`c"ٲYI<ݾ^rT]ϖ߾y}Rpl{7oe;{|5a[Mv|xɳ|uRv>Oe\@ M9,r+**g9kgC˥DeP*..!ΎF8֜֓ b3:<0PϮYT_M46 M!wyjt||6ŏq\~IƗcg?q'Yl+>ToHHjL Eg8FZ]wID7QZU'sA(g2UYw%lLQlFnVp$<ĈX wk/\BmU6yt0؃na7=A뭃t}`W>8vHl7foԈa' j}ʒԸ\+NH!^ۆx$?l!`t8u NBnjp^2S%"zFUב'~y^B1t|KgU>ӷ2jZ[5:b]S өh)aE㳖ŸU~#Hn*y*fNh#926@E(QBk>d RҪq]>d#Ǻ׷ݰ:Jwޡ&ϴq=_񥮣jj%B(M{ Dlal xkHӔe\\$[*;\mL+rLR(HW^ `S1r(]*xhCVFM!ۗCn_r$o!Q>rpӒDzRDq;5lurqW͡ hb: |Bވ5W;t~au$7GMyzP endstream endobj 2832 0 obj << /Length 2512 /Filter /FlateDecode >> stream xڵYKs6W\{Te` eKNloR޸bɹ9pHh9Cn4!)JR6^F W^E’P7 ‹(:7Wuslz%wop479bXL8yۭ`xhe⾷ś s %BY]UǜF!Kb8C Π懷.X {?GXSg]QOWyI[z6J9>@dJ(a?TdfC'۬EH/d< hJۥ;8_)1ۥMu׶kjkKjx &1}sZ޶Z>ͳ vu2M VI\岺{/nؘ&J/;w^0G)7oBp Y횺`ŜVVDœbV(H}NۺZ"Ex+.==0EK/K\;NLM P77Ͻm Moҭ\N }Ϸ]6畳s,8 6@$LͮWfɉJ~@wؙOkvD @ 1JU@OQh`#jQ%s/ 6۾&kۨ25טGm#K+Rd{opf`#]%X$ȿ]'N0C&BA8[K?WXإ+[!'UܡP; ΛEQT?mjm_`S@:]t| DB|$.H~Og5J2?Y LbO3ҿEQ%u,e;zAUt W3`t EH YtmqBGۏk Ad6z$:i(x)@YzX74bN4>+,5ݠ8ժm+)쑄AlXc^nѿ% :'hN T?,Ӈ5sZ}Ϗ℩` *?˜EݯgUb3ha' 0ոݠp@-=4hbj, 罭BiM p[ƶumw>`B[dz)w "χ쯮\uA4N:#pBӼ||$N6W')3M b38}9E&oPҢ)kթ:_^>O4l 4iAEtz۞ ^R<PfIyv5Z ónu UD`)34F:s.mUW%3b"Ȏ=I$Yn"EAi 9"w G⟩];!#>DKbý*(K69 @sKhNǕʕT9 F6bd,evoR)ʘ&Ec;{$~c/e55!8\B=Z!}ָBk_6Ҕ)G$cˊD#Qb(0qleC*T~M rYTcь<}X۸"~x È3k궽P']jќ=X!!4jAgZ/! oq1 § 3\((׏=hU>K)> t {&L{K|W;'53D#[ =ENեfs<102ؖSxd#Sj9ωlKvU2rPMňWQ,g6jV,; endstream endobj 2888 0 obj << /Length 2486 /Filter /FlateDecode >> stream xZs6_3J?@ūDbAhG}M'%bit;G?yw懋0%, E8@( &E_7"RAбkɵ.k]ݟWUy*w/`>nEDz/iE@POx41 csy:I̹UgWN^LW4[{~N"ˑacp׹.hSV-Lʫ~|wyzQ;iMkFh/tZɗs<i9K"S+o.4Kţ @+ԅ](bcȑW>62,jw%W)/J3Ӹ{W9]h7uU!;6rVH% )@@W~b_8$k2Fgիbqђ, }G8$kYVeUz]{s,&WR8؈ Ya}it5TOȳfKP$5h&q#LשeohУc ލlc,[mJdm6q&"[=w A\ 4h%[~8*?N"d<8 2Sq_U`h$h! &ĖL.c1١i䛕n&U54B0 Sz#;4Z -w(c ic*9"d_.\cU%W*F"5IkqKgUwpu|8@ vRiHkbbk0D!xf^n<4:GslDV38XDOwa @E@].iѦХoJ/jڂ'^ $rwF"DMYմd!b֘tlqaԤSM$Ɣ~.XzҺw&f}{M=P$XPI)8\1pPȇorN6{JipL<=PeezhiGJX%ĉv{kUFN*wN!Wb H$@,.y :pݙwu]cs:}Бz oQäO9*>m'}LH+̀}Ҫ/n;[Q4^٨ތ7N`]E OHQKf|Du4\+"C"SPyox[m飾}qzȹcxkîAgؔv].Pj۵w0}D)w̻g0CU J|~هzA6GE|6Wc>>#e<ÎORQHٲT@0'r6 ,?nikM).6bl062x#_2DupɶɫPgE8 8B(LKrD.ju[mʩee΀{t:}_*= GQk ^k Sj(m֝o @=t^M1!`N{7}*iF-Oti7\;u ]C4E \ZOɏ Hn·L;V`/4}m>> s p*34x+)(EDOG ܯ9[m s2<At,9E3pMm^ƐXluPOmW;_(#Ŭ> stream xZ[s[7~cBt&׭g^3o`|{Kxdl` 0-LYvR ) گ@(ua1JLX0 SԾ>r0o1BTpJ+\)I кrXG0vG 6v7Tiڧ + %{D)x/5 =yr4yۻL.rӞ/~9<[fC p&O&/}{8W28o1u1T,Y\2%=5OɅ||4녝]~7l_o=¿$g >姛axXb`c!Ijxȓ=k>@ga:qq=zXM٣A@.4^grY&87V$LWdwl,#Hq'_,B['7hswdirc!}ʘ{qG8DN,ֲͶ;Tg=X'\'7Tҿ8HdBPݸ{qc?ris[vv*;}7؀oCjyu1Cɩo̫N|hrf-|&^ެ6hqͧϖM \- a? H4Q֘%fe;J%+PI%'\U`UUVXU`UUVXw%^DTb+8 EC+j$NI|Ghaޜ·z@+r&0dD}`~'ff[Ec 3C뾹 Ry<АOԉz j9+b1WQO7p6_χՈ3cW$QɄ ȞtW JSψXJ5%$1XFN3ӊ%/>]{Y?Yb{=ʹGup b3 oa[c+m8>}?-XBPLdz|38w&LD0cWVR ŝɳb6~i#F)Hgq|=LW k f ٣:~,͈3Qb1Q/# ° ',onjRΨ%$, j HW[)Oh~>^}w=l٘$x()wy};w^rJzDq9z` sH`Gġoz<| Xw5Iݓu9E,;@eho?Ezp工wyߢKǝWGOunrn5y~H<1|s> stream xڭX[o6~$5G7l2gx(}%V<J;q€%~(q~9ywp#brmؖ\7buej|5ս(:N~og,aM%(2.n=APv. Ϝ[ReXƫ\fq+)3nYծNJ^&@=`mGL%I3zQ|-}?4w]߉|1)nElϫ>"B6yTԱYdM&B$̗ofXEw9lnwHaenJtgx6Ds=7'*] t+|6|ygӥ A4(ę)әkGfL4..}uVC Pw7s=*zer߬s@}֗]]?=+e޼qKz Zke8279͜3r{>\3dbPrL*+6z,8+6ϫ7htNw{Z=@TmKنE$<OdYEOvX\^/<?Ӥ!}#⛍G* DjMU1%w]V}U*i./hǍ[w@r"cFeUҋ?PuRgH'sE+"X4Pv gq 5Oɯ{$5hŧk{&p>m8fGVO!Ա PR CabXbJzߤUoEQm */N */J !*aP|![Q!y$1vZafSbqfwv>av3(N8R&ĖzIpM]VطDbx=rHV R׋9-O O=MeB$/':n1ZpS_2టPv?kzSȳo$TU"x!@W'-zq u>+ kKlkIw̵: nm#.qa"9]ŜPרCK2:aTez6bl&0$U/k W[UBFTc|dbLwί|7[npj[2<٦:SqJW,Nb8ҫ3vf;]RDp7`f`۶*vHa Gm$h5 /_ܽg@=I Z.Ńeeةp3y8rs ޗ.\oD7l,D Z*ךw:D)qX.lrϗc endstream endobj 2943 0 obj << /Length 2672 /Filter /FlateDecode >> stream xYoܸ_0 1O$i(69A.}J\Zi ԗ@[R9oF~o~~Oh4ndmgbq8Y)|?:fMKu71wq֕ ͕q6ۺ*}Ǯlꬪ/{{y%ۖuWLg)C-EcF#a"KA0~4Ї>clqF#a:H'hg<!\888g6nNei̸!.t.EZH[vvK>Vf "d7py,r.`U[M=N*Wm:?\=K%9k2}ھT04%p9 RӰ?ү czhZX&8ҡ9d5X}50="i$""N'>hU ijzS]7ӍI<3HAӎVky)tkrdxCFGݠ\=>veiG]3Fn*"1L}/Ry3)+$ bׅ)} 6뮬C$lG*t?٣SFy=WH¤~.}@3ʪחk9Y9CvpwP#\qEIi#1*3"kiNZZE 4rr?X^L#F[^J9L1Ђ9ܖUY;PEi8Y}\ƶn7 h22mvo,WlU`:.(5Ē zE5 .ZG.hͯ[zؾVtVT"4P%((HjZ]Pʧr23(JbA6K Wb޼Ma WwI @G*\_1 [FSU1JѥbrISs#XӔ-n@5DF)BTf#y+)&<3FkM_qoe!-5!#2-=RH@@-3e1EM_0c*f,G2ӓ!чL#MCbuq`bXK:0cGKIO&"AКϱ+ry~B$Rؙc+ Gy-|y 4n(X)ɐW|?Ts5jpn !&ax%jh$` @Ξ֯t'@!Pe[h]פD_w+'6G./<g ZTO.s;Aszc5~%U5bMs#yֻjƁakeð q܇≽nyp˚'TL;n*Dם~ W+J%G{43 LI—$cp;OD7إum ׿{ lN endstream endobj 2906 0 obj << /Type /ObjStm /N 100 /First 996 /Length 2344 /Filter /FlateDecode >> stream xZ]s}e4R&Nʭ$<k}эȿ猴6$`7SEUOٙӽ%z㌖B!&$R&v,BВS#⛤F4#H&H[)ɮKFJh#Z%"ʩ5JrN1u5QXB\A#Q<ĩp0a]ۢ{!Ub?wh׃_ֻٓvrz6{>nhvLt8ۙgRb+y26$e73vtmf+xqpY|qL95&FzЭws=!lEMv(z_9 J.,7o݄jQ JL*xvmf:8G~@!lY4oޞ wj:8FF z$.c#N4?Lslc pNŔp$kڼZ2L:IЬ҃ɰZLP[&l]X_OTu<*uT\ FWr7HJLZ̎Ipy@AN:B,HŔ٪ u+>z58}2[,z "_t9vg/'tq@~C25 EfeDp$0//W?Ora,Kc  RԊWXԎe_cmt=oׯ^_ a1G%': HSCd^gN- xQeqn(5vj'کU,`H ݧ JTz3B$[ۃmn$m;N+HfìM| *- ݶE-;}TW<') ;a5}0^X'5Ovgfǘ ,mtCGޮ/7gvn2,뷦EXtK|xv-l1{@XuAA(((QG!hYF2ZѲ-?(JH,V7's2 3&W㛃AtX[ }uHfu]F*w)VǾ(!hG<|x>_Wt1߾gvZ*7#066hر򊲅G.B9Wk@ tkq`X3WUUV|ɂk]ʟZs |;ɓ^<ٷFɍ BX怬hw/]u89a;p1o" [i@* "}U0qD-nu>~]ּ|UY#8Kj-W66?Iz򇪚j+_iI`oKkJ> ¡VQσ=?[Gʭ#####nR 9jq+$z;k^P[y8ᘺP\T5}rXϩ9@=XJ(w,&eRz5!ZG6I1\?bݔ&Pza0 6 oZ /~rʍBZ)pb70ՠQMxv2cn{ ]Y]fW噏W"I ^m0~{m-&д6kv>mQbv.(; endstream endobj 2998 0 obj << /Length 1472 /Filter /FlateDecode >> stream xY[s8~ϯ/0-_le'l >`lAklj\Y6`cR2aw'3G򝋤f>O\: [O51296Fih@ &7<n2/sg?ǿm3w,Ir )iWG GnU!Pkt 狈tK>{IZyXˌUvi:Rd̎Xp?t%bߪ/nlޜg<U/H- ZpIVW~iޠMrb)l/Ik _M/*,M0䬽 :6nUρ`rr8*Ćg{/Ə6WsѡUnp=\!m3%$"q:qeP,>ϯcm1y&R4i ?=8B E5?#qx^p:ᵘĻ y¯'AH#.ѱN!>/xnr-N^tZ?|m˾ .Jv jψϓcݳV/Ȼ/(Ր_N!`.YGnPwo x/Sdbq'y%O^"-6rEĽT -]nl^Mpn_i՘ԒKujp>hll7m@3tմqcE>2dW]%Zn>_Aj,=UqڃD݀jA\AZR)>± kŒ)Yb+[}U+t*&vd [{Z\ ? Fcoi|fR#5˻ ΃B#~gW_7k"\7Q[77>RlHdT@|IM[ nC~l uYz$Ol5@M1P]vYϊhEKi)~rRRT+A(=do)^ۭ䓁9l a}3`/1XңV.VS{pʨppAl q;O0 endstream endobj 3049 0 obj << /Length 2224 /Filter /FlateDecode >> stream xZ[o۸~1/[m,IEfʲ+m I]Q\$Qɹ3Äz>~]~9WʋI-nMѩ;%=a~Z/ÞcGPˡa/x8"4RIo_rҼYUʿXsH*=#BElt L=G; :ǫ[ > w?j [%{Bb̸vGV{rVX [F_/Ùqx6>K]oߦ#S@v? an%2 'Ofu#t[~V.TA%\[sWFWMRU]!vGc,,[}$$'`Q؋aRI[=S9E(x27 dTΝWef FKsp!)J&D@BlHkCsm8f[4ol؇eoN[EsN@.qa.uHxFVmJ]2l6v'|tڪȿX]PBC~im"w J7rI [mgzoF$J젟 hgh*!JA "R9P@ǜ՞mGN6HqTXiE8Pljg;܅]1-QGa;pwIlfvbAs0{Y n=uݔ1߶YmgLBZI`zIZ7lwhI^|yTv1aAx &h9Ήaz>7[zIgNz]r2Z)GYaU[nn VEձ'l㱟w3zi @ DGx{>TW0/8^Ԏǜ2 %`Ď-wE[қՆWaE645Z!\} )*DdYkW-(v%]- Ƕňo`P%u-j_mSEelkQe|$)Ga3\ÉtZ%nd3`ښ .*)u7rfsrc'eR'In6벮:&xUڍ[5N~[FZÉeeZ |΋-|CqI Gz>zB%gƆ%˗(+q[f]~6mj vK jk;N2I8 do1!vQYA$]j=l* SB?/?w?&p,`r 7o)"<:)\O:R+ Σ鶞$PITqs!%$36Nݟt>՛{w ˕/(_nuߐ~ďQ}3֬p՟I-_s%|Cg:_VS叏vThSqw<8a_ZjA 0¾ȟ[ړ %~ܜ Gi^"U zWf+#p7>vx"~\׉? endstream endobj 2960 0 obj << /Type /ObjStm /N 100 /First 1010 /Length 2439 /Filter /FlateDecode >> stream x[r}Wc2kUXE*W JЀ9=@.B.fϜ -T]\c|Fr$B+Edr9GؕTܦP G;DusJ:q Z9T~O0i (?9 )K[2(I藥9D N$鷕N*NJU#MAM.0G.2o{,VֆeKUx|%v)侊Ei%RsPXd !@{HR $,$T$T$ПȐRWOrhro Ju" DD\t++ItAGٕsPfa\eg9*uEEZ+u)ڲ"srB22JUR_!s@iۺBFu>"J#PڐP! 9%L]R7}W0;B5sa-vEJIQN.f8b65T{N]f:1IF2ľRvԷ(EI1YNc#7d3KpJ;*kT܃^AXƧjt{/~X]8n7$*y~uߒ2@_xw0fry؎y:4߳K4p56q G7Wcґ&FGCeAtގii`lҐyu^. ^\ne%m3yId{*F4ޏ+b,{Bbݾ!Tb#}}L3*Deqp.u-ㄦl a3MϏnؾG8c*36fѱ0:љglar=?bMk&=JϸX\&#k a4QϨX8 ~FL5iIIYB|5b`[c8k.:?ܲ݋o6"n|>1c$3fMf/CFC2!c[vrCG;hh)6/)MSo endstream endobj 3066 0 obj << /Length 1608 /Filter /FlateDecode >> stream xڭWKo8WCm fDc6E]q4Zmmd)_3|Rb;ζSp8oϣ"{qѮf07R"k~?༧ h;EF=dM4XߗR 6=`K`3gzEB}nt6F?Z}mQ-ͣ(Qu[MF4 64^Xh0>Itp}T1/SV;?!E.X٥+e'͏|-C^_w]_3" { 8Iԥ흑Ė;ъ^l%31/ݔrh;t6ub@^H&ل%f2kU'fu§!K Oa޻π 6?2k-N+G,T{zDl}-,.'7@q _t`o]ݣ V.ܫK8*$LQ=F(V\]v"JR{z1$VmtB{,N&I]r1. 7hܩUi5'0Mhh (U/u s1 !4!aZUGYznȻ)k'tuݝiEtբp'sSž2 -6ɉ1 zTXj#~/T-Y˞Z2ͦ]Q@EvTF йVɔ'ØsPMٵlWun0^ pu\҄ngP\-l\!%$s ]C$⇆FdlZ-jB}zv R_SGqCC^1D;mdTj)iCL5n,~r.cLQ  M l/ƀIRIpg֍ZJNXKmY]M*w%6_(\6w?!);IH[ÈP v6 ~Ӈ;gZa>׋ ąV& .q+A\}IW SC6FˬyxqILG1wDJϱTk ޟRW~Ɔ@w~U!#a #5DNs]iJl #7P)d]+1pUa} Ww sDun&qÌ4z(C/DruCs7]n0/?Nrvrj0!# wE§$ >wӏj)>tAu=N$rWYyHcb^ٝ-b`bB/9^4xgUlGa|vV׏&Rg`;^c s$\ժޔYWRڕȤ6 ߀㥬dSdVP"p R# rkIm"ſ.C+% odgd+v endstream endobj 3078 0 obj << /Length 1318 /Filter /FlateDecode >> stream xVKo6Wi26Ro)آmEmⶇnLʒ!JaIGE/E!qٻ8v2~,֎G) IbJw+w7Ig,~x}D= HgGɬBf[RUGϨ1:VOV,]V|pS}Sg$In 4tXxAly֥͖Ǚi_ԲZmWk^81z^l^-_+h뙗FT 3fH23@S'nS`sKA8ِ Xplmd^% ~jW") b\N(A I:1H)|”-SRJ8,d&+jVʐGuCfأȝNj2h{{9g{  0`׺nИc8NCHR'Fc\,#=#ne'=_9h̭ܚO9Zl-T™0'>hJ9('&3ɵ& yږ>zF7oɤYuk=Vs)mя,n?TN1$N1= T>L6L\ӿY-[exyToLMO&qT{*;nkS£w/ endstream endobj 3100 0 obj << /Length 2311 /Filter /FlateDecode >> stream xڭY[oܸ~R0[.Ob3Du}M;[("w.C?[Β@4Xi$"4e9 j_:M4"Y2SΨu9Mc9p%En]UWP%|X};`)D^T0Bywg_~A/ȃ=uso۳^U"`(I(HD21G|ftלGI(w5]XV٧S )iz)H[c\vݔ#G`('in0k;S̓~ϳnrWUaJsq@d|Ufr;jvhށ'ЕսYY>I3t=Hܺv˪0vݣ]Z{;ciREKyed5Vޫ86ؕz=gP1r{pcB;?Ya^e)1إ $ ?t|X_yoevB'jTwh*eͼz|fB)' K}OmמP.I&J`"!2@/&,f@CGoZW^C<_Gx$>N"]9xȂϹlԟf]0H%S1lSmFj?ƌ: Rw 8t@R*roOCI2ݛq6$<9T愊|VX5$^bYD=z+MN1wM8vRg~dn,$FWaovo.΋30ޏX$N٦fLAŝf ƶBMP Evh O}1؄ʼqz%&)x$]6xRohP ?X)r u2,$lGoᐉlL`:2_C#&)$Z'"uu~P㕕Ψd霐 ظ[W*}yLKFa"s:YnW$MCe Ds(ullܪhke"lF"M'.5W\.m">>G6ðC5;s}6b:)n֍|M=8ҎQ`$Rc 1pӾ-Vi-`x-5AouJG̶zU{ L4`z-@Z+.ϵ|5HiP?@ Ts j 1UdS:%Ƹ0N4`^s#`CևiDWy)Ha c;RNi%*B8#bI@BbH~e)mU'~ meNZ&zI42. sr?, yg endstream endobj 3113 0 obj << /Length 2330 /Filter /FlateDecode >> stream xYK8W}Y9g{`'^ L9L@K]YROԫNA4EY~[Vo~Ç(Z,x߯|c"VqP}uxÇ8a̸3'$ZJ+xvdtny$}mQWlyRIU wT-eYox~,Fv6dcWuKlZ^i=*DL,% _Ѓ>6OzT"mpU[?\?tm+ʢld4L>!IYSkM?hPUF7[wi=[t-uYeWDxh p%"|ԪӹndsTKC85 S<S4`UN#RS8 3Kge%An w٩*É&놆sʢ4AZNz,vZvC\v Yd{\s 9}W_"/o4=.uh ҋ ؆nzhh^Evm }$Ľ>9@doY$!':wc_ H0V ;<6߻}0 ] SL䱃H@1! ]PCPE-2 鍄CvzWI' c, 8&͟j*GB%3w?0Й{FB}$iϵq)о< cD6nXx:I1}cn:QLo`!4PFoeG&$`x Z=pLi #煈xpR#4˜zu!Xw9oRÉ8Gc[wly!9MQv_i?Jjv}I!XG\eq?JO IewPDL_DɵZ#L?{x +@Ey>^e;S^UjSr`#LE,{ɻkrzs?Z| EhY0:m繻Kp XZm ܃̣Q9BBJF=8/ >ͮ8@l,1(qF V/LIO8H?&ef*ɞ2&j[֓'{,r< QJ!f1>wr:ಯL(9W㬬+q(0he߹;5qHO^)SBU[> stream xY[s۶~ϯФ/Ҍ>s:t:HJP}~Iɉ.=1A` n{닟/^’{y㜉 E!gR?*5ļNj_߿ƾ{,{H[1؋Џp'}"}J/5`KxӳzX)K ,f+RMd4]ƸKY~zZef:yb fiNR`OLor ``#M$0Mba0 KU˜~A4\1?~Af`KG: ]yQ:(MUѬW q9z/ V10D$4W$p}.6fØaUF:Ơ?kYxK5]K+e@yY,wOƽA(sV٭ղЖ@`@2R􎠎"AFh9 ȏ,Rz`0ͻ+"kX0)L,Z S)sHk44--3m{Hޮ_1].Ygݠ0kRUYn4x &=Wt]/s'Pn1iw+w( 5Q@Rɶ!vUZeENs}B0D'ݢ3RL[q;bP,>m Y fERc-C&j⺠WڒIjPvG?d1 d;=V}/ Lj^_\@ ZaԩZ.#!(޼jggVc.sJ yQڬ<""x>:M_GeTYSY87 6RW&!rKO8G lKb4p$ 3nTY׹"w5y fu69˳]x^9D$FcC7,hVi܇<8"9ߡ5 .`a0k-Ѥ)5Ti(Ʉ+%w(-7f%jyAs *[8UVjg4>}K/HXˀBU M2F Rۄ~?ȹu{jhTXfRm0gygTˢR{nz#;>{~Dܝ)83!:5`'({'7L5xEU{vHHnS'z.E6{~8]{]ON?? k??yAJCwLMvГ_T^e>C[amv?`C0NϷs7=p9\} &o|-ɐljrSAi~xGA o$?)ˋt&ǞF1ZaP4#0ﾫ?a8'=Fo]=gDr*F/߰x}c:9ninﲚ.I;GAd+渥Kt.NL??~;UmKUH{gdk)mےZ< dbbQ endstream endobj 3168 0 obj << /Length 2026 /Filter /FlateDecode >> stream xڭY[o8~ϯ26Psx%}H"ڦ3m0k!K$7?7IY("wn #$H$4"1bq F:,2vw)dsǬolN]/3lzIAz݁o/_ gQHEŗo8$,F1!(Ň~(cFILLjPV/g(#) (zRx_.ck}ZNVY}`k"1JZX0)" RQ)v]QW,ZQpN5VU,YDъ(RhA$|CoSvݤz8aFphGAEN1+[ ?^*?}N4=_1뺪@{[?dc,$ z, ^5?#iiĦؗn)CYG~@/'e#ͱ@:77s % |vbpcMǬa2Zt7c:ڡ#dzgH pSW9P+Ts ""@8Bdŀf]QB(JJ)_SXod#םjk5EuoEN%oo^-@ӅB|hWFb&vqҴDeB0*`ޗSY *?Ŋ }3๮2!|/˃~˲15h]oV@D j U ?-^l7v틗G׌ Iv(T49TJI4DK'eIg(=ʈ6>BMo+Kremkzp+OWl 14Pjv@1 N0;4S8֤z~t@Pet/.4@7Ke-\-IoZxC &i6|izyn3fgkLM_02f *U](򌺙'PQa0>OA^c^49ЫA A;襶B4{K$_v}/79Y]藰`նq9[Td: }KAG4ݣ~:htRDX_ogfC`/l.ZHe$ zw:TCC-\ֹ:/9P 0[7%YX}4X悊嶶LPJze`ITү J,7A3ޛKd퇑R=`*s9vx"x7TB`ThӲـ3ȥgSW~]\~?3ܩF錠wY~[aoc@JM`s < K)[wNb8@2^_:z8P̍z `6-ݖ0mb[Yg.kQqUp?(Sɲ팓s12$k$'4a=ֲj}s V箩Uz^eFյ'F C& Fb Q7>Z`PpQC*v5Mp!D5{s3gvfdڜtA,1ЕC{RD49n$){6Q,8~$RRڧNmwu#Üpwc1jbu΀ط `K_c93zr?ߗs TRazZCN[X7Է ÿX|cvw endstream endobj 3057 0 obj << /Type /ObjStm /N 100 /First 997 /Length 2560 /Filter /FlateDecode >> stream xZKs7W{+J-YUy+}|qtH*$,rdD59ƇFv3b0OYbG΄"Xd189C*Q(dS67c ; Mq:M "Q)x' |cΏ@iᢿ]=)@}xG)*R (bE_,*928֧y @ქRHr.XLGTSHWY؈,bJp]yFDY9@x bU_d% 7&gRt' @#PT $A)~l u[0Y,CE)pI9(pɾ>%P1b%ߜ }L R(*&sA,DIUI+$VE$9*u>OIEKW`Y7L CTbraz]T@ES6tpodSS@JMHȔ,*b.ː'G N#joN`}:6ZbDeVT-` 0/GxdVYU50*:SÏ<_.k|p0#|QÁrm`2iOT vfߏ?-ڼ5㟞47ǵy7#:<܍WjQbyڭ6]kw6<[|4oX(ze|%!LnªjCDjoWh||q_M翌˳nYw㿌o~5b$a٪V)b%="?6ofܮjr.?@AElQӎF^RcIDsvy:%E0hxa1 z@oHTDb6;2:8E8E\"oD!LhUeGglRoBYw L쁦U] h5b6{w`hYXc @\hL}j7Yw4>WӿO"p8|;px4" EM9"\u+ANZXuHT:Id2baZWt'fA$ݺ=FǒmAvs43$铊e_jntJև[nVC#b#R#Z[VZVZVZVƹ4Υq.iHnu(69hB[ X }60? lUV6hE *3@bϠ?n9h)*c5JVkLbQ lH v`GT#؍b];1~5|V)[$`9wfy7 A^E,B; ,d=].p`kɡDO?|gҀG%G| m+@(C3Sڀ*ARU `M{6v2eCx4 ƪ ѡ8.zqZ-+ o/|i&OƢcY(}a`T)HJ-NN?Xk{!dq^(X= Z3>GFsY[@.zL3U,9s _sV zN̛bvq>zZcan?s@=B-(hG{ɪs- g1*"6_!!'3|= CrW8h{`qDSY7XGzLWC„Q!+HI}cwzҮJFDP!^P6m&Q!IS>#;ZQ'?tO _pzz2S[cZs8BSe>P^_t4&@L[cGG H.%T=q>P<.GD+Blz6=AosFJڴ,y+i7;[ `MzmXr/4?\VC=t%c*b!ɗp4z~x5lke&%Σ.sgg%i3.k>kx Dloxcǜki}HO:eŹ"T+rD}P%(`j;6zA"8x\5dӎ;Fb>3D%U7_]тg9ZӴOpuR・uB밅a w׮R^Kz-ԮRl88W5zyU U ݺG%3 endstream endobj 3181 0 obj << /Length 2416 /Filter /FlateDecode >> stream x]o6}C^@K;[rE9ipH}Eņ!9|Pb?B0q(Y0X<߼bkSq\] zd@ 9K3nvf!.y`] Rі(۲~ b8Yr۞jڀ򌥡 ;=ݻBYGP)n 8BH֣hxp1w'5'~>#5H$nVU)s: w5]8Gٖ+$LX2圉8&r_/VySkMZA骪f]wjV )O?*/~KTH] (̏2 '2iƢ3I5(9KYn%ʬPdM팲„w>} bOd%2h,m|+y^dE{"Qlj= #4z&}Hmkwn*{wbD,'F;ZDZ$Oem"N?_T˺㕆  Kes ϫ7HQo2Ro4xFiǩ^!D!Z<.t5 `J5q kYo*ҹ8 F kX@7Jx9CW"gϻoZX}f4l;P+PSU4J2 sM8.g(*&ܘB(GڂvSzb0g9bvWZPZݹs =,|O+EĬ2*uIFH8be =M֦.cC*S yʟϿ|H{F򬦙(Zd 6R&+$ iIO #ϔuAͺ t`sNһy0e\]JA'lk$biM(L#uMmYT3*p&;[N}Zr(._Wy}5*1e}? ^N Ts/p XV0` ?,-?_>~lA:&jJ4^'=Lܬ-X\MΠHEﺨ.4 =/}3BrQ7>!a-B3z`}]iil.B!}crtuŊLkN(%9]㪼]a2ac[1*=^T `5'^b^bUU۸M4St<<]d#.NunԏR:?Wu yg/$aHثQӤ3LӔFsp/k!CImFfyGã!:v@胂1.kUSG{jLN_ehl'7c.lj˾^)aǂ'e#:7nwl߁hs ^^Rd]JI>iYӲ-:}teߚ epO[υcg(mPf_I~~|_ endstream endobj 3224 0 obj << /Length 1964 /Filter /FlateDecode >> stream xko8{~O6P1|/mY\mQ(mN\Qn;)YRN0`Q9 t۫3sBzs19`ԹJO?_,Ldq)` ypǥ3>Q*zxRk9uOXtaje%z}kʮM*y-e-fu̳+l*3J,S(a 4pEMh, Q Hx }.] <Ḅ<l'J{"OH`ڈ&"aTdJ&T{$>%?>߬+ڀh|i`["hMɶ2yQC BP(X*icdda|SCs%LjZᕓI|XUfLO"LoLdY-ab4ّPrwn%ͻh AO0ѓFf#;sq$jsP{ +.:0n7R5TkjZP7=( /F+ꀸbz&+\ R屚YCSjfxVyHPp HsfyrUK!pШt݇B,n O˱rX\+eTD?_ _+Z'@ؘ=@΂#](Ax ̩sY!z=:A ah|Q+~x[Y޾7~.d 8\eir!;KecϿF~nkg?h4 K!Ýz-*9Od^ӇM H|h~ @-cĞ .Tu A|M\Vp ;#@OğezX߫*`wQm߳*oLk +5O(Lnɺ=gCkl U^8nk;lf!Ry^5EK/e]L؍5. wb8 m:zBj퓶YN>; |sS/];<ڦ3^խ~´]Yj}B:;{Br(Lx?<ˠ^"]{ ::G3ǴփY?[p}ϛ@_ P.f\)HtW_M.%#vFvx'i%U17TU@*r7(.֧_P@:N}L/G endstream endobj 3234 0 obj << /Length 1599 /Filter /FlateDecode >> stream xڭXoH_܇b), ti.9˩ԫN1*IB%iˋY6 }~5{w{Fh c1۶\. _ؖ2c_̪\0ϼ+\֋?ޝ 18m`IfCKMd>ё(eĻ?FW /ǷDכҳmM*4QG*>dQfUz`+d XZ_H4'.y{|$j"kSAq4']<-ݑjv3sm8=yµ|q>6-7 ;E4q5(h(8HpWt@rAf d [YY3;z!njo - q͝eEw\n PQ^Spف0.:]58ӫ!]KM;#gBiFnBe-G`oR۴w*4a. y\ڊ*jߖ5UTYtEh6%}@B)EEd-i/eP!s,^e\ޥYF֒vblFH8gSNAڸD]%^GYF|9ך+8*CധVVzYɦ 2*0 \6š!{iٖ^yQR6[MρoC-#4\Ӥ&Quº*N L ,KRirh/45&!ATG#УXd5d@Y6~=;b*;/b#+tu)6;ΝC6@0@p [jK:}OS@#[}t:1i@2#:`Çj r?*H&T[G Z4:ܲ酃ȁ;=1[q!p-\kӆ0a$yN( ҅cJ 56ѷxUQP9 q+ LZ%wT̔sN%oڔ\?QC0χa8pp&jސ2iICRՋ|0CRr+gȪ+@lJTU :fd;uTB;}2&uK^wG~o[7{=uzoen@yGU}xe)+?ǿ>_yzy的 >!C3pu7EU~@xN{d+ endstream endobj 3246 0 obj << /Length 1673 /Filter /FlateDecode >> stream xڥXYoF~  6<>88p]VŊ\Il)Rᒶ;H0vʱ֖c}<{8{! %Z:yhE߳Ŏٷŧ7`OG*G~Ux1:{ko "^ M 27bu;:r8Ya0`X a"L:/qùEʟˡF^b8s e8T׉=\nw(8E{3]8`fИQAvģ-i,S壮 \Ѭ P%hUjah4L3 ́FjQУITP)8㩚*|}ITFRl";2YFx ڌC,Wr5`Hct> stream xZ[sSG~2gFRe d]V&{#"p#gO C02pZ7a>/&'+{r9{I}5yWzO^OFDդ⭆娿arEmQ_+`x[\>9#;,:bx 7oEs!`E3"N#ٚtu| 8FFբb,b] `:_/~(MZ0۠Q?TAm$iQfdngNL(gUa7Ír;B^!qS"Q' &o 5Njck~ľy@*QǦ{޿]{ 0֨u5ryޯ65ot`T FZ 9k~:YB]W'XaZr+Zqo\# EP\C(h',Q}~Z!ơv fQX&cXCП=Dۅ*97lAFH#$&4e+Y-AFH#B#b#R#r#d$&7ɾIMo}d$&djُ\GDh,kYeTT6oGa7sȘ.bŞ&xp"hT ڵ"oĘGBK+<,z,"h/aPJiEkN}xr;H_iqH&.="t$lPGN-B廷zL*i7$(S $z5o 872R r wo7 Ǭk9Z%: 1aP]w#zJNذԔe(#02,@+-FT =-rAh1M/FPp@(ϓ0_GoKOۏb5fv3܂_?g՘WE'S ke 旳1=huH2Mq,v`w![8'҂s3VD{u@wX(Œk0/=3JvX`4L;{bdnG@9Eu>rBu多~ZEںl9]B I֡%aq۾}HQg$ ys ^o=l {q_r!h ü]qYIATS'GNzvCb؜FYG~͂^4٦HY~h}gWzoӓ Bg[; QNO7oVn =-_~̫.9Bwjbt~H9_ޛ  \c~?22[/vy?N f8K^RgNN?ytF'$5 ]rȨS~p2[HGCe@20{[W[$[2mFT[|/ǭ#K]- J):R=_2z9米~3r_e~ wRCtȭq%~ W endstream endobj 3261 0 obj << /Length 1837 /Filter /FlateDecode >> stream xڥX_8ODڸS=mvӧHpt@ͷ&eU6fl73q.M/^_H0Lu]q%ǜi|Vdy20er}ܥ$ȅk^t5xt|guV:r֙swἭu \AX*bh8uFZuMQјa+.ӼeraX{&6WWED`3}^F)e"h@׀3ago j,,Z9A;ڎcm}*Oz>} ]am ڦzoQHV+.GB\:vPXٻ4Oݑ܋Hbx22&r1Rf=/$4]ke*ƥJNoHQ9$Uy \W[}p]Tu`6C"JRpy-ʸ(c _x){e^䗣0qy(GC@W&fb"$/E>Fm#pJsy{oJHuNY5x4`lu5MJ<˭ h$[ 0m f1!sS 1߯|_R9dkP˖!5i[&TD<)tK)o:.#E63l}b mERk zU+6P$绿4ZZCl(ɲ07=З{ G$c^ (J"OE?`l,6 Nl&sl3|?cQ%[i7 0xyiD\bVq3CG=*eW81 =c°c"ۮs$),a 끹i&@y"]6r^5)x/B-ƽի}$(r]`.̕wF꓉U攁T04H2}O&8|1|ؚ40&C1 oaWl qf&+y{ otFD> stream xڭYo6_!e2P%@6:dڸO00%G?dQ{y<,V~|XL^ű,fJI^SC-rﻟJ20E>):w=jNcgv%8y|(8`șz %)zAjȡ"5"6Z%$=hA꯶kYu㩿޶jwRlD\4ߛX]sE,Fsj"?u)EwEYngXjE0Vkos1dX$~[*Ti|J@T@\a#K)ZI?XL(ԧ^-֛RO[)0ާ 4Cj*_`8on?/ LgRh|럫i/$8y^k\]Zwy8nb8 @=h|z9,$RIr+(^N R]](x C$s3 ukq+jPna#g'ҐG#Hs#QeSlb j Y FKh \2:(:Iԣǯt_?\_ԇ8"A絨`T:\e-;:ןE0k=eɃ ˱:}8`ЗpխB߶~k`6~'rf' l0o\+y:ƿS70חueYũ̏qb5M ZJǫ+. 83l *!g, LkՍud/"zjz kV~}n0L`NlN~xL,Ts$o \LFs8g)#1ˌmL1}WQdKjRuCv 4`zTtzԡpQ\}!Іġ5$e$+2P,$}o}6.F^'1%#Bى* lgx5$SFdvޞxurP 1[Q?(e:ޙRY {aͳ|4fYJ85^u*(WLW1UI;Ҿj_#'-q(sDʔ䪘2"RJ/Nu%]6>x!}S F8EÆly5dјBe `8:{UЂ~j/;1.5%S4+` K_۩{F xg.mv]Ya نnؗAjZ1TڥJ"]+tԥeqH8s0c>wǎXJ6fٶXNi@x X1X-eۜqqxʆ4k뷱B c)6 hr2( YdIRV-&h h1~Ќ(=c"m~ڵzkDՖf*'fyEVGbfB&Z@U!{GuFaETJ 9b6P ֔|(^eEQߪ/j- u*/{A=U~w=Q=n om#î޺&5d гgԪ/x`A]!M<?viGs=I'ͷ뱀|WFIx)K>ɨ{o G۷-n8^ &ԭj&!t`nhw0w;>k9ןK\.&ru endstream endobj 3282 0 obj << /Length 1662 /Filter /FlateDecode >> stream xڥXo6_!d{Hddh>@KMJJ;HUJiP:Q}hl1{=O"'#Yrx $$ |gY87ns[Z6yC$Y/ˌ;0 ?Qkw2Q6}óu(ݞb%J1sN6dȚ,∄ #Y_kS^%R;u-6<5RT%kQ_J^rpb5 8Գol/t”8샙  9d=罙/"JݓaѪ'f!W ZҲ_[=Q"՟'E(2{"Bf(чZ/O`$˵++d޺UAT*~߃]y]vWL6<|1o޻+oz$Ӌ3{l9yu'I;nv:|MIνf9!O@ӓy!r0`ozNB!F!rI6,,|yң.F깅Ra ؏5kõ:Z"˚H}OHVPx2/X?m'uzK`_ꞥv )~1:?T?ke A?">kJǶyDT] .q4YL.?_\L%,Լ'O94 _VϷB9p`{s^ @E1sdzNBlþ>3x7x/yn`o%~> stream xڥX[o8~ee fE%"ݶ v6ۗv%:ю,ͿsxHYręa"yHwx^z}z.ǃ2(`*M}`/j2TKU 5u{h׸~S)QnDDG?TQ>־z'q$ͥocGʛzQAuCmGS:*?^_^RC˽7O87Nq KvGʶpJ>ȋ훲ˏ@-]Y}]q<>1 W`Oݬ{sqQ[Ol$PgAK cz#T6dCIoqi$e\ȗ\D-R)<ۿ]ޖ[S7CMX^\zdPF~FAԵ|ޡr}Tn-im-odv1VC[OZ޾ӧѷouQ肍qrTHPF׻c(b-UVٹfg {KYև%IczS; i۬rJPӭ.yo}ug$Q:C\He_mc(ψƲJչ3uK]Ѐ!ڮAqb_suXsr&L*ct/B)Ĝ0%NH1wn% n]5χu~r̹6pV!Cfy$ ;Qd==q4d6\Ōs%gdSg{.)R$㲋FA#V1y%%|3Q9*5OakXOaGR<-ʮ$4?t@a&,zg.TMT ^UyD`)IYcLh% WMtR}[ݶ Tj[od"lXzۺŅ$b%w7U-~0 zyN!%1SɉCS[qZExm>YL,BH<3Lh4A ]vǂg9/=+4ka&\x]g*vAtac+68nϾ< }'Pī #){*nDXy\DxX ,APC}&jl[Fo>9Ց@+k{ڂrfK \sAB0l^h Yh -4N 2J5e&J] fxP@`DN79{c캬IVU1>D'Pe~1G=*ıU`y[!5"xJPb(![4#A QښvLH<($ 1k6"6sEOs\N8/g YhUȑ2"aePƸRtݒ!,I,fAhO̍ v&J2NòwELYGYݸTPjbHjMxzXј鸪<tNu BΕvY9N lQ#%;Th_`^]$SuSo~xM_4n `ڄ| 1x pYDg{ "(8yE<1߲ӟ^<$(wNp? ԺiH#CY&L [օKq!ڮ8~zg )S U?(MiMHX SeFf?QP endstream endobj 3310 0 obj << /Length 871 /Filter /FlateDecode >> stream xWO0_e5I)01mА= Bώ/5)*b*҃H7 ;TECݔ,SP\_eDP!$hiol5/]Q5!ss[e&=ElBm; @wq^S"p{c]Fi,H/qfetG-ihOBxaNW`g.S 'rAbnt(~PRވ> stream xZ[OH~WHws! }p uv=mmv0B39߹ȺuvS,Z-M(`6x8mÝoN </B֔!BKۏMK5'apY&j=}j;6eԚw͒8NǸ"fnlc#N@0dG5$u)hG_}*@KZkxgdsv&AevuxYC# _H!KWyF47)S)CAc4VWOd_;~5A]Z>d!D{o:^ݾߗ 1_z%T&rY5:U)D; 9u='b endstream endobj 3254 0 obj << /Type /ObjStm /N 100 /First 983 /Length 2403 /Filter /FlateDecode >> stream xZn\7}WqHJ@@ Xcܵ{ھw81E  )_$t\S] \i MxF¯ts9&=^)d"C Im*!3eꐪ-9di&UUO`:g[T^ vh SԪI2W?،nl+\T )k${Wۏ°lUc{ l.[P=]Lf~[t<ܚm j{vH},7KNAh $s塇۠Ԁe.LcN)dG)CᡒY ldhlrPRdNT*DŜ͌K1p^l#X\|YB-}H%T%!9k68F4zPJfЂI Qjb(skCJTC# ͖B(Zq MqW]2Ȥ=%t:jiU*F5q#d/Ţ -H?}~ Wa~e./_ruya>og_?//1VzMrl#;:[ZZÚ̬u.!rxd˳#}\mz<>韱i%*iD`JX,E-߅_ޟ_ǟ^3b22 DĬI>0Llvr=dy>Iƈ(3 t^^iF+8@aZƵz׆w?mQ8!+%f"*AD%xd]~nH`h6+\WvVPX䐧kTvD\즍*`oqجJ1m&d&N :B $-84ToHA nRŎjKA#*GBFl~Y*caEVVaeʣZ',zutydKߢC͏[ʎ-UCOvzӽh~cWm>}7mFJdEϤsgF+Qޏ6Jޙwi ]斢ꮖ%=)y:_{]=mgQ?5{&h;]0R"I@3eЌ^;^|Zl]?]\Xʺ5L*iǟ6ٞXK͐#1ӳW#bf H D/ z hJkڰ26 F(((⿧`?O>./nUQ+?\Үq}/Eswև%*ͨvi6ش?̯TӭJeݏTGM9n(O 8Mwu*w]+*aj{ BsoJ.dvɑɑɑɑɑّّّّّّّّّّőőőR^lGGGGG.\8rq~o~o~oő#WG\:rudbbb>ȱ:rs͑#7Gn9rsț&tYؚitM50ewde>c1" zjXdK(i;/ +G͛<jz2H0"׍Ph&cn*vQD!bg{ b"}rmdZƆؑ{-F!7ts!Ax)m=-{JMB^O@4#Ć6$aCoLE2'Ӯ:f HU'ʜ`4W{ۨVQќ!1?&IA A\&q);K))f *N{iDutXr?,3z^h۰D=/_6$)^5y[Yʬ$ng]6p~n]aaۤ':A.8jJe;y :xbG wtbNF=x0,l=!)e}^uvA:!'4POTXR>uN?2R(^at{O+OtUJB^&pJ{/S]AÏ=M1v=G8(&=L]$ &;M"W4/]4vKc:.uDeܐQm-u[@#h endstream endobj 3986 0 obj << /Length 2753 /Filter /FlateDecode >> stream x]ێ6}߯c tN-\-ZUֶWe[7S22$lr$3gf ѧQ"mpd2͖U-2Z2z ~w]X`}2,n$r&C15Ƒh3h&E2ş1J\yˆ=x>.T#_o"{\;WH.߫$IFi$htQxuY~Ү+˟Ip[:֕dC}NNTzI.]n+w|'ׄNQsKvCT77b8O߂1\݃;zsO{3׉F_ۈ \xTO+nvO[3?;{%>+=%ZÁ+r,rͩ0;CցBH~Y"gq*呲)xz%eh+')` ȿxxqmA0{? D0a&wCa-?-@ ~H_aHb(̪:jkK&FC|cLRɵHTD8+Yޕ;ws&_]xLՈA3 ^OraRF~xDQ.E\HvX$=~+jVoVI!pzVr,-3g{{QxJg0| <С\Yn[BW.MeCӄC<8̄Ő\P;;1nN1y_-v6.1Ka ?);{| Dzb!_}zNΔ~|J=PXȮ4My rSx OHWM?j>mc*-4j.)K ]5Y()4JrUܣš}#J@AIeIGm>8B@N'm>n 5 5f_v'<|U%/pw p`oo%AfN)h]!]H܃E#Fȱ}`Io1@Z ]P~@ iºCk}b\-;5Tu.'Z5 _]V'DgnWπLF p\߸K'Y w9NH0o)/N*ҝ1r5֡z?9It]dXIOwo:DA8*D\z>q:$ک# ٔF}vKʱyljz/=UuZ*ĦZ)rS(BEHk9PU^K &|7ɽWol-wV˽9nᗻ8>LFD(5f>eDP0أs bfh[9BgqWֹ޻@x L= *9qSIenryZijrrE]G:m8نۯupO&p>ؽg ~{' Q~'8jޖ7g\y~0\ Ož] ֍?:TuT(TļM⮩O˶Lns(%ygxXDu[WKXǥCܟt>!RuEB'(RçHW$@ )Ty?C觏 sz4-. ֈ"*d]u鑷ܿ[ˀ3>+\? endstream endobj 3396 0 obj << /Type /ObjStm /N 100 /First 1039 /Length 3631 /Filter /FlateDecode >> stream xڽK$q|:ZGB$ Hl=??۟ˇ,?<=5-2[acͳQFm~۾b{v{߽ߞ?K}Id#=t-߽c6|c?1 [X[՟2Yv#9/GV%vtiQ|>i'&3Cn弹'kIșglځ'%jn0 Y҈7z^9L,c;Ky“UC#ǢVêfCl kvǜ]b16h oZ#!hy9>rL׶rޒA9NMe=F9ŰtS7Ȓ-]sxБ:8b@SY[9ɕiMkjNy%z?llY$k~6r.*S7e7Yz7{DφVsôv=fǽqnT9˽k̙b"G:e6:1sƸ46+uS.9S|69 +;e1WV\uHB -do9?h:U?Pș>) vbj6cF.L3qřUKz<&:Ds^Uk(R^ DuĨѫRvo. ]ΙB}RRrqZF֋B3u=CݪnW}R!Mj QzNFb q+dt{Ȇ_ U: fw8u6wpYKt ^A^|w/A}ձSeUWǬn\\Z7R2uWǎ\__fΘ?\-}\[sſj޿xU[c_㮎\~!nHPwd?~_xӷ/M篿j{o~x_WzzCǟ~R#|O*YP72Hr?yTuܚl8qSlL6†al8DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD^D^D^D^D^D^D^D^D^D^D" Bd!Y,D" Jd%YDV"+Jd#وlD6"Fd#ىDv";Nd'ىD"jA r A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :``00 ``00 ``00 ``00 ``00 ``00 ``00 ``00 ``00N}(7g1-ULn8.1\So?{.S6[F|B:fDVkc6n=[unzndQziTw@n4OH:<'sІh ?k55{v"kcz:sMj#mCSǣɷ :eSAGow3bEY.dh=\a'ctԳɵz얧#qfة$kJKnNBG $l~qSOd9KU{xM |j|׾3tkt{9'I'%1`Ctʻ9ngctMb7:q3yM"NJ|?Đ\tkZ/.μPh|$zM[#%tF կIHz^Drb9WU2asJRjAI\^]_yĪuVf Nq ^`'.{)Sk .欷5^Sȿxv '.ƪ/_3+84GwѤRoPuo{uk$VH xpM['7Hw8"~5/:sJI]I,HC\(< endstream endobj 3988 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1865 /Filter /FlateDecode >> stream xڽ;o\7{ I _C0$@ UH,p{ƚ-H *(%9<\J)R$PZ[CchBͤЇk jTZ RGW4Qhu-Q )S@CFˁF+hgGG] Q#Ikt4>u}$k{\k=)AG5}t|0)JG(ZnMk̞,0Ц֕D"-T>Ae9jH#zHxG k!Ǽ:c%Z2Jh6-аZjact,_:Zz9ZbhBBZYb:{IMK%jM. sE8 IgKQ Rl@.JWAzf- Ҏj1S21J]N[FB)ihW%FoQo2Ӣ@XiJ-"EtīG2 ӋQ锡ި5Y0 Sy 'V^61-ZDo\XU$[IB4*VXxëW_>\|?.<~w ʐ~p;:x22 1GH;V1v<&z.o_z:~Ub'DO+BcCM) QAPQS XT#gBZ"TZ$`a<@cq#eBA 'èq +aHص)őgh ӂr|H)%62JO,TI(؆ر=X$EϨ0`2N6`X PA >P71:}2I"Y `gjNKMԜ gjz U,D0 1f2d f` y .:dZo`&a`| f"ƅ(Ly1IblPJ8҅; R3 Zi V; N!4S-]g)nǽ/u44Zz}X06h1V: K&'ÔJnPJc04S('NIC0ʆF(vȝc~bG8eC<c1X@x2i Z/[R&ѳC8cm;@k>w]_ )SAS; dZ:r"'[A_ ڰaBȆ0[ 1!=kR'';B"/5`"-.!r`3,w@6\q̐;2/}}}˕p'q));[!oػHva8hc׳6v ;.l8vL} ^;N"\E%N')>B WS}A<ep|s\9~)elW}vd< 6\ONHbuyBLt!p endstream endobj 3989 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1993 /Filter /FlateDecode >> stream xڽK$7Wh9ިBl{C1= {Je͔rtU NdjK%IUO$ w*ѧr2hHj=:WMk4jR[,yAᖼ͵nD +%9EuLq41F&hZb k OZax^_/ĝ0/)qMεK R1FCn~~}ܾ/|_ 忷߾}/|sz$#5{eY]}nçtg?!7"} ,ɥ=wL>d" -Y@ud+f3g,@\^C' L :23p9>Mɸ#pɡS X uR[en~"%,dev$[JN0e9Vfb ɑş򀥉:dXPg.yXGb/:xPW&TTB`{֌ae>pQ[DPHTbiډ[w y04HT90%I4fgb{ m Z .YgQE'Ls dr :9 tr@B9 rJ9 r@R9 r@ܵrP X!j9 vCrDy>QgUg@-wXN  VNjvaԜd9|ks]_t {9hb/;}}y@u}}y@BVѫʴv^ jհGۡwPNBy:9CPS"\(7ONw&W;%gKmw$g.pw#g+_ڏ$ sR͕ވ 2 {Bee/p/aҗAý ^W1 B2 {Be@e,sa_ve'fư? 0̔C._ĪQ  |+-#N lX=Bga=4 Ş bT(e0 =uZcːWyj6?0JJjܱ֤HEJ4l'´0f]¿q  Vd(4t$L܀2``jBQ*"os$E2g1CU f#pPlke3uke R]C"0s' +5BʧGZjW'rW\p~"-ʴR*-ZȉXyHHT_ ֢H˕Qk8JPr۸lq%o>F:+~8v2j9AhΰH1J8ě;>.V5(xsN0DAu0@ WfDǦQiY]= ڐ6̊6^fb/b7SYjo,?ZN!C.C.m\!3-r`r9q/ˊ4L7У endstream endobj 3990 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1787 /Filter /FlateDecode >> stream xڽM]5 +͹qDZTU* +]ł !ʂC|nWY$SUinyc'&)HT54h0~5JY&n}8Qg=%nfX𑤘!|($R~BR)lVAUzOK.Fk}"à:@ ٨аQV~5<.ZfM$dT. lLFjDg?M47rjUڠԘjը aiQ'F.X\񍑸ճ p\ӧp"5kR/Sl65LPOi3jEdj֢$@$)x@0㍪Z'INHIa>$ "Ft'zl(Q%8F;GFؓzϩjO.W*6HtkI֪f4)[4II-Т'UE8NR4ΞNAvfl!'iDaA%!բJ>oES1 Q=݋"b,Ftp"V }a YxIR vqD-ф2Ab**g_Xŋۛ?KWp{o?7> eȿ~x-n?sz[E{:h, ^/u}͇t.}?_/wZO }CrT@z[!XQQfDm9b^BT dP!D[>\ T}eHA.#VF(ΠBh!ʑ=,9C P$z9\#ub@, K.2 r9!\.C rAA.2мa6j9r"9*$[e0TVF B8F(KBエJ'@,fZCT"k {b&b::6S=#`!6/~BXּrEH(.}B\Vڰw|BC {CA4ڠnػB7]{WuCR}gT?dؑ;LCݐ;ҺS q!oK1\B*/ rB. r .!oKp !tbztː7X;^n~ yD-WFPZp/4@lvMc"SDL !G"\aBgQ#I#*fs)TȰQW  =S;S bP1Ć!f 2z=f C)BBPJp xT:keȰC+beȰC,2 j9!. V\|K>:gz]-'eȰji2Vn2b KJ2 .!C_/u2BXZNN)!ŽJ ʷ5#@Shpa gx!f@D +/|fGރZƳD`wK!R-bs gpyC A1b^|A{煘ļw!{a; [NJ=|Cv浵*OblHl'g!Î< Exj̄/fB]8g3nbf3!Cp ~ B(Qow25xK•*q^9!\"oR9+Up !v]JBlP*gpR9T7(3R}y儸+# endstream endobj 3991 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1831 /Filter /FlateDecode >> stream xڽn\7 Z3"E#@m.z1@oߟ^H&}_$U!TJI=p)ds:C):'P{ցcr]Q F1 ŨM^Pu^@<,ø$0+K-9pj%p&VzlU|,~RHXNG+E]V$yRc"=V\5(KmA(y={$ 5 "b2LRH|-^$UZJ3\t^!E6ܳ)_`$0+SҰ).Z5K1è UZE k8T.FPӑx;(X}+w/UDy-tCcjbhIՈBVHB)*&J(WB'!AAkz9<u2 ]q1{y0XD㘩ћ.h(~o\GL+AW#cS4bW&b] ~(jyVQǰF|ajj #&cVᖈuĉXqvuZai1%_._xo?|x|OrӟG(Ci\sx Αq+ }3#yo] ~yWhux? Z=Q#xeu~GHG<:|@<& CT AB#&;!"j>Hg4uN><Q2 M`>B_@P! B0AwBHHW$b8C:^+3Mk29H\Q)aB~$F %d@vơJBzx K,0AmD}JM (bA1Z?rJZL+=ZiC!`R14SJaP 71:  `21 *y2L̄D^ԥoPI0 *odetL']A( „҃X{9 L)]pH C3$ [熈0iCDErL4aQ.،FIĆ߄8ӅXAB,mSi gz K \KOxLO!f&Y͸eC5cV͸Kkj^I[*_\@ d_*hUu\!X'Cؓc{kzlcO2]pv]=&˰rת(}4*.HԓpP_a 4@e::NM+<)zeQs.DPsD̟VϹ3\ qs.CPs;!f=B r4;y24SKa7`b , Vi0  endstream endobj 3992 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1857 /Filter /FlateDecode >> stream xڽM]5 +Mn8*$>$@b*|T!UU{^ğz9Jsb:eꔙ54q4OkpꝬQP$)>-QiSODJh 04QV/ l$8Nkb c-ImkgQ>vf17J9E`W݁j1wfoF5]c&io$[IID$}IF7k6CVGcTؘskESkiIYSb7mܡ:/q.`.Z`Cܷ>?PU<(L֢4i)EhZVOcx@k 2V䔙fkJ%*f Aș5`kO7H\Qj dƂУ ]_ͤUWK651EIE"T-ڤ* Eo[c5;0BR*|HE T0Y_iMXZa\VX&Zɰ@YYӚ(5d""W`۰:A/3^ĺbX`իn_}~~᯷?ܾz7^(CׯipkaΌ0yXWHNfez*~Jo.ݾI7y_UYL9QM;#j8ʩa^٭ggaGĩ!D@5;hC N!"f7Awlp͎ vnN> \C` 8&8 ̄%ClRzU xil{`1 v<ɟ!ACl=71. @vMBkX3wt,_Ky*V؎{.YH̪/qAn@37jݩpύpύb^Al-<7s#hs<7B~AQ\J*t}˳zD*DT ˩G/"K. OxD8Bqu#q\҆%YQ[Zw#1_$ȔOTL̄C3C1yBQBl=xʓː\'5WP( 9hv h^P([?n ʐA/3/"*OuV#g'qVCg'qVCg'qVBԲ!2e5Iϭ?z (CQZ;eP/PKgb& b&غ~z1^̄q/fB~A1G12\jpBtjC1D@.ٻXF,tpKp !< \.#PKgp !ΐ endstream endobj 4629 0 obj << /Length 2781 /Filter /FlateDecode >> stream x][oH~W䑕gZ6n%$(IAbgi{T!~.ld 0{HSD•0bGD]9b(Jƅ1[F&NXL^ŋnjߝ, |g [zЩNGj9BD O>Z " m)lORwXQ IK, qrW.B +HĤ{S\.ezxu-Cazr{` \xct֯ s"NuI_,, X.>c5ŸC]^X|GiNG.o^IET/ē@#A.GQjP w ZtLyE{YyE^0ay&5}1r~45)׿of߾Of "i" M_(Q"Cp30}s:|H4=%pﶧY{IzqBFeΜ o MrMH:)-*1;͟qd|~kI}ۈjMcx|P\ل-؃G:ƒ7 ck }lBtq[ҹRɅ[hSm"lW/!,*nցphʪ8Wl^kB`ƑTToWG[TJqD8`sMTIm,K74 D +пnK% !Bᖡ[uxTn,[VZy@ŸkE jaaN#z'x1 fcnpgS]O"r@` G`m~3Xܔ!nDNɞ l\r|?&Bt^F.$JK;\(e(KWKL $[\p(/آTf+(3ņz,vK==A=а[2'.S~mO>¸:Ѽ0W4ؙV9p-E Tѭ9 0,o`$A^y鸋I=1奇 k|JJ@GOK'  ]TE^ R4J5@*DX!\o ]dDC5NՀH0fz\RΒyoL8NtE B8xDjeA<\M"Q}U-7`EO}zS)NH)>гd7xTmc.2:EA`8+_T}(IKjU*0f?*mK 8L" @X,Rx[G{I@mq0BM⣯rT{q6jʙU`ݾNS]uIQ2z2#bXVMT ˉ 8ɧd:Ua9b $ʎH*^!3ve/IV;>JN]?c8G*f[EТ*"YTB x]X}rۛg9 endstream endobj 3993 0 obj << /Type /ObjStm /N 100 /First 1057 /Length 3404 /Filter /FlateDecode >> stream xڽM} -Z^`0I ۋ$f3mcp}Nc/`=O=WߑJ}Ǻe[{[l Ʒ@RwÖe |:~*b-QYDZQ͒W{HYH-H1eEz+:_T(ZǨ,fZhm#bkx ۘnKHP%߆ӥAsd̸.j]YHd5&{+tn.{ GGou+{ތ [!þ'yDe}R9[Q7ύlR6]|r6c(LqaΦ94K0gqsiÜMö1m s6}mΦ]k]meLG vXKZ0g3/[&9E$gXukz}L,cd1\cVs66&֜CҜKk.luӜ-rJ\lcɘ8X9s,PHT5k-gqNs<9lE}WM~JΖ+Lj-ZHRjӽXVlmۏYAi-b\/2J^?>,}˟~߿'{xMd{s_kW]u,wÙW;6}z?~?.}t*#,DC"?2_edf2$u4 g%HeƦs2N2ptDha4Y~b!m,x"|DUGf8S4 Ȝfh<2sAap9pfo(u[t9vbt[#B='fu}[3֧YUXmZl$D;OǵtY.hG4\'@ %!WtJB*g!{2+^IYN3͒ tirAss-_,?SOYjs~xË_?}}[>}K_%7D9?46й_d=~C^/_=~yCyƿ4C<}w>߫Ow/~G^S\|ͻ,O9p`ڟ e` A0( *ƠFFFFNNNNNTya 3AePY,T* BePY,TV*+JeRYTV*+FeQ٨lT6*FeS٩Tv*;NeS9T*ArP9T.T.T.T.T.T.T.T.T.T.TTTTTTTTTTTnTnTnTnTnTnTnTnTnTnTTTTTTTTTTƠ`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( A`P0( *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *AŠbP1T *1t$PAŠbP1T *AŠbP1T *AŠbP1T *A]1T *AŠbP1T *AŠbP1T * Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  A6T92 Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  Aàa0h4  A92 AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1t :AǠc1 ``00 ``00 ``00 ``00 ``00 ``00 ``00 ``00 ``00 ``00 ``00 ``00 r|s:6նuhG.oR:e.܇N]]N# %hg~X. A8}xCbw)sy#te8GHZYoL-i!tgyƹ8#OwBHi3?-}-Dv9y3/BxR?#D9*!C?c]qA-9j]ּ~g3?.blr~.yVe>/x떄دl7nAIp<Fy8C x0 q68LC y zB>/x^O:v^X7nO{{K:6س.%7W<8Bnp!7w:np qN3yG5dѪ?\@MV#kr_"$\:"gp,Iԑ,B\:"ӚE(lfm-}/.ڄxhO#\"iM4{C endstream endobj 4631 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1830 /Filter /FlateDecode >> stream xڽM]7 +l7?d@B[.tяB&tW*@ {Y~%JvPd.2ˠԛ +dsƀʀ\]ё|QrD0ʘ2ʜ3,`ĎJVGd~nZz"تbrG.*wb!Q3h󸮸XWa\GYfm꘹PRNBȥr'-RɯCq8E&. KbօGWB  |PLzq%GSRdfx|5^+`f @@#UEI|JxT-=`|Su층q]u5PQs2˨DXqZDU2 n-4.+ɂbĮ 6R4ײ\Q[+b7F׺Hb "vcq0&368Ca|ua8 Y5;IpT.x|D m`ĸ !!I!b H`nK2f,<\ qŐƵǵeX9ya-,7 !Fb2B2b |||Ó~?}.<e\~x?.??ɽ6kϡ{BF ÍLݧZpk.oï>ïݫWo6Doo_Lr7R|&"n(WDۂW2!F 0e҄ht@'b 3a4x DѣfF;c'3"&@( ?PN$$ 4pʐhwlQ UbcZ ;2C)B`ت֜t l_;J@ʙ e%1P*U(M: 7,cP* TB+J"%B̒҄H@MךfJeE R!fUiCR!fYiCrpS̾BdIpZ9T*M+QGpD@8;;b:R'D Dv*)z9^u>r칪kڄ8Q^+&D;P_+> le bH@Zb@@quK(^B\Od EдaBiC!4o@=!VmB%BhmAeV6[Ķ v3V-MxV--ssV/EOI[c"̍a#='u[msSan ak=DDj+{1agP X'! 4(6:6D,{O讍΂ n6: b6:67 a6:&,' ŷ>'3!;1NMLm1.Gfc3uܕarx Zə '"I\ܾ%su@7sgdeT*ڕ:'JC99A3$Nei0lMޚ7A5wϴ6-/fM P/ JΧ 6-|BмiBZ&ĉ9!V4!@TM&D=p z zbA~_zbBG! !׾*!]_\"^Sw*T.*֯L\*ʥ Σ- endstream endobj 4632 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1878 /Filter /FlateDecode >> stream xڽK%+7+lW5^̣i/DB_B* ݞЗR蜐2 R(Tkf5$LZAе[fq~!VAHGj,|:]A$i 몧Dl- Ţts}bp k#llҐsxB.eݢܓE>` u=BCxK?5`"k5d5fr r5͡bЇPY-P []QzM7\_i) ,<' m9qhx$kЊ' m>D(=W - 0x.kQZzbʡ 9 2XdARmA,Z=H.׽l1iftWsJ6q Z`H+JEJhPb ;& 懒 -eN)F(U :_"TTmD3rzEeQ5Q%7, .X!űn"`e)?Ėh7@cnäwK|FpbX-7OO1}~vo~_>~ ߷q~~vר%  C>}vWC9Pjɐtsp:zT*)@ˁ/&ċLC&ur q`BP.!Nsb*D9.+6m뿥" endstream endobj 4633 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1829 /Filter /FlateDecode >> stream xڽϋ\7 W^=It| 9y H -T\>@ݾ 51-a@:~i0J1@qEm$ #% n\!1nIո5hĜRގyl-d1OH3kX4N 9 i(؊Ѣ%OŴ9Q0n/ql> stream xڽK\7+L6j=J$3Y1,sJVifW/3V7[ߕJGB.8ʥ4KH]ݕVB׸J#:Nҧ&CN5.h.|~Vu\lI"b/r"wׂK1%iER\]ײK%h$rV\j}p[Er%Z.IRQrBI.Pu\ D 4?%* gI?i+!]rvL0WpAiUWJ+-H\LHycWCG1DiEW"sF+Jӗ|W\m2yk!XZݵXG?v-(bIfZA\,bv2An0=ѯ. Vw^KV {& 8RGDtűD:.45a>rL7i"t I拲d/rAH߀)CLAn#Cz}r5i"c̣/8&} ѢK:&d4Bt1ȫc@DŽh)qDFd߸"HW 9S/rhpa O~4>/o>]2_?\~.ϏrﰴD)|Hy/T| ^w}?}rW~v^]o'?˄@{̔1`)_ }lA"% ] "T6B QL)tPtCZ6U C$L72lʀZhCεYdA}SQvfDƸ h6ΑXJU3v^|vu !/d6 0g;2R))p!6ά$(6ւ(*XgbPUy1 }#DR ;!XMs͇)ZqC^捒}jrit}b]N!YP_g2Nי|): N!י):ᄯSL>A}QwNC-sZ,7O2WRzKާ[r*oP4TKKP4!TK bk7RT.M5<<,)ZAZvʈs'Cy2ҰP]ޚg ЕaB+C!teuP]&C?`$b ao320!#1!0!+E^% P#aBFbBZ 'RT.-rB.B҄r*&TKKryWKeP4!\N%O咘a_]A񝊿) B҄hR!T.-o\.K"riBp B҄/AbZM\S.M_w](Xir_6-dغΗM bl!M bl2!ъrh *y: Uɰs`c@J`@5E(PJa*> 6"ȁ0bꄍI46" QBnʝ8uuԲq^|MLOSK@ !SLSl:Ⳬ"x1"؆`"K.KD*gxB\RT--'pAB8pw!V '.JŠJi1?}T(-4Iۅ2i1ЁWq "yҙZZ|ZZ)?d PTyd8pR K KJX']+n&4F|F endstream endobj 4635 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 1868 /Filter /FlateDecode >> stream xڽK7 +l7>,! BR I X>t4P{ L<3z%a)0\H5PPFARF`PShCJ! aB΃0b]gX\-`TCtBny訇E j@9W@:Qu^+$3l4-zM `k|*=ܔPJU00+-tNրQ:g茍h<|yXX)Mu,/I?e)/#*Tɵ`qI.׼D.W^320BMQJZW*}>wPVi%:I:KY})غ&2V 6u џIViQCSRM=-;\ڥF Ԯy/ۦ>z=]Fu=lNNabNޔ[ԝR ;p5zTผT B)~sVJAg:+VaX˺$kUìkD=°FI=/Ly\r-kė{_DQӔ~v5`/n?כpwny:AOooݾzon?Cx]ŢVF9pMRi_/U}wu쯟+}^|ł^ yDXv!FHQ8F"51+ 16BEP9fezP[*F2 N1|4T*+T8jfQYZy06w, +-/ kojKu C;U ł1H_< Rd0t@_TuL:٠㓐CC)j! L\S >2a  ` aQBfAX!Bp_-Gwc9 ;\s*Q[y8PcJy.D? 0oxtp<. zUaV>_/U˰3ZfCPݦtKI=yNjRyR% b> ar1l͠&`rBCh3FdX=O;Rz@&_É4۵ @DLa.(% fO@ygȟ<%F..D٩H}8<eZ|&G{BXV#߳8Z{AZ\N.8ō!@c|1kz\1kz\MA̦c65=.hz&jz\v@.LԻ\f87u\ɥ ArB\ r@.҅ L.=ȥA\`r])φM40{s`Q!\ 6 ‚҅9|1Xwq.Cٟp>:FB|k X ]e|w^̇1}2 ˼?/4C]lgy/b-ՎFVyKyE]!ƁZfBe|@-a>āۀ1+ b$ bV.{YIì$|>PIJg* c1SX6jm> stream x]n8}W lTNwxQ춍[]-'l9dKYk*u%N1,rH ϙ2bN>y1{`(d u]<-&_N|ox/S9BvR,7kտ]GNǷIwꠅ‘`|Dђ+<i<SGV-MIt>wk\w!\.|,zr"}fq~懋~ymn TZ(GplT_C^1Daw{F{WƲFgr xMh EQ]P! DPM+H ecoۘ~>sq,h/~ Xf0Ք/wjZAא/Ű~uPviQ#R<+&mpx(ܵjѦ ) anhYuT?"Y:_a\IJ#HFu$+u(&tƖLpH1jvH1ȣe".pdt ;Hl/Еl#FT[v=(іtn6(IxÝׄ ڒr;@5^<JZ)Jc>6+Zl-wgכ؟.7 2]eD3VTpsݻ7EHc!жb zoꆺQDEtbʡ. wCF<? s5* Y[o Q?'JLq?V!ry! g/K+|Ldï)"Ç7@PP]XwLQt0jY|TioT"0QY,kBTg]X=-|h)J4P 뇁4>HmVCKk)@ّ sɐ%I|@;ۆn?CU&BeY%R`)|AagL$SKoo.8yci/#+K6{ʲ> c?t{bW.Y^ Y-**6ۤ}/>C<|P( ^GUrƋjCL{p U1ew21v0Mrq¿¡yERetzk1;q o6׳'3 endstream endobj 4636 0 obj << /Type /ObjStm /N 100 /First 1021 /Length 2751 /Filter /FlateDecode >> stream xڽo+l7|F$-`^5pH?﹣9d#G@PrFRhke oHfk1#1FV㣄w5lɢ;7Ek- YB6~BǒJ>P#R04"=QW\w%}4PeZi 5PJ}\jCnl0P[?HTw ~093~~Y|\+p#z1'Wzb#t|$l* ~@R9eo0Jm*aTbj='r`!FjIuS ӈ)2f\\U r E0nX=h2-l*ME69#[Q IrS\V6&410!d4k?ją\KCWjJP(7]\xߊ+[%LO.(śmsjq8Zu^&oМGhUNFhԷe/)O1ZCo1VhbI&FkwtL];W9o}1Zuz*[_{7~~ o\||ߛw~.! _/|.o?\~%kEb^"n|($ /^˛ppy-0 0[&DGbSsЄ`0aB[LPw%a 2yw?[4,kUZtKMy [hB$64[sm坰ꇉZ uaE$zx+L,VDmۉNT%֚DCJuʨ*1?(rEY@\bpʊP$Ã!-NMaHX@FW܉OKjif\fJDfqB\rfB q`\N=S 8!.iq93y}\raeJ$o"e}vzԟyQx.q4ғ2%=0.& q8rjb`dH{K< sRv%M0.&]m%'A qI˩zB\rjBNK`\NMo4qI˩?LlA!C?cHfX_~yίlO2U+[~ona>\^|.oo~ǛgkH~ٟ~x??vXdm9'+bv?c$7 Fgc*l(7;;;;;;;;;;BePY,T* BeRYTV*+JeR٨lT6*FeQ٨lFfQhlt6†ALLLLLLLLLLe"$EH!)BRHrrrrrrrrr22(dPȠA!B 2(dPȠA!B 2(dPȠA!B 2(dPȠA!B 2(dPȠA!B 2(dPȠA!B 2(dPȠA!B 2(dPȠA!B *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dPɠA%J *T2dȠA#F 42hdȠA#F 42hdȠA#F 42hdv߯gwH_hQX, go`1_aaIzxBUD_#x00351V Y@OX^]5:ң'R4z&0^s# %% uV׏}S_ɧP룇 4fV*r@aR?7Rk-alynb+i0Rg1jgÄs+<> +IcS Ss7qS&~NM 'Mu!-/TGS+_W)iLWU E\+c6{aH,Ǹoݴ> +C\,|]qyX`\NMq`\NMqIG\NM> stream xڽˎ\ Z&H *\`0ż}~U"E/6ڀ[%~)RHʁrF\6JchCdF g4Zhca3% UjKh'CraRLˁdj,ڒ@]fhhf#w{ ڢ(E:L0V 9'[ȥ~=di%oc6M @IG)pQ>v&#i.~2ZS%C> UyBviLAV 2TZU ]Ԥ&[2QFYףz4",zx]QWl5jjh /C)N L xClY0|YIK̙#Tzszj ՇX0Wp'<CXYQe~Ch] cQJ?w4Ϟ4X2` ~t(ऎAz B8遂? Hek DQ QN,UX>i_58LX s" 9C h-qϳ/h;2&tO͇wO!=DKQ Fn%V@**IcB6B< j u#B1ABCtKL9!Dj>D1rHq@9B&Œ3FGpq@[!>DP* "KD^!ƭ%v!P*d[;Df#7BTh6}0eؙ7Zʈ)M,VJ}T;EAQFXP1*R ;u (Y锃0v!0%(soRwޗ wI \9PUй @=g W=2 BK-E:PK9"Ёrs!Ɓr L&=BXBBJi.D= qI0h1VzAXR1TP*xQ*aP*C0 j9TaJB RR)fȔ .rR) qB ”ʅ:΃z5drIÒKNQuTZZ]GZwCء8|/VbkA.C}Nآ! Jcąy-آPC5z ;O=\s7 ao˜P5^Q4~j*h,h|YWAC͂ bk{4a QfA\14 ⥠qvޛZAƇBaf{"VrukOV J8:/+sz[o,-q^WtdڼIBrpR*ǒ=e6~pr1dL]"1\ /7ưҥpr1XN$Kc ,˕C_ e8p_ eDRR,~䌚.M% E%]9 `2B8W- b  L)]9 qIPh1Vz;X Q-r}%uW뭭qC&xvQ*YϞΚL4}UO1*|yS*GD B}r7wK‰,ox |XBxijAXp!ځaWpa 7<ߕ7 Al*ۅ8Pf--x)] ҅8 ҃riK.]_.ɥ jꛨa endstream endobj 4930 0 obj << /Type /ObjStm /N 100 /First 1014 /Length 2070 /Filter /FlateDecode >> stream xڽ=$+ډZK:aammplp,,8{KU7VΫ!V)r"hHj$ݣaɄQSŷhSOOTjtj%u}Cbap%{4QMUuZKLTYcKzIlĘ (Ή3ZxN121[j1$R[xx$ֶ~=I+ѯ$.stBc_GgD hJ1@_/Z@eQohQ2.^8r;2vLi5[hdnTKLSe lN%U9$rGj {8Ic< xdYjj[?X\)F&Ol' qID0(!cN0(>L1 [rRPA*4fÖ%lI+t:ahI[?MO,Xj]bKUdd'UArVTsG>gQo> q|n =P |+r!>"# L.bS çw@_PB<8ܥՇ4kw9 r.pac.pS]Br@ w918].pS+$A}NX5'"p"GQx*8ˠ h߆zHD <L=.zPMQ"J4Kb%#fKW_(>k\A#(B Ydڼ^ 8δ>~ *V: m8?X6!!gHhӆ@=O;Y*^L% ~B(vF' . bIzDp2yr/:cH${͝+bq0삘20>o5] KOCئ'T2.HOBAOȲ<@N˩KF!VJl=uɊr<˥+깝N+<>˥׎] ].-73 "> stream xZM5ϯ.ח˖V(Xa"(HyY;=\@Bj՗mRI*' A&-K&BMMM4NȦa4D`#]C/ (;2 H8˴s5$a-(b_b_ְ(`"vý@7 UfFlAhg a!3bb%ڹ30Ġ~6̨۬HK X T vY0gjZ*Z֑@x Di'вS#Z.r;FflVV$w?ϐ-ƇPW1I<~YA#6?/ )xC.02Um4!⦲B- uKp/D;{ńyhdҖ0MF2\9"Y{էy2_S'Tm`@jw9]0_fYZMTŵZ+:G Db U$M&*:լ%QD&pڥy̵Kٰ~ @k$e2"I2t%Ҁ0kӅ02N_3JyԍqQ8IQB.% E@ ̾Bp"(T3Weg;R+h+hWeHUSm,ECpdl0z# aA$~'$|On'`92Ē6AX2&>>E $b ,Q#^"K;2^ KGQKM o= B|1 |1n{έ ~nĿ^LWL_O?j~tÇI53{ X*(FT_~sC߰. ? endstream endobj 4944 0 obj << /Length1 2976 /Length2 21931 /Length3 0 /Length 23401 /Filter /FlateDecode >> stream xڜzP]۶%wwwwwn $'@Np}7*1ה1mMU(HDMn ,̼3GWG;7kvU tGAnf(4.֎당M@q7;` `aprXYx P62ԬL\pbN.֖Vnf4 CfN5+=@ :Àhg׃= 搅/ foFG%/SRPۻA՜hN5yk3+`t,@}%)@P)ހ_M rssebegՂD*=`nm0ZZ;1r 0ZL\ž,_??Ja`[]T\3E+:z| ,\\f7NMoC Gɛ;;@ӕ]g`6ߌѿec?Z{t~2a/.{&Iw;M!͟ ?B/#?UJo\ `ab K+;kqnemftu?H؛[;XX98&..&p̠efA@/Pl&FG7 TA_[`% qD#.o `xL#.fo`XLҿI7E@#Pt]7EWq+F*(o#E7q@\#HoZҁšy3(n9Km}abk76s ߌI *ߐ TsG_o  o ?r:wv {M^@Ųaa_ǎX:-S@Ev:YAmvA'0v9dz]1ZEvp7 \I|:aJ1( gg/?tݛrKf:ٹ H;_ko쿄OS? A?J[Pj@{ /M9q}+dcPsRܬ\LLn|^ P^\]5@a?$Wf.θKt@ nqь/̦!Nߓag_c5/@s).(lƶΑWI3uɣ3:kd!&ԑsN9I&<$+aϿ3Ad,F)gB_ 2'p,dY&G͢4Iע$s̑褫w_9PX%v*0- ˴[=,-}(Åtd jV& XDZ̠C6AJ5ϏM/xԌ"NLk%R7uȘ Ӈ#O;Kt䑁/Ly,B IcTːRl]ʎίZz uZ.Eڵxb$oFY^݁ Lj L+GS"B / u.jx}XcɝG4Fok'gX::" 0.g~Ə~i&}z|om;/EH~WSuzu0k9߿"yQnja jy׬0d#9BSFt3hr䃭 =}g=Dc t>n>$GU(*Z7mD Yd" Q7^eRɏ{ἣZMsëۨ-Il"̺»[ٻ;!(.{P}[pbK;5bbU_:wIl]P b? 8i'hcM3HMMOM>-,!] QlJ>g>:J8OĎY6_&/mol.m2{ sImëZ9ȯ\xx|_:It#+aBQlk#׸#bQXzo.U=8bZkRu C`֩Lz!.ڌxN2p jq$9tHZ  stWs$KЕbҔ>8JIgXIpi-.8\ wc}h]ΥⒽ6W:K{Qàu^Hl~Iĺk*ym1)\J+Ivx?kҟfuooGYzB+2kfwYr2-JH(yL=_p~5ϡZz.#cְj;$Z]s>X'fV9NNv([坡t4\|)GϱjLׅjbO uq&P/Ψw@~DGue/{`vHbZ9eHSX GZ -K5r+Mm]= m'UR|;W]E0QOͥH$)ЩX sz!p3EMBejZ? a>ΐ|!xDaDCU FRs Lz>Ӊt%V/HyHo7iH9.UvL @z:\P?n9:6@_(8lXj^f@3O@ 2/2uU@>H>nF?[ϰ`F쩢i(iUwz?\hv{) > Rk#jaCYhHfTNQ \w7ԥs{h[ a2iMhx%'/&a97۪hَ:YN).PK un|nOC3˹"`XޚJ8 T$AV?ĕxi*6wclj8``^)-SUg8@qKO [he?.' ډ4ܸDaQws8=WLJenM⮜-ɭ{$77-[ uIzzkΖI*~ħ^;7GX 3W9*V4Ŕ9b:oF&7yM~ 0yI2ެ?>Bճ3 ܇GFi366_, cy'H Q-| εh3,V`ʥ ~_FrCd㈋W7N"Eݐđ}5DP}IS$უq#r? ڮ?ù0:'L6:thcJϰ>p@eJ_xi ]]@ \QnAx?y%14: ˧ \e{j%gd&j>#-5+B]w"-I( 0nx "ѩ|;B 4 bze^<ۍ&jgN;,gnK)zN9ZرpQt c>!!g~+f.,o>["w볲Γ4)dʡسȧAg^' =tArH䎗'/ҠOb !էW,#%ôSgWd ޑ8?_ 'uݮ緶]< qУ?v !0ڋqj"ĝ~7V<vpoׯ@?1[=4Q6ˈ42Yar|fp %8L]`IF)2 ‚Sl6&Xu KKSZWxNN%z@ƪ` 6PZہ2#n.npKٖ@0fk`Fg]3DpuXI bnz^ ofr=أ/ 0nX/sRy|w(&_-Ė%~3*Qh[@wb<5.'-:(E*hك[bFltΖ: %)&6L22a`%e8-碷4_/ƍ |E?*LV9 cұXԅ9i#hI2'L*ivUL,oZ۔uxCY(Ymd ir*:lj?t٠̚ (uuy\X40Vi%/w67(ZG0نS_8mc,Od$)O>tR'J\?E͕me1@[ 6GM݄pq Yy2rt0F#9lЏ|x t11>c*㾆`uב4zLj_GM_wK^oiM.w6z`~iT]y N\U*F톀pom91|fu$+ | ,$9ף~$r$j0YeuPOzv$51kQ4o.^qσS h]xs.xh(!&ATwsq_sWLwZJ:)2$ u?s=1fPw>k"F6aSR]s]sg!>C6LYd? iJٗ*` OUU +۪On=ц?_U}Ft= 1s Z@岙­[pիƲkLx}Pktۙ.jS-FrM9iry`_v:/L]0#>5o9q +fxFWj} * 8pb9!(ݘ&ӥfK4\75(;=w/"M8u uʴ KjWrt$l» uÛ.ч'͹̛ӑlA&lZ>gZe g 9"+͌V%%*N FXq=o# P&Ǩ~z ,?nd$Mk9)<Иe0ϭ|g~zbIK@C? 4k3mjWh1,ߢIYA]es`TBȰ]-v>LWۿǘJA~sPRGl ͧ]qięߡrTAtw$0!N +::jD|& Bl':QnTSG\pb1Z&ëz&<X*Tc[ /7~U|xzBi!#D6w:z5 m֢/`cٸ|V \*- [V\ *WFRF' gP3Mg*= $ͤJZ:AYѧrB)T?y(`cFD^)ruఖ8]+ݰ3͡[N7%zi 1hz{m5,YÛ{Њ x ,Κ>g n=a_۬M 0*v!ಸe=DKӀŲȡK"+f) ]\Yk8X 4n}2pMg -lj:duX8Ls(: )ɖY>˓UM38QorfH3j-ׂ=Y&r]n^'HM[rӘb%-Jމ|qQvz377tPώa [`s= G d {~Vs%z'¤cE}L`jz(XS>̮RRmLuI݊P ^dLF%q) Ktx_ .5XO>TVڛ~Ww1\f%V% Ciu/<4Ao5 , MR@fʡ̹u.(s~jGVT+d[^&/*|[XA+q+T;=gԅ8 +,iu{C""ـpc YS[I̕'Ts㠑c+r#.~ݳP#훣Â#l!w>;%pYqkLEs '- (#StҐTVĬ^-d1bF3zzqe{3bP,b2Nav$ k8sr t/ pZno[r.1%/]Y[OLw 1Q[^wN;Fi{cv0ETאX3HJ`ks3+} jKZʔ52Y<黌3~]8S ,K e"X˅ŵ'v+%nbD4e^Ij㥼Mt`F Fel"DώEkj?Ry^}Bze8+u&%dQxuCKF.uü^cL 8 7(͟ݕn.z4;.063Ye ӡL9qk^;z]Wdѕ~:A&o|y놨ZBYdS¨Ž``99DOݾPuڎͥGyK~Kڷ^R r+QR)*ӪnYɆ2}2y:‡;52"j>Mo:/i$vґzp| iif9nQ|RϪd`~279ōڅesnIᬉa? ٘c!`6:py|;|v(4g>,8YFY0rּ#{Ut<@7`ApNiWIdOu|&U su>^p{BdTvd,X S= :_w9j^_ gؾ+]-c 3@AYbo+?\H A,a?~\$&qI>S\ Z@ޒ:hml.@H<}2:]cGEȢ1)C.ks O<ڹd<ϗ\!|@Oe"l RY7amR=_}pÈ;w[eDqX8 &]U%.;#od!RhΠķ$>k t"%4O-0)z>0LP1hGqy76rtG> vH5q;hP|qF(HZ(Rg:|Kb9E82-{mq0X>!ݍqpUz~j#e^Ḇ%n%~BdhvXuW\( ×})#νd2rSjɄI\ɹ^ˆWi}=aU7;BޛѩT1tzs6Rb*>싰A>`PY1B;xL% ?pDQ[yؒU4u!ļ=AvEW5[ҸOq3{ Y-߾*cAV"}EYCLN_djo\S՜vRw*4E+hQ:5?f#"dpe# Cwމ'7aUaw)?LQ4"L6rlynnb(`a0^d5 aWUpjM@n| ,]r",p9SnH/+`kP [= ؔbC$UȺiHD1x1'vűwWS3%We#>Ia}F-/WiUVZe[>>Z*jP!Q>g*XKLAv`jNT! ~ {ۀPWv|,MQB-udŻiQ3NASN b ?;[ dW~! `-1S-zvD`,川ɣ:d /d {ٺBs9n d mܲ)[ʪsgzuPw*&,lk<#gx容OZ,oj xˆ[OUP?K߾UlXQВ^Lg'״>3^p+p:rBs[N]t:a4w, Ѓ/=CDOc̚2GaπJ5y"uu TwXLT 븻+~8TRgpL)^|3jj]rK;\.W3c(K6E< ? w_uҡŏNº0D]0N"DIZۮm"Ri_Ȭ),=V c1RZ+Dg1DX`yD?]Mg]61 39rn :}^ec^)wU[c\f3Aqݜ7qxd}^-4o˶i (K:tEYfhLN/ˌw!mmnT,TrBM|c>]e ."`08H7KP̖1o{B~aCV|2ipӦithR=fK-FnZ\2bjnyc%9Ou3{T3᳇'uN T 9W:"sqv"T,3u(|}ŹUб9ڴ#>9 InG8f59ۇ)lK~לHf2>L pW؇s1@e߫Q\#itY@c9OM?,{}]Ivt8Ep ȳ☛0̮~{x 1-g 8fSy]I7KMMOnjxT\Q`J2AejKj>§`9\ i=wmBԧO3^xaV?Gn0SfSP]( ԮGWFu4;/YfJf7w{1ֽ@ uʾd'Β<2|IdrZ49_7bSfפrq!Vp^v5%s9ڇ|qJ6%wO5E6Qw}s 5N%rX7[:߈y?7 F;SyrPaT68*ϱV;E՘].Ezs FwkS4` $oE.t*eO}~Ez3rK[u]X_v}1(ya=+f% ߡ.74qbzLZ)EN}Y;$q;W_jw^i;leac<no_ԤŌ>{BgЁ>;J:GaWY1{>֮7dA؂Gɸ&P*Y$,i;lE~[})kvY½6<̨հ< o5UΚYݬ!] >pR%^M 7X(Ϙ+4'F*^i DapI<GBJOiu/U$StNq꾯vHNZܐbњgE6}-ܽC`G^QHGt4aӏDkcZ9n&:v9np;ڊ˔JR6BV e'5= 6]-g!muu ߳y?fs/j*-UD\" kFS3:R;u51jOBSk^joB}%a`yGs3l1G>c?p>!" }ѓ..yz=y9M>_$R[^be7v* ݦ}g_JExgZ$62۴S4z"ZG,^?-Fc/j>zOPOЩ@3$2n@vZ1YOBNU.ɋ~i^@x|eY*b~9QB 1*V.ӓ e}'aRt3mG'قYC1Sf)qE:p-Vīk+ow+)~f){ KH _xYqDI K`dL{M##ͦX3D= %Cr)D\ja*W2}᪆O3Ѣ-}Ly"XXHk<^ᨦ{T *zYb[B8%d#1eNA҆U|n1R9@kۼNe Y5/=3l1'-O_=܉#p,mwQfFu ek4\h{)#U~9olqrĄՏ?, Cd .F3S,hQO;`<'r&cKXxmwm?MCVDFeb-M9ZK\l)\f9=~Es1I-PK`ĩLdo F^cok! %lG%2ֱݙJAZQ)zl-);%Y۟ VF~LC<LJte7m4έ)!aoHCFmNNό?<ӫ&:q)n6LPɭ Z{)׃mϡՒ6qRW:+:SE*irJ/aZ_"1PTO_ Xldjk7GXZ8xdҷ9ۓfk[+Nrԝ'8ٱ_z ?=pٌZR)ac^ް]NߣD0=\z .TobZRx\#Pv%۪D}w9+k˵Q;YFDl~x7jJ=_Qc,2FFd="Ӂ{*X| |mO<8HA#YRTD|z -^cV7lY#S&pQJ]̕$wGTcc1ZC¥U̮k]ۙQح>.=OGd|y-WL lk"̏ yP(&8-Le [,d,-̑?E$F.'}yg$~"њO G1^m {e7ScUiۻ2TL~c,RSbo+vahйτ nܠ tə]VcU|!G׉J/JCkTQ_rX#,'&!w%?5%X6l>YDdH!TI"3rUԧ5'&v9f6\n5%.]ʽp-nqU8]+S9HoEg; 2"=.MZBaV\a ,A6D}PH=0>)B6׫ìWeR,r4˳+i[ۿF<ݫp5S'k9:u=N-!U.B7?F{ uxb1U.ݪvdfNYUNȟ&hELj,eX垹;J 5Pas)ҌNGUJ#wC}a6-uK(+Exf#aBS<c,*Gʇ##M3x'C&S Yh_s*Hlպn8SUH`.P\܆%ʹЖ16晙cԾLA5CS2#Qxy(K(cbX99#8"a)p|VoG "_DJD N kE߶kSZ%<[WNݰrgS#T+4Bt6"e\(Ә/!%0*8^[ȾӼ"FĂ@\&(enDZ3c[9nђdOzك'¨F#4̴P_F:k~ `HBnAU=*WM3$ ,TPqAǢ(xӜ_vmm/-0kwkM0)if<]7pgU*CϪ)xF\dž ֊Z*%h5__ ɨiNp걆R 5m{wi]ʽ'V_ rK]Zϼퟓٝ  ve _d([ azȚxf:?6֤!t)3=U۩ςc&eN>bO)+WJhϿ4u,)s1ԥW߶4i8q8b{4,= &[?i> j2'{Q `.Oľf;Ȁ溜iP{@ &E<}+|1h+ԧEu3GQ AKf9rdu Z\TGfTAM4:Cjsà=TNH5Bf$-6M{QE';wsOS>H^Tl P}Vo:!{B`'/h^JGɲYI\ذS0UomWWul1uy@7Ox 0 Wb/wYڛtprf@/71hpAk){!G -ݒ(Sn1)k"Y G~y;6ld`=%&< f)'^b\:n!3ue)[,{sMs^('u,5֋kt|gG!A|sj1%ƑcF#RۇPXf1e ΐ4\*JMcA`%U ?rcM"2YU\l!T/ 5#yKM\Ss+Ɉ2[ƛUZt_1a#@bgS,q54_^E՞>ChklUW[eҹ )P3';Cg'K}uEͲ@-p\iz9׭4*Dj*ϰ<00^1V:8+0"NccK\O).'3%?cjuHH@j zaIJ9i7ay8LJ w<}f9_RJ%Lm˹|NܙG@NCzc9AFΧ%Q'[/^,%UG9p\X2/`B ሩ:7]Ae|:hah5^ƽyygGT)Xh;U } =|␆Q{~::RtjMςae"Cxn=NjGLu0m̐QuB0KcPP6ђOut9{ W5:w e;|4F8I뒉|87؇<7uufޜ/mqJ,yX(ݒ`LՐK&q/R@Ɲw<*[sRfYsT.$ Qڝ_ ƃ?l^> m`M]qSe0as x_AQ*$bmgӵOH\@@6NH=5&- ./_/\.x\mIР&'g몤M͇~vy3ck|sۙkC[Q!5n/!2weqs/Y~.po,p݉4l|+\& l%0,="| uj~x$5vMxdy>d?FMo$$uv8MA6f* t߮im!F#vu~# H~yD-*x_$~0055d-#iJiJ'A22G*ܒY?"gفSUul#+GLO8E/)ThYq Vl {)@]*[^J] NzaWnPȉ"a(:NnCB ^9 VeJa.aP_eU\mk'Feocyb"oQxuu[T!(VëK9p75` w.` KY/usD5dBPu, ,U4􋛱̏l˂]"-yA7'Cl螕 Z;A-U`Y` 젇şR F3lў dl/,,hwz`S6K?J^n?;{ω6(u 2^]{)EQ ` W჻Z1kުײ-!O>g|S]D\= ;,l\}y.Jğ9]!w/2N'TWkA8qVA4YآViicvImKYm,+C BwTrg2 [x")Ff6)T B^-׷-%Œc<)o;6l n~ hoc'Z}tOrnRJRTRxqJ35)9Zc jD^m7Z3p( $4L⩭oeFa0$ TL ~C@/ 9x&RyrmHⓡ䳸w)O%S痆~]Ȯ S?xWnY?k1+*DwSk< `#Sw^P/ y+mP०p|Lhȁ̏('ǩC=(D-EVzTer&$Nm}$h+֒FNlAPٽfZjK^q)CEI4)_u|Xz\v ҶzN"k/ݼ#{|^LByً\mhTUCKS{wꓒmU0Z7wdwN\dr^12W¡1G2tIȩٞA ߢVh F>ʘWIJf-ǐkJxO̪ZXaWϛl?)lqgIv3ʖ`ԋ☬C1`q~ZSGM|;0~JX k/e0k`B̽?5SSE9L#IL|ˊ.' epè +Ģ>`jTљ2\qZ- z$P&3F{q>䪋S O Ƶ X )YK.`4+ 9/lj~!쳤Ove bjXbw#$=(u˸0M}Npm ߳y8*aH"@brsC`eYjM*Si3t5l^$v*:!NJw<8$]ͧ+K( \.b]Ȑ00մ5S ZIBR ?5Z/ڶ"hZ.JOef׶O|ٙk-v6TjQC[.AY@ ٽeyN'Ŗ3I'YeW љC`Bx_i vV ݠ.'8Sa*]fבLPbARb{j'W|̢;U<)~,wxˮv3|Ȼ e1@vzZzՇxcjC|{o6bAz ʞD|ŀŒ@caդ">m lV1˦vhw#^E"> stream xڍxTSۺ5Ҥ#H7 & wAjHB$t^7J](]zQA^x}kk͹d30T`($F$[ PT!4c$f04 T,PD@4HBRQU C!ahN% III(<0 8ܰ!`0H#K {{{ B('y^7 0a^0(=hB$g8/1 C!H(0Ðul$W?ѿ#p #H/ Fa^`8n PW2 cBh8׌¿`Y UA4ɯT0v}+{GBt6Ex´T`&ۜ`PJ\\ =| ¿ ~;31`pG 0@tsEps#Ik9ƞ`0( 7 iݷ43(@PJ@ 1@?X-# W}e?#^?s顰̅xMtk;_YWwGo?_v#| `UjPs_ՅAn€jPB:a-+Vp /e77 3@0( |XA\w4]0YW AAMDL`|~ ,Da!쌁GɯؙhW98rLV{[0 B2?Ȅ8UbP欁gՈ" zX]tQeg: MqDmLПg'Dl* XG.d44Zxzl.˞#wN+-n"7Z^w D8N$Ytfom%7k2SiCu&'NwiW`O4(4zgGl)ð {x1)QMmX㸅ȣc7RՙݵwۍF=UsRպ\RfAd'dPYcBA{hۊQK,Uw ^4mu gxš? D?|p{jn+Aݥң"ę7Ej:"v"7[Q$[>S 7;<Qdnef&NJ[DVҡ5r=gUw8(BJ3{9Πsuwo!!|_mTEQkWM%i݈{1:O;̴LVAOE;747LE?!һ$}MaR4͕zWd'~ 3C?~ՖSv[&-Nn䃼@jie5{左[F׽Ts UIȧFr):]JZY4%P!M?WșhϏ$ءaSzGQ4cQ˚]WV?X[t8 4"Se =y<#0lZp\7.E{:pU"U^hzzIǶHaITX>oxYPb'yq)F~Oi7&lT?ˮge(l~90qV9]\|>\*Zdxv]W}[?+gM)e Pjo}q}G.Aj`{ƴ5=G3WC*IDzZ3+W- u˳m7fHqw0LgJ+hR7RI[<]6C3WILggdgltyͱJR%5j0[0r'm>8i(s>{meǏlp|in|;ԙvgn]I0S? !0j)n-R}E:/!#G㨛U9:o۴?5f>b?^\sNMܥb=!ڌ8wnc\6΂'2,Uϼr`}Ʀk^%]q[9NJ [x;N&"- 5z.6B<{5B޾K~'\}BЄeG4lz}]g$-!JXo*T2.?`gl`)V !d~oѣnW?wݑH ]@ O7}oz]y)1X R|[727r4UE]zaEi-U'U7yYhc-b0kx'8tx.Dѳkx%{@! f njuɁby蕋Iv|Ho J8 3$%ͽl˾&wIbpa[rfR cG(]S6!bs~P^Ξ}<ѐ&A$㰓[v²s&>'+Su oR!Oωm") gK[A!ţըC~moC| [P輱:Rǯ.n"cd67wK6Ù_'Sp|,F|a.2))9 \++ĺ| ,"bBnUhME3ƢQ/~;XT悔 MqwQ,;[П!%7QM9J0XHtvdK.8JpS\dYiہQļ J)N|[!=͚QbY%F~=Q?cґF՛^gl᦭*Ҫd_-Ei;·'Mc]L]ecgz z 6R kSHXܕj^TQ J̐e4>c V/cbje`rbqؙaΌ O`kn_EkV2BDKW i7Y͎rK%ȑ/ɷkhԵW{|Czn,)v_-vwı{ e yѼ5OR d;, ]kA\8]vn>&אY8Ca"r7q֚啢s;<5 Ll@.Or%Ռǣ==+䂓6sS/n2~ }URڈV0fo0pj22fm˨@.g^pdt,Pb쎆DY0g+*mռ?sngS~)nFXN`fLe鳨N}t2m `^uyu'cS]0 `%O)Ĕ J(RK0)a䫌  "MO-5Y@+횃-aF $O8fh1*N>niȩ.38Ep:Z=g\P_kn+:Xh߄oqʑxXv:#-"]SY 4{r#}1E(BuY0ՊcyOB4/rky8H»rCo 27n'EPf^X|;8Ԃ&Q`YKFY4@F3nfyXܤE)b /c=u1r5|!*x]m:1LJukgsC:!a\ ݅xVfO^z3z:G/NT+t kNQg7ʯ62OWNm7w|PlU((?=$F_d2R^_EU\UE"||wp_*IA؅ӊ)AĨq\ݱD?jTI?"+!r S ;/B،1ПKfv#{POlduk"'r OP5KֺAyY9XbiD*NQz)hrM3Sv{COEW=U#sSc/$.gK!Aj Cb%\cV 1B&m.T 2@"fUR_B>kqQy'E w؋,%t=/齗AA]ޣߑRFɓfab<Șp[Ci$q6qnyQ 7(%CYFXfr9bR3ȓPW@яPHVrJU͋7p,lk_*Oh}'yIk|N-LKR}şua sjR8Ė8w_noUmNf S`{*js,W|ƩI)i"flvX=5S]j}1w,oPN5b* ]*"KzKM%)։u.MCI.LDb#P3pAk˪kSE]u.z_|>M`qX>u"9=zڳaz s}%p^5`,hoN~Jxd~;B jwgTFCVclSd,iRоTsIXa-s*:EG-t>ğJX"[ss=d_SK hǧ'y~{j2K` ÍexlTI&yʞZԁ~᪸ nUmV}BWQ9MD`Ͼqn /ο`i$TעKr3ݬk-=mxA] Hb`#b\ ^y)Dgw06|bNmP`f&2E%{ E{S0d3)Fy!Pש݆mO/O&h@*-.>͍$lmKPYg5PCk-Ǧ *\Z&_&FLX?o-X=8~8 .+"=`Yδߜ7W@Ce+37q㼮Tw;?Fz0| /|;ܘ:o) Ds =K-a鴨\gWE > stream xuSyQa"AXHx\dDg"B+1+|&WY#]AĆ#t rt&TA>Z4s:¢gBvP#X4L,SB ]3i̜!>@͝[q?,fδ6Ptw'alPXp+c62@gH4Lx`Ѹp;џb B;E`B !@5|SGa5 V ku^(o>H0fn_T06x)"o1WB;Blľ  îWALd3Ep?5wO-47˝dq\xӽsiiWsYw! 10uL 2)5,fμ87 `px.1"`P @7C0sN0aB0 Q̯4xf.=eςAp+P/AIg'ϐc0nYXm,Zn+t^fD6r)m`9o9L{c" j湥i0=gCT~Ф5EkcϝWFWO;T&#񺓛Qz|%1͏(u#%[҅S.x^Ѡ[ꨂJvU}E*&6޼d(۴dzt̬]ӣ뫻5S^ّX}Dkm60dx0t~zli^Kɚv󶞆{k'֩#%ILf=?x$6wjVurhu(237k<]iu4Mтָ'" ^&?S^PZo#fn=q-ޞ'IS 6Ɖg'v5+:+E-%F#/7삯O$1w_H\W8PAݓҨ@BT9>2hZJ?U7[qf*L&\꺪#oXl-Aih\Fѹw)}ʭDءx5{b 2+: M%w:~uxe[ؤ=j*/ާ z:V]q[e"Y)sa@&YDtd[~Lwp[:eMY1uX|ƹڪ~9qluL,a$+o[{$mr>[4|x~p7>Qi\XZT< 0\8e@<2}llDUޭ\Q=D-)p#1ve9k|U\3)J)}AؾގWuЉ<گ4kli3[}!FW7=81&A[%E R9etI犓%?Hd)g֍{}:drވ>~s@ҞhReQ? {#nq69WxKKԇn7r겜p=*VmI.xu$ #c|?M>ՙe:Y`{Yt2C eͺiۍ{6i8U捞5 K֭^]%+ ڍ#VE\~E"Pk~%lLs+ęyoj UVHF`iͶ8QO 6kKZ$M sSC] ąhv~B1Ja:`:>LcKRa-4&w([nR(UK}5*a㧬'R4>o R:`4V̷(2語rnxjo \s͓T҅ اPPhy`#qRãvEjA fR[SiNuC%eNy՝թsG9޷h{cdE>!Gm,)hi|-M7Q21dՈDZêhEm 쩒\h endstream endobj 4950 0 obj << /Length1 1626 /Length2 13710 /Length3 0 /Length 14558 /Filter /FlateDecode >> stream xڭwUT]-]7-H%;l=!]tqnߗaY55w#[cQ[  #3@QZ֖[A!瀧r0yjFacC++ dk`njP(S ?56ʏgc+[;kcG1hf 012kHȊdUb6Vy'+sC1 `?b}w ?܌] R?S}GsC+'|Mld`aa&ot4t0> 'LWnG5鯒}m@cW_ FvVn?9 ƦFVƎa>b՝ oYma0:[0³~4~65gkV$lLl,9Q534 lmF&Lˌ> [Gr.}ТNVVX26=h/}ks+ӿZѿ$-ncA 3#?探F@C3G;XwK ,S637mUgWUU߆CTv0/\6v @,<]Zu3]<ez/UAZ 1/tRi0"z~`CBPEO_18=~[,^LNoNq\0\'6]nI@'#狣XD2T`٩Ť,LP6hވ ]PVZǰ # Gx)ԣ -e6!s׽!9W.Yq6Jpr$W GNwǁ(u｡*]FCJ%Ic >W0{{g)Q¸/Yi`xqk{E/뽗,]?Zi z\gQOs@=*_1.r`f ,gs~[%^@>p Ke@֞ wW- kcobi/y@Yd`Yb|flA.sgzw|sMɾaFgZkO*U /vDdzz?Daǚڏr~ 'Ov=: o-8Fd]|]h?[S4*B޽8ez׭Tc^]vYX2џA0ol6o%Z-e4J}'9'ggx Z1'گ-)B#Ff\ۓdxת , L.$Rx țc"eh ݒ8/ ^)R4 {J+w3{|<uN=” RߺR% ̣SkZ!B#hlݲO 1ؒ\yGHYrbwFJ"ǦIfp4n8CԸY8sڭU ΁hjG`;LKeaET<tJg_,\R/SǗ +v" H\MbSEz9 7utӉS EpUd423tU&:  /v[m%<@?ȊɵJvd5BL*q-sf1$)LM^bǹ|鳼Z櫲{ Qɕk}~Vb`5vP;feL[>σK=כ7\ttKi|$Qspg}.0smGlB\ ;5vUR)j¶htiqhZ"MQ$R(msĵ7'2%oD s?Q;pZFUt YC.Z 1ͬ ALfKHg""ZhȴQ1I,XfL!dg }޺iM'3z!؏?g{163ߝ"N'= l%M$bIjϛqfChntjBAh? X^Cy@, PY{w# OYk%Ot'hX#b}sYg}HTVlaiWMƦyRS@J+@rb3"wִx ~yuq{ڙ/ʞu'EudՙU,.#&/ռ{V DSPE՚yl~0T\B_<=+2]V#Ik6F>ˈL^-b'[w7>7"-ntTkg}gljmJIM,Ó=R{Ww',~&^x%Oͤ)&926- ԯp]CԠ/suK6?LD0k' u"IɹIx$vk$.@S='"WǤ~zhٝޜ~O[$sUI3lZCSa,n[[̈́MZ< er_I,EzJۑ"\HTi"8: %a5@h=)63fLcAʰXÍMh4ȣ Y!fjIP췖2,kNSlP.8Hh%=:4ISοg%{JyկRSmmDk TapӥKUYDj% wB )g'aAKL3R-Q W2Th*[XV_#yE'q|Qݫt>o_+g%4q9a%t®`T|S7EȺ?c5s&* x]d!ɛ  {_m"DS+-5rj)CR]YXAW0g| fyӂ:~O dcrDS&i _Yk0#Ze4_*&tRސNeKx}5KKJZkF\gb>><ܼ}THzӁy0i'R{Hz;F ISiʸƒJ =3ݶyb 녟8kY2;!be #mv(4+TP[.`8صKr J#9N6U% Hx ZJ!3 `w*L653u͙'8ʗT;9_=Ӹp2Z |'#i0j26)'Tz&(DG>|"{B=l؍cJ7J}&hخv~|FwX%"؏xP55}7&.Gah΁xQ:"nѪ]IerjgF('Irbz&/"d-7m_m'h"qO&^‹dP^l\ROȰߒp+|o;? _^Q1Fkw~7kIH$xb4@RډȦ_w+c4f;QDQ-ocĻw ݕ-EېukE{ .kgsNDŽIɶvsjj_d^˨P'G^)9aT .A?|X} jkt\  kNx!4jfط_8\ uz)!#:NfcBc/}i- z6C<y5ǿYc 1 Dq=DÐ?`6rqgMWmlΑ@?w?R6Z4H)wsIUcn9EY"F~g`g]]G4!*FsRYW6?'|*5_1Upvr)"[\,X7GN7xl f? AbDihIlqsLa>RHtqqf[3UYH7ntPiulҖ.8'%D:'ۡК)dA:4sd)`YIA ]Z$rsaX"nBEy4%up&b6yF [V9Wz_ =-sEnIYg!fY+W? 8]ԥ>*%ImV2'vU,)U^W}j0A_Am JPɝ(ڠIjbɈ+X|UL&mMP섛3.VR笇 J 8:I9;4tL<걼A5x05! D\I<3EVƴѾfm+7}GJ3nh~ndE=1i>VN#tFYy~l e&b-㇬2EX8*R,ko//~_$ꑴ7GAAsٟ 3 #%|5 Łfa@/1 klF ʔ ?8 = j#=D ^i#Dv6eY؅WՂo¡3.L;YEHS%\3 re8°JG v7Ï|ʫdcaqy ѧj)ݜ NKK k 09SjzG//Ic9=V||n;,q== 0f{<&3VN-.1>'pjsX#НK.S3wb J1v93ZZR+nT>d2jٺRf56Em6s m6=⯖cH5*M*{|-#Kzv# -Җ!'aXCdo83$nE4%s>MtQ<7)i N\F0AqAH`RG};(U_OϑE[Vtа,r?j@-m|sLH!Oj_OG֡P"Q)PiIw2y>rr+%*0^^|.4[y8 :R&3QY:NFKvˬ+a-g#0;8Z^'3F>K9dsfv$%ǼnED-ATiXjzKvֲ#٭bLֻ1IɃa?Y.Aށ -a{vĢ‰%xdOd/2 a<8J +VX⹄[>|3)cGS9i(;$6ŷyQOZQGqtܒV[U&V"0uv~:< ! _K^CsOBܧXjcLT߆rܧs&hPP]4߉cw+k6J_MĪ'?С!$MT$=&yD-}57,nWdH:T`pǐWftڽ!AYj+@ܙG!2t‹<4 %aQ:! WjV?:6q% UM'9aǎTB~4] eCH 篴qC-+"YD4c*yP1ǩVKh{þ˨EeF/Yը-v{ eLvږ]#F9O[.m nb Ŧz1e.{OfĤn߉Du&W^'d(ǽ &'~RE[QPuUq/5 ,+Ƅg~/G ?s]RNҗ #&u'/uNj)O(o Ai(2 ed?lf]-,NOf mY"wLf9k>2&h!-Gl<oI=~ȧ1I(~u13s|Ǩ}y`=[(a 2H#m:Gv뛖pQN 7~E)"i~۫q1,*s;Pu+* %Pw~g7GD.^r΋kF%QnC 9EHZ(Df~Zv1'Id׬Kv3s-L1Fچ={yWơ%aTDYGJdA ʤ!mz#jΰ-S,3h]*>ů~S߉z\[Su';?$CXY-AxF3z# `>UrgkH/yWK2 {{Y٣L?_Hy a^ G,MtN'Ȩ:=~!e0nG İ%8 MWW%4[*BfK#m=XYR~윏#LlJyKl|r|?ºl&#7S ZLod;P@tDfDLةp7v&!l ӄQ뀇us.Ƃ-|dbB`ҽ?K4S$AxC&-MxRiIch1-6AOnua՝_etɯshPQw0Xc.=={s_Uvqu*v-<[툧O/g2GbXpýʮ vPPCFϲAyʸ #}NQ٩ ~ELmGX :Q vYg5x64͉ u!r XI^ r/;jIkʂ &սQx?z>!=bp`ިdM\_8`W WBqL5J=. 1">³:(++m8;[ܲ[  1y]42sy'leXD 6 'b5j0O,]nIYL-~]?<{vzT uB{4"I.Ydښ*^)o&XiI~,/?f(?OgQ O@Y949rx8]e>p`C<)㣎!F;G/7P4<ϝק}R[37DYE4byidŔm=j+ aLk.M y#*"Ԝ}+8*]i%})wZ+waMƎ5?0v3Vȟ ̬$RW[/^hZ>zlBZ9ڴ9G/[N=ilYnLQB }_GjYX_-Dם vJj!X1{_Iz5  Z? j,$6%he_$ЮW/}G["sdhzMVd oÂ`Ǵ/TZ8L@\i\uܣYȅ\E5GNDKjeWG)vtaDܱz2i1<˿k2XR4K}a^~o*]4P̋`*kL//w & +\Dt}"p/Ip=8kv9|8vFza#cD2VAgxÕI&>R!8uG?,4-Z% %0B}sfoꅊ84[K  7rj^By$Fe{0Lk#$WkUdDW!աϡ۔D &$s4 >!k>s,5[rר:Ů OKqݰ(~[Vw4ʐ)jq-r ~Wl}#$rS\%:WH;E\eMa3OV%-4c#FGBN` 78xxKa7GW(A!Xp7a瘘yf7?#^hT,Q'43sk:iN)bTY41=.+]]1foT_qe<)GHHaiS(mݫ8 YD0ƼoB XվR\`辢xX&uD vި֡yWf |c䢟fnBTavZ4]|1]U w9=_74X V̗H2&$C *M!bˡU+Vq\Afڹ[Hλ JʗQ0޺3B%²|=6@K> stream xڬeT%; nEpwwwww/(Cpo>}z1es\*r%Uza3ޅ`mgSqѫ[E̍]Ab.<Ms3)͍@9x:Y[ZU4iiS ?,#-?́ ;s{ׁ+s5 - TPHۛ;J&@kS95[ͬi͙/3`nj77`dlw. )-@* /7Ŀt2v'_3d dOKku1w{`f4/pu NNf@sg0 _7vpz+/Y9ЂoNS-i{ z3W;k@T "@@OoJ }$7PB oWG++`lw}c=94@c_5_5]LX-Rowfҫۛ;r虙Mm27_3jio.G7 )#"x3spYqoR ?eyc'k߾_`MAfm̦NNI{sssSe)oMzVKvn/3pÏF€Pz.w[m(C4Gҩ h/'m(rƙfբޤA t#u[aW?ӴxN&03ᡞ?}~)$.FNw/nUK٭5hI^ˮdqDLB&aq,ʼnt3j2g =ՒfZCR %r9bvvaen_ X-wZb_n/5a@GZ+ @+A^<$*W?^ٳ:{Xc{oX +2}- TCハ) ջo;;/[ YThEYM7b6c&߆_X}-%Z'[|:uk7GC -.;GI3 bX/?{.,0ђ( _*˽xMSWgا*Yԙ99x 7 ĿKe5NS:b2ol6eBBEFֱӲ֌93fEwyh*u8e@CGyNRr /̧OH]v Жr5I*"|)eaڜC 3^/ޯuvlh.^#GW4[:.) ]zo\t5@sSպ0]vѮ&yNY==O;~ջ#Zk'$֛ah*k4Zh[6Χ1-i]2_ʝrq2@(#8OTe!w{rn=äcpj2m;#u'eS2Y:Qi24Ke]+&5!&|kJ{_1kǡΨi>ˠ6B+J0mbÈ}hJ{;ۼK>i%Ia&K(5goJMZz dkh6B9iՑ߶$}ҍɫTR|u[nYlB»t3e][õ4= R $'1 ּOGXUW8!B u^E|6Č #[/m ok$Zm6d{ɀ061C?N6 %w ʨ5 Y~Q%=XZHKb Wqp _&9* Ԡز>D3K$0 %0KZKG}.LD4nn4$vxYh.Ě:8<=#% 8B0nlN&UӁ9M!*2;ȌAIRw8,`U:3-X##;s 9/_+;`3]Cu *m)8J濾{WJܩnUgIvu%ٯGʬFؓ"Müjx)Ko9 y#8Cܤoezü5A|MsdW+|A}X* *OPYڃMOҵ6$NlZ_q-,>d/o>r?0Iw)r':={7Z~i7e}m(]X6t,=y!%V:)x 5/)L+q"/(d[ՏiGiMoY {^GQT䦘fd \L@XxqnȭyV\ǣfԟ& Ujf8Xn@$Q=omh e҂?D4j\9RrPW\1k_|9A(/KбFze! ® }!Wf`G$ b[OȊGĉ?S+Փ4LKZ5"Y͌IEOrE~}|xd_hIRؓҩNk@ED O-}-9[ H<8o8un1L4/CU- k38'EC%m-gD{Pr?58LQK~:4ÿ9dMHGl_;?yPt?pcwbyjҽPbaB~'/pEElPU' o#hd/.1OU;A@Gp'4 SYQkˍ*7Rb&" dE 3QsS$jFێu0C!4Yu) 8. R8k֟f/Vgϵ-0T(WUr#%WWsώjʾޮ~}bٹ}p}ngl|1j&] g6Nu%sN [^C3Jn~dzֻT(@P ף NPcO~uk U _ZwaQ9| zˤ07CIf䄍,N%l~8o",[{A!ufW`$$uV5.:L>u͑7E, D<}㱩k2|j$rӤAK#Akn~tETQ!d\km;bxD 9 @*OYQ7jK/88GUb+GB@/mKt*\)#2dewHVk+3QX3Eã^KRNjEMݾD!lBaAMݝmUB͹9 F {mIx~yo'ŬV7֔,0nN}k_AV\,FdV{wc7/A4Cz^LV{\=V^x~F8DLMܠt;.7XV/EKかR]%?M$xZ3=91x_j=,8mZ_wp=Xڑ9"_x]\1G~:1ɏkYg?`9?ׇS SbPeu{$=Ke+0^$ ݦo&9JkV Q$UQ2r~rPt6q<5zND !u~IlFc VAaAꬨ=Q_X^oq7ԉֆKn.DnPZ DE :4*>WmN? ނ;EӬJo_r]d˩v Ί$zb?R7WRg/HU.Dx Kiu8je\$zC21N|ddhHƷ z?SgT2.l~0*lh]xZN.9;gɜrf\ƴ/Lm.wD# ʆ8jɑMܓkK&(+}+Y_ XINJrkR+h ӔE ~j4ja;5E`D1ؚ?kLoinT7Ш5Ȳf|_@ \MYzf4hh~ˡ.CG.5w,vP"xù6#}á8o(ꖭ=:uȗC"ղ2t (7tKuO(Z*`өM~ҵhv^V/4טFXah)3p~_Cwÿ<6)J_B݅F.zbY%sT$[QdWV7VT%J<ȯ?j? S1#iaͪ Ɍ^}h;U|OH\5h#mN[$Rn6)r0'uxwOUw'K4QW78"gT)]Uf?\jPeET{^Z&`6NZPf jN{;Apw X'a2t7$}p7GzCPV ]׵/)Arsym,w%Wb/:{{SZEK 2 1rU&h( ->Ѽ ]Fmڂui:(z^ss!dyaq1'&IHȳpƘr(Й֞]/2 qyhHJjTU}*ݣbTЕK@R a}40ThUן%&WL扂"xVJ2]AUB|QQ;ՈM;ӑk+ XO1L ċ0Etr*No͉Vk0Ԣqwo\Ҝ_¾] B"ćֈl+?(cT")v%'Vd76C?AY%њC׾T(wUrQ$DfK߸N&hrXз11T Kx*j&J'nr GXFN{c30Y2[ќ}<*DHVI%wLw y# 203t=] XsVKq)e5Uعlr26|}AR`N{ѝl$_/=A`$o؟  p*KE#*47-cީsŗ8sJ|-MP*\Gf> u`K7Fn5]7}HS %rӥgX7,ߝ]X>Qe1Rmf#D\k@ \WxR%s?-;4=WVz2GD;;uYdHz𻖽j2/Cpi#+]|a,/66`}Ĕw(v"L>/j̇6qkW($#I⧱hm/ 9R=IcQmc*fcMeY3ąMnwvtks?W[FMJ-2~[a^`IJwsm'CGFY|GWyj|_v~igO^qTpHme<^1z?iE;*X"Qe$w8*i]u0ZY>5`ZN!䃕lpF3X\%"H9GvFH|LM-Oi0N-lfjA3qL V:腥^KX_d}d-"C\GgpmY ꎴ9w6X=]:FׄqAi1fSw)XrԘbJ>LV›^́s @)~fr K(_yAsr阭"R *̛\MT }lʘ0|M\BhӛN\} Ȍ-+H*ﳵN'`* V.dZ3~tT ʥ]Ly2+N"wMڔ!5샳@d8vlx/mpCY=Sw l \QNQ</|o ׫Pfmz1♲Ԏդ׳6c|52Vȅ%y v2dC({r/!}nw9izUeHbܓǘUh #O0[Dm#;dlq=+7Aރ4C$Tg:aE0 ;J^Z4VvQPR'zHeX$zꅀ}ct687̐V䨿  BS}J+z T[P_ |&t->sLR"ҜoŞE"(+vk~Ii(T.L;etX0_ɐ=Qͼ@7&0p=$k!fFwzެNbר|2 k=&xk 3WU>C}Y#ay^I ȝ7gʦG# gۡÑH{GPJC|oBH,z}ɞ \ f^@VG* t vk!gN-y~!=*4ї@s ^}I/4 ML (,hke!~;^SQ&$\R_p?yL NGr4,^mw9+K\T!޷e}o_C_ tQ>aTUߒ`N9wccǧY_ԗG(-1CC5'F ۪2["ZpRU;kʡP$ŧO2Q:Jt*QvY2А7u}H"<2 -I- 4TЕ@+)mcВC.Ax?'l6x00Z1XLL$+Pqji*LuM$D|-8rX,MTvSO )wg\ .`- _ jS-%APi~6.` r˘}aV=:oim#zʾ!*EN{ 6˓V ŝSkO QLkMLl_9@増k\|ri,Zt :nG 뙔,]|F[W U; c, wd( /?F i) N9dQbKtxs9'/^ã[Nв"^, q=qZXO~L|_C^ mЎL)gJR0noa֮qˮ[P!J7|iY^G6"TWp:s+D)eq`#qѡ)ZȴCwbUҬ@d{Ȧ8DS"$*  @ũr@{,\[}HJ/0KD^?o,{1zx RnL&#m2DV2xyZ ש 8RIYyZWK@,QMٳ[a ^ Z\AZj,$Bs8&PIg.gUUH*x I t($z-ة |iښ|2mL2ْҤBbr͝hNsĿK\[[Yи;"PK8Хָ8dD,ühIH+Z7bАahALXGV[i1\mF8eWK EeE%Ƶ )NuԀx#/t˂.Eg 'LnD۸2-*}3>AS>H0zBe@=290KQ%Ω. t+]˒ "Q0{D4$ھE,&?kshB]aQ*Rx `8w*I`NYneSĻPPOXss dG#/ݕ $ö`M, !ǖEBZ0D+?D|^DD%2Ue@-wByD,uBc*odMz,^R(N:v0jWx| \9Jd팬/c2x jv6wt1CLyӛܗ4"o <䐵IQer=8];Ygh~O>c`] oXgn-5^F.*Zm gVU dIiQV6GV%.NT[՘(yފ9_2֭1X::l{'?@C=h_kā~N?TFБ,9\x8-F w5 *aX99p9g F81R`N.֯9YC5TRX b>-ʸF9ydz 0,qpÏ/SM"aO.zGsț z9Oqk-9r тL#I\\;(kaN$ݓ19iX#𱥈/c0TczRM;N0YbIh28iHST=-KΝD Fm#m4!Y5cz%y-〟Ӄ)ư~]U60Dvk#{~ 4`Cp"yDY`JSthОCNg̓Y^;C$;uyP9Gi=g+*((7cD6g`šm6op3+ڳܻmA$'wƉE2RSfg:uͬbmjlděYnB sW{¶9վV>?cC2b7Oʒk&C!F_g !՗SZNN=PLΟ{:˧~ (e%S | ZbfIF?120."̶3s {ـIJhcq*8 z_-3HCʇM 4EZ_RZ…%!eWl Đ~,` B#w3CkU'l>}BlNQ[|keQc~ҍ^,uk  *hJ?46r)$+$dFJ@QUmFktЁ_m~tb1. {'*]qw-H8ngGjzG9MGgf(svɼODuf|Hb9bޫG۵lsJrWzs]&<_d%GlɹT5W)Bf_z{x@rHXF1(9SoArDSSɁ25lW >7vd_3qJh̦#" Ky>_M4T㣑[F}11L" )#Y -sTB[,X$h=i@Q#,eb"zhSC}eRb<ϷרWaƷWRE4|xtT'g:">PJ|C}5 D0SɅ?^}PjĂۿm=9$Bzcťcw{Ri5 Q84d$\ӺgdbZ!S#=ᖬU_$ؓsWB\Mtt^,svpvhl% _(0=q5\;ȭ?>z#K7mUnGivAwmzfH[c&[)eQy{`aX ;b1ʹr x_ ȷc4  -S \ *i]}9A'*p}p9ڟhxmTas#C9DI3R'Y v:oRWYoYAgΚ%}qϓVUr,M~dZjLirQ R0\^e Vq!pD0 _ݮu~w(;mq_SQؘN{鋳Ô֍ab=2+4p-`k^d5PѪXgh[$T&ZۚAUŠ!⌓%$HEKvgLRɉ= ])1a6 l7;7{ 'bGlJ=H6r]dg$;@&SwfQy=ܞ8{(ED*),ga,cg3.h,G@|(421dUEyv:!-]J5&~vM{E 4br~r d]EW @c| Ƕ.˺H=wI)w,2 g\ַ7C#؂ky+ͽ^~Ӿwdl`BmMxȘ`p,[ı-R %[5=Vϱ(L.: wJ7o Ti6'ъtւTntQ_]KGWo&,#g [ߌ䮐|v>^4\T|W JpyLb~.ɢ. 6TH$߻tdocnq+s?~ ^ 4=60Q%rB _DZjdaTv3CYnʝZ!N!. :䯨#QAj=;gJ{AߨdVDETR&^%[&k櫮TJNOk( ۡvTY8a\~ pmŕ:U͹9EB|aUI\nvP yd%Xx.z#PQK꓈$S;j9YIEOa7*ҋ+Bٛ~\#u+VWh]^A?"CT'EηXz_LI\^ԋǝ$Liωᚰov^љ YOAC0dCBAQGvhvr9ۻlG]~Xz]B /N|\ue&iYX)nSe[U1]BKFOX;$jS.pqI0ӆj>֌oO*-K D3J#}Cot 1KdE#a0I4f9/8\ѵ"E з}r3ɶ⏝vPLS!ZxnНǗq:1Wo3 "VveZq7A14mcPܥk_7/\P.vOf$tlO ekQ+*H-rּGYƞ3_[*zk!^}:JNRa&PS2 ?"J'>R eigkC^ە~2|#t#7]ȼDGTQD)ohHp]*Fdc?)$s=dmu|.3Sx_=^M!WcޓeH(0jtͣUxG|_*H ۻŒ`8]xfNSt؁IGޯt;b|7~@=s.w1jrd2߃pGthoWI8M+-mDVsgOVXn{ˢ֦E1/9fz \vp'ZѼ`=bJΗH͎LѪ$jP5eo*abt>hp]:|lıCsyԹƩm{y8M:\gB687#m]Do\mO#^ɓVv{kL9C-UY~)8S\6NHlؽ<{:| >pH6JӐ408lMĊ]ak(4kV @9i>RYE,X1t#].i5%b;-sgѦCqmrSRbFX'wr1jodUXm y-ؼx!i?wM:hJUO8b9q7y BcսW7r漏ނikқo u5nv8#*dܜE61%5O}K"Q;D* D誈$fb[=#O^VjgT .LPݚ~$&͸@afFVz\(3Zfs &+>>! [VUĐJ+yqQV߷\o=ojS'IQ6n/%iko19\l*3],YTa0}Lm/XQ}x}o`#܂;8Fج:iժuQ`.)zy~3dy`J"QݧK2q1e0PY'ts GcwI\V;i(NO=.PR׎-W>#.SٵC: 'GGSTF:2Q7ʁʑȚo%Lx.=i舖pK%t*`׉AmMJRt5p"j+ջ7AUq2O4H9vycVl׼}ɛ :oi'Ҧ)Cסcܤ}),x<FlƝ.BL,aK` yP d~l_% WS -U( Xg^ѝگ?DÍ@ ‰$M]HJUQp\!wE춿q|ud`۪},3"jkHS")3:ٔ{[FH voB{Ϡl:Cӗf툣'qAϪ5&;lIJd 'ƭ+ m~5(֐G$i endstream endobj 4954 0 obj << /Length1 1644 /Length2 14112 /Length3 0 /Length 14971 /Filter /FlateDecode >> stream xڭUX]%{ЅK [pw%CpwwO7}gYd,JR%UFQS{c7{;FV&>= iDXۉ]@|M)@d`c"P;x:Y[hU4iD>=-T?n {['*p,m@J Iu$(X,M@v Z?93}r:gp9Z:;,N@;,Ll\MInf?o~bdJ.&N.ϨJΖ0󦩽?% D]v?ASKggO2'lig0@@'S''?:K@y` 1cB`eiY3n?17ӿD~&4]>ChTfA[j<_(m?;dv=hlN_okLQ;Oiy8xXx X:*YX̀6}]dci_0L!8 Lkfq 9Y}2|!+]>EiۛB11{7#+5~_Dy8YztYXXX?I? B#agbo L?g? &NNk|?z aeބ?*=+åЄn/+Pjm ?5LS|<NeFzql{RA}TA?34~mAphL(!`wz w+xt@3IDkè-<=J:~z5:<4sݷO@OK9%Mv4ro0 \ݢYEJBɚqNl! "h'~V(@2uZMƠsQlk^/:k71jQ2s/ԯY:a R,oQdl=bRM 6)ԥ$CPCzQ.[y$G/CS%iJ^5/U_,#^ifVjQ笁P. hBG(|"Äd7U3 U0SXjxLTd̫z߿cw6؉[3곢:W.|˗&U= ջ#h=? -[+|foN9?)+ź&զt;{lE`So)F%˟2H<%,@X2O?&jś~JoS?y9&yMVZmesNV$Urs\ƽKe5M:ceBB~"d>SIiLՙr!TL7 h)| kf|G5KE B/kU`͖$ľF`AӲgh0>\{d~c3 B4u=gB71k߅H>Z0ҡ 'JgNbny UA0Zv=(L#?`Hb1+cIh _YRCK5a>*׋S87oQ~"[j86ym(AXZ`M` I`3:_*QCޓ6\X_ԋ-Y< &I2yrjr,+U}MqEc45"orGi RD~A}< ]t$= ~>yU2+>d౾G`$i(WضuE0(Feɩ =uQ<n%4Sg\1L:Ee <u=wlL\!W 蚍5b꠽~FXK޽bڧ2"-Fq`Ct ר9.$PSpan)#j-Q|hSti*սOtn CP G;AH7] qC=( ݽ6]8R_LeskJCioc rUZ4*v_ێY<؉fRi2z"OZd~ dpxc(6j*Ղ.Aq!)cs?FΎŜ~ {]8Kjb=FU zX8\?2ЭnG|U,Y""IFt%5ѽL8LW̻T^\;r&*a.ΎA1ǝw]/^)Vz@DUcMyӋsdYy+La$InF=9 7M7mcYLy TjZ($3N+NpK10 6K`X˒Z`8#67 8&FhF/^:4N(zA~˯ )]}|1%YMn`N3=ۧ4dٞڲ!-ͬwzz$z-l1?veOʌ ]'r*a9 s= o}r$&*"8:<(owX/FJ raUMշFFT)W[fʵ& k.۴z3É Lh&5ב '𿩔-?r&Vx ^5/ ,JH5x+SR}h\xXyE=-ռQB_3^y!3@䭆߸[Bұ] EF-rE tA]sM;iW2W$ fTٖZ%1{ U B. 11rʬӺ7:fIɑ06}E94|b3Ȇ+\`%* K;00"*N=SDk)e(aiEO e~{ T%ckP`74Ԑd-J(alH3\\*Q^Tn'/Xu@hZ;EO7{.o`^{gV/(m>+*'o2ꏕkF_p6>Z BQ~B> ^f"YiܭI՜evʘ$6x qrݸցK݆`иTq(\ي5~r#3kU;.&e$mG3DׇM7. .g+B+@V0r@*K4]WɍHxJ-MVoKgn!tܤWXd3N&`z 9|ct[>/:`G/ zą@CW)5@G`r t5 #Nl;؊c:H~g:g+WZ.0r(m̲F"?YI"̝M =Kk0rn+iL)lUϐ1nI);)g wvm[ädv^GZJU,*6ͽ.g6qS;;B}hpu&;^Z c;Qcྼu%* '_"5+BvѪۑ[Ğz]Fm j&CㄕA#zMI,:qzU! $r_ U9u~FFju#g}C+ƹ7w^biYi\5X3D~*џ5$ ִ |TnbfcM 7~6"FYF5%R$t*;WR,xfnvSW1LA{u=38#:xz¥5D1fMڣgd+4x4AtN'r[0瞷0Y1H>l'nO _9N6; ?YJ/5!w`a&︾3]ɜ@obfd1>Th QH]m^B{ҖC.+\ 6Ē46]NeiJk1đQ{98DF1#.tI5cNthMuwg3ħW'A :6R𚠦͵??6 7X7v⥍Bha#AD 2|oO/隉S Ow VC_1c Ƌ$LkG?v@_F APD""e8w*IUe33b)cHߋZ.zb 9 *!|xՏOˌ&~DVDU ? ׵{זLd9ld:K<_6~SļѐDFuV0\7aĢY|& 5G0 e)c4VKA ZT;uy~]4N P7<ʳxF5#ڥ~ԣ9OUMV%nΘ@[o_9Q|%u gPd$FafӯY#-&SBn\NbI4OZle;(/$Mn so+K|@ 8S -1zu2aoE̚#Ezys)j8Uba8٨aI蠌^,!@vW e C}ICն|[ =3ߓwZ#p~,uco)!wIS)*jŏ1k`\Y ŭDp&%`dŏ)_L5cpZ 噽C`vOk:|'VM0u쭯!lp|;DtКbiSjd#OhFp^8L)f&Hq]3lOUbfx5d6r.l؊rcj\ 4xj琠߂O|^X_ov/BT h΅M&)vT /\N|#3kL?A@5jRiu ;+ XI9z]Yq{[:2Qh[" m-u|kw0XG?+ĺʬuEl3P"&)߈Y,V&=28㶱R]ʸNRՏjY6W! OmwxWI8;-:fes5/ǎ3qx8011/L%(3ܧڨwE JJ)^ox"K]Tzxw.5{gq7w#}/XJ8GbEלN 7a7̒l3%6"34b(ԃcȋ({.W5ݎ_&$7| j /*?M_G@@_w@>kIݹU{Lp# X:'w\^3147HEkUFPpW7-\lhaJG_M>Q&;C0hWL;S#slou#4"璟s ݉:AUK8xEJ"L Gvo$5 1MK>x_i f\뷂^z}9#QsoQaokSN)zE+P\^-׹nY<ҹOL$jeY>85tXKny*k'&Rd]~3q⒦m%?Q!#Ȣ֒jQTY6rUu>uؗvJl!ķVO,c J3SsH8;ivk\(XF;c=e* 1X zfuyΊ,g5&\_$iOc]U#;,~RmbjA>Z:ˆqFL?z]vd&|Ȕ>(& hzkDTjǛ)#R.xEC9fc7N)\Eoaa42.KQ^#Ur]Yj%4zCo>BĊ=ZYz+fw RBFyeXC rt|wmڰ^)KDɲ>pgn]}C ^22|;p_ IRI}Oy16b_|lb- L9݂Ԅs>4Oj*ĎWl`#b^?(HUh;:b~+da)E5ưv;&2Q|;)hz摣+Kg+>~pSd2y8 }?\a|5vϺVNex.nڼ Z[J~mcO'C0RKVVytGbVjmnG>GL5DGc3?Uga"h0A{Yɕ.#Hޡ ͊>պyW]tZRf3B/AnD[̱QwKlv6Q)nbqcdbh 'ԋwn|M(Ρq+HUad ~%aM ).!!YhRHqi^'4 ~9#;CXz.cˊO.iY ܟ:X( F),^Wpe{Q>B,O>a4{5s$\]]|-iXFpZ4JgkEX"mn`¨Ci޵:[%m<,<^̨{(N;%u u:f-:o]Z%fdi[:0>i6Vr@-F0a^?Qw>B5c"6m;y*; /D`iw5wILk1hF)d](?n1*Wۢ_fOY@0;1(57IMvpm3S,Jd<gLھqnI(Z@ j` _+gIRcL<ZԶ n7Gd rXN^:ynɕ r1"m_%]|8jrpse+z8t5h8$<`F0kaXrȈ~nH\FX_b7`0ւ/=I>r(|̀ /[՘Gs|)d]9 <ҍpg,3uۇ@ ?w/FF@fV)OieȲAj, KkĸGNn{ QVlRT7&ön{9BCbE`Aӟ];h!?_ 0{OT͑IM]>jEc:uѫ_- Qr rt ŸvU 2^лsJ[F3όP C wcmLxnj`ӞT5"$-_wˍ>^+{hs伏50JCա.zlVCdoL$u9>t;g&jOtY' J>;plAdM*piJIWN{ T^k}*zϽ pv|^S>37 Jz2/Koլ81*+7@ɔU}of̍?*} q;|e %۲#at}e͊GI ׯ4)~6cҰ~}G anF8%k{mhjBO:%ZEk@f[/4w\JDlqNk7ߡG=b7ih6V2/D"Ө.S86;^NoVqxF"'۫kaDd)v_i@(Tl6~&%~a548{]k?Ӽ1E#gzf (?:,/t!+YkJ{_aNG<5 ,  Ua:(2󳗂IR>N=FfJ%l>g >12ƿ}1(\v%.0z>\/XEBFWMW]ge389.XAW=>O?.9WJ~m#+E8ˇRٳ" N0VluӬDHT@<kVa,cEB8/>sBB-{9+$.+i9Ւ,DiYpB5ב Dcg5"!m4Gtd6K Ŝ ڲB;¶ǿF<IE>| .qW)aEr(ñCbFmܯW%j8nڼQ̮[̒zi~Ipڢ'yGJ<謅D^FTn}m0j.V:m4L@p#+ǔJ>>}!};ATv=Z ҘU˓70wZ!DdodnN,ٕ5''#)pӥo_h4{|Ⱥ)p${RE#^1g)z9DA"gTVUl4pPeoWd5ٚo%Mag#.Qg%<*(aHkg b߬5튇ҔD+(_F#j-=Jw'F61| @%Oelk 8jui2Wlwzi >V^Y,B%80VMo~^KzRܚ%4W̻zv ZnUjIQ&'/ ̌늸?-*, gkd 0}3ͮw@%ͩqB06B W׉FiqpnS59^\)]UX/[Xo 1āGηlhZT&./Ve. endstream endobj 4956 0 obj << /Length1 1647 /Length2 15181 /Length3 0 /Length 16035 /Filter /FlateDecode >> stream xڭcxm&c;pEtl۶m۶m۶:m۞<;{q_uVUuc*P X;RQӲͬmm$L,4 ;@ hdбAllLLdJ*)((S @?oK3kg#K[+#kokC## #&&- VY'!oif430v0 0X064'5o.>`kdoe 0sY;~߁ 6 [&qpt07u|{wzv06ߚ6N/u3v8:K`h`k_a89Yg{#={CK#oon?oZ_Z+3G#Kcjh:o߾M̬i1kcN9AX[ im]LWo5߆u+w{5{$,K={? cgef2*FrW.M+DEDo)X%W6446.ۈ`fTߐnʀFYQX]Bm,nFIEqxP1Yh{?Rzf ZjZZ:|_h l #G=k_`'{k|g ʢGyJzc FиF_ݏ zł<*nmr IVSۏ}q=薤IF8^D{6~PhåDz\Kn3*kN3C^=%rE%~6HA@lB?=H:02<4}ֻME¡xJk_o 灒DgMb#P>BK^|0ɟPb@~5to*E zOc!6Fx@IܤWJtV}_N!cH;sQSe4m^%_MQxwk:B8>;_]'[_h-Dw-QT%:꺪h q!T3}/Y]Nq*­_^Q?0 )YcH.34L[oh<90V_ԈBtfL4-h5 ܗEnv<no}x1@Nu;`}ԝL80YU%m_4T}wbIx|@'@ VÂU=^K8n7DžnR.plX de2WSȍ jHz2'' IxX#ZŽ n,sHNs)*j]Ѱ #r4;KipnF[uKJf]nNՒT, ^) mk|'}NxsGay Lf`^GK8#"M)tّ`BwX2/>|0O.IAaoCgZy_}a3{ѬаގM=wc6 Y`Xv\8GVc.Օw`pѳZԨN~m(*I ˞`WW9F,Izf1hOnޞ Q=+pPXWC>RJ?XjP&ؖI-M)>-[.2:L!ؙ]w:5wooK?ȩ?!=o$b3j\TZE Z^E~5@CmBU]1zT8h!2\ *d- 1fl3# }T hnKM6,% YQ)VWC@mO?)XQrL/B(.\zXRPjdeLI!1XMuZ%ⶒzj ܗJ"+ ^n%0spvF -T#ۇ‹qQsHx G-2sW5ta˼,B~T L 6DDȵnV%@'a<'jG1a ܳ,סzC4=?@ reE].FyT!uy녫M" 5/sI`WG3"sBȪ N<5^rz &L|KNYUX0В(R4S$k.[>J.#2+>ua0IS`Idp@9flhJfqwI֓׃ANR^<-!7Yϐ@dIxx"+PѸAH&hrv1<ٞg3zOy<^8N{C m@mrdۄt UA )>嶫76/n, vکnK2|e=Ƙ@> .9Q2 r}) 2#E(5ó+L CM="}W_pb1zۛS_z 8Sѯg@`syXBҼd!Jz8q]xxR Tee`qN[.z!xĈ6 'c6˨ŋorSA V+A G9$8;h9%SV!aMr@?:4:kJgn\es2;yUA /iHf9y(K,# Ap8En`BG9^+϶ ؂ f*'cQdJnL2}T5 ]mu'{:Q! Nq(qZ[xH"]z:$+U GKh ‹@.2ŹSzCڲOLk "#gSR `B E;1CtWQx%H1%C8BQj$ d; z`5;(ؐNtIdZ8lP:F8`GoS*wLdjQLX|Uq63 W?~E04jg!e!Xo u2<v6(oh՝gEN/֘|] wyaO('AJ> [t=c}Շm݀`d-]q$1 Ό&rM@![[N[IsehA~ _1υ2~c#xť`NK]'y܄~ř ῰93K 9#n^}7Yh; вʪܩ-I+[Nj5<7|핪u7$~ n~1>1LOsެZ=P3/D):р0n\nKD%q.zgvn*#@SC1ߪAgb/AONΣ߭x+E%޺!wmp8+J'An0E^\Z Lɳ)lmic=N㔞c{ NWGo 5mǒz%P\*c#bƬ(Z]*0=Yȿ w 1B/eS*՛&=<:dadi׌.}&!$yIvt-d̘.z& -XZojrwCTKu]{qX㮾, x}Tbi?NwDGdz,[6 Ӻ,'MŌ?s` Buh5z/ߌ}2JD<^IK6[ ?7e^*߷9{/D@"y67xz C7 @哷ּ"Չ7x*Y ">ܯOrGk_ %n`kBiwa/ ?FTj_Sv6<^=K`=2 ʬqa66v@,FB͔Wx|M{C&#mVI9˧3*;|:؃vwTO7ơJ_sz ¨tV4.0cs đmۚ"iiA|A[\#l)@aGS\+ԭ0W2"+χᯬ˂d՝@Yr!&:;DĤ|vk^C1*Y z>aJF=:_aGcח/T!- cB-/ i2 vJX &k5k&@R|O.x9*(*W=aqA%*9CSxkKO඼nJ/O͖{,.HB@'\t3I6V6;6EM)|=Lo@ޟo~=.O%jo:׹m}zht^X1&‚:]V[!HO U=  3[x5I*hBu|8[v GJ %WDpGę^w#9-ǒ0i6qŘwcytBoI^NL 4XW}z<E=8N6 TCOQqW LQ$Oܶb͐M|[t& 'k<)<>n[iXl-<=փ ZLoWcW/fdo٧ }bEY+:Y __BIe"gR(Slgw0%1HS*~Iz!Les[g٩-19I8~Y +潿YC&Yύi%*ܬq09+}hc ǷldKDq`@c z1 ;G4}hz邂 !?ܓ2(a[7h;jTUVOq9<)LueXtt!4:v$Pj@X&ĶA ~d}y[e_X*;dt&xE̩-E M[NݞLHvRz&t+Ko E™v+ֈ؝6+oͲėj~|7#L+ RKهSޢ8KTdwW+O+LJa(QN\>D.Ȕnk.E PVL?֟%ɳRqtŹuHD0ژXI ;ީ_9S5Idal#~l{=FPJLU~oc ݋8"?罘H`U/3Y1q'Ctut(p@Buxh8Wa? _iHpT%:xE-UZLB-o)h w*?6Y4%q6^SV-?5y# :[w:tB06v'³=SS7+f-"ޛɮzMI^lzn='y#L[&kY/'bjPl) +o "5&4h{򆻐nfO?H8zfzﴪN0/-֩nBȊLVeޒ8VX(sX]uѕa.dz@l$?d5dkPBv9F3Ҳ:}KSCUV7.m0*,: m.t;I6i{ L6{Ww(s_U"P$恺@cD,fc 2B`<^M6u?0y;HS[a|wD~lygvh(n&T>* Xå-61_t_Qh۷Kzpy4qYsl@ZC># h*zP%y23S2bfIЀoM3h$Flv$-BmT>e7J鞱-ǁ=f. 7vceB^^h;ˀ}S,LߕL(Y{0D\ 7f~2ߵcɝTgyjEMOu-wMj+n ΝQa*n࣎_w ܶq/T?.Lidq^}ʖƹhmdN0! 5Kt.,PtiQ9_@VGX t*v@laP)3!5}jgqjo\9Gm;:O8{VE+.]cֺԺrtݖ~$錍sL0¯KbDRFך_=VC [Y"wM=ulSpYlAZHWlTpwN䲼7Y6nyBD2aie}-,LWƎrvJ$D_5ח1#)|drkܝrf= Qac/gC4A K>Y/qq|yDcj0k^- f dž:5s^bތ"*%e֭Þ}|3#>-ƹ1 z 3,*X{S&O) ˯2{W3Q=6KRg@sȃ#F*D]c/Ի9?Tp刳VNqߏьgfz@Pmbf^bt.Zd)3f { T#| 7_]m_oK܎3XzGtn*~3f$ ;S7G.W*ADB<(LeDGfޏwc3lյ`m t;8BfUb[a ospKf5FwoZޑ)T|uFP7/JL?AMܢ1! >ſtt#ƥ^6y\^U>T/#MGuy#[ 3SI`=}Ip t`HmC"qt]px ׋P5ա6f@)hp 9Uxghmzd̷ji($!a[bz 8w'8lSkAMAP$XXW3dgOJyBS1ؒͣP8Q̪[9{<rT; zyRk0{f%k-*WEsG[l}JE,"F#"U }1㋡nTbpNOΡ\"d ۹֜V`s(Dd!7{@ӶT-䱣5H)I0PTb;#/ln,R.C +L&r0hq"d`C=nexBmbޭӜfNhe)@qZ{J Y/G~[ב/zl?A2JBgu?s(fW~ 2p^zf^ g/Ş}f/>fncHDG@V`qX H1y$ Zd[J(H@vr\erxr H~ {jQM,j^<W}ҐlEEQL23 o@*o(!EdZ~ f"'e{t*W1qH> |zaQ. C+덍.JI0޸ 3+xkAVK1 0 f]:Xnz}Ĉ0&`RñjisN `D[L %v2>TF`[Skи󩂩Yc,Z߶'<'_o; i< ؑN"L,5@8Ynmpsy>Ty+_-4:ܧxskkhTݴt|J䪽6N#vRO=N_GzC'9o&~[?(Eosgu3|琯 :#ŕo!+lquFͱbHpoNJl0}y'L>QEBltR yF)[5HG$RGE*M] ȋ0lhsJi:{2D|R4C- fNTsLfu]Jb#;%Ux+:g\f <:,O <6bFY\>e-b}1@-6#?и\]WC03^?b̈9ߜ(~!oMx=XR-ߺoޔh;fD+4i)Q=W|o/0Dž^uH5IF~nTN^c24CS2Q#hbӥȲ_rn>e.X c=Pa M0uqvu=v;w1D8, Xb 93_L?)KkF лȏK~.=R&l\=.a  Y4˵Szw42smuXLgZ6R j9=cqUl}.Dˣ箜c eYf9l^OC|9Bk-1RiB߫7n0թw!]' |z0ÚAҩ=o::&4? 5{eg{wh% 3E* i%Z5~ &:S(NJ2ap4-bje=K55 'v+ω4wGBIKaY"A_!G+YzN?֗ NHsAnf~ i*CF^j-E_bYّF*fo*0Dm[sD GGeiEsyՇeG\~// s."nJ0?2qy"`)QIuXFKC3\= 効Vį'@N`$sʏ>ZpuaF#>6m_tKݝ3,y-r+is^` #qOzRHʸRG1g|h[|3qOg><ٯ33Ix54ԉ%ewAppғȰA%hw)]x ya<{"S\2 YғiZr\=KO/>=Ik>ɒ80ґE $JZɦ'WkB-9cR(Ҥ r& U\'&PNsI<_ i!i{ o!|]]~ABd TBXG٥Ώ,yEZ![FFMYhF6q!ph,?Q8|g#[^* *e/ԩLܨz֙YtG'D-ŽsSFDfNߍ샽0G\-U~";Z rfcٗJ6D'ǩ4f3PxtU495q=B LF9\JvW~&7Pȁҡ]" $Yk 32s<LR$ujX3緎 |ؤVV;@-T$*'X%q?ec.!%TvtKMbj0 '8!5 zn)ER6|lAla* %j7vAagdy}{c"d!cqA L^]9KBsM vSx5S1+\Mp̌k[yLJ@IXO]juȘ@䢚/kKR,/M=Ԝ\rf^RTp69M3: j1:I$I Qf^q/UG= )Tse`2YM.n ȼ`1^۟Uc20Eq'] 4`'C$*X pxkg)^x:V2WJ n@$yDU5j;QW-ZJd}mhaݕ^wf͒<;Nd LڙlcH޶X"ld͆jCBT|~2J[P fLoϊ)AJ5A'yWC8o˘-}z.lP:&ZD FK/ȮjoC9钾&Lkj)I#,@=ߊu,QP*UϏ-g[E>?<Yv1Orm$p h;X%e[z$[w3dCFzSLXNU;Gݷr\hmTHޛ1 -v ٦"9?b蝤CP@Y IļD+ E|bܧf޻dTk1N9 mk!<4Ǡ}' glS*|o n1^X-24Eu55e_Q0\.H|"bCREDIA0uwlt+Ef}vuBߌnel8RE7k"bŕyC֬mwXru8|Bw#/0!Gca\$#-)՛H-. "LZί  V-9ni?d;3 RiN+/`28JJ8~A຅^Q4\K28˲n3g.Je7l- KZ _P5;;:og#!nʥSUKs~ SD`]bz3 tg]Xi͞v'7 'Tj$H Ymoqz)]lZLb JEX7q-7nQٰ N0m)健Y:\dFY٭0|&{k]+sq CXkX<=g. #+Jx Ն(eNlz$s&YgTZ2Ƀ| 3>jNo6v5e@蓑c|&A@vbZ@jj+߫'\n%%05S9O ?rt<|6c;6?~XE.NlGLY7=(OLhD/yZo&Dtk/×__A*d4I=`T5 K .%I:x- ɍD = N)+aIVXMװunpI;즚nӶް 麾qu|[1e xMX1=tBc"/qȿBUu&>]Ųp_f ß..E=MSd)EqXTn:J8ؾ pS?}X^{#_ȸ?csBo,5ԣe_>u1n>b`+f;P^]LmPB湪]pRjQOO[ a4NJ 6:?f}~2"c=vjU*7ʘ`wxvs £oޓx=OŽ=#sCPffBs >eBr_}ݯ[X xDvnOK-krD-ˉ^tRGGNm*0yϨ7),A*r_+˜"O !9i'x}!|T>̌qUprZeSOUW`@ JQJ0&PH\Ǵ惂J2tx(搘,AGFɹ[Sυ #fz. W<w_33[85}nBo>a#@IFߌUHN/H-Ѹ׾w1`.Y]BAJ) *tzֺ /A'efӜvroY9ZIaI;}q} W;c[9-V-0'>"dtAGL@u "CKpcҭG!z0rWF1DdۏLP}3_otцհ/H*J)gk=%@'۸|Մ [HSJ ǙtݑdXτfm0׎+׀(9%؟qg8ř30)y?ih( M_*Nom qтz;hǴcG$ )¨dRp>.G^tUVGn{=t0 TT]c۠Wk69mݣ`Z<;B5Y_yŠUn 94+7b8M3\^Y@tFKxkG%Atxʬw;D,J|aV>_LI0dM{40a#p~|bW}i Gt|.(JzXp~_(PyE"ErYWmօ"lC%?קk>FwL;8c)bبRx Z1)( bl;<_Cɛt\Y"%sM:+8EtʧB-f憘 .hpIjˊlؗRbLa{d!p,@h֬SCZzJY8WR$u󻨾%Eժ?=^sM-;a~0QPc@>xsbZmj@s [pΆmH-W2׺> stream xmUMo:W5?$R. d9M eCkmCp;;w~>|3E_?O]5߶w]Occ]=~?}Oyh9%?۹׬B|Ɯ>);vw%g43>\ 6 EJ78 1{~`W(-;]%=xe_,b+-O;q\L}UI--=BKE1p[! Mߊyu>.N5K)Wb٬8i[_uʕMzQ)V(Txޢjy!Z2P="Zd0\ÃGR\).2*Шa!U,H`+j.5Nα@VK-x%3%AYӀzΚ>kP#5m0Woþj.ZT$X/)n)#Wo(oRZ $Kp4Z-b\1ܰJ P"GXQi/8k^Zq:Zs9dB )sL-7xJ`aɽ)f$1 dъcCZC<73JgznHȰYɚTa,_-O87}KԴܗLloK+gJ.GZyVc48Wt]:P~`rZq.n1] S/Pu7Ue:?&?!d&1yHn5)yғBx#1ޞ]Go׏M?X endstream endobj 4959 0 obj << /Length 700 /Filter /FlateDecode >> stream xmTn0CƆ@LE"jD;oƤjgy_xN{qV'wC&]\]]u>t\qxں7ŦmN7isƬ'k~G]?ߓ` 4;RV_n86]{̭֚u[sfߴ L:?v>4|`0nhWu}QE KU=5Yw߇l?N6jwwv Z/բ,ko{&PaffIq XMJ0LfhrdĥP> stream xmTn0CƆ@LE"j.RC~8iZ)Ayo7?nkNy$냛G׎ծU[7|SlfM[kwʽ5g x=i6;RV׵_n85]֚̽u[OsE͡i P{ LՑ @4=tb/yVvL MnݞArjwf4P׏ީFT]Nrî}sBZ2pmmR?\rs<, X#.KIɌCH'hjmJIQ09da"2rG~\5hגQv]`n @v)(A'b}qHI($ux-JBJ!^I :ggM597F7FN}Y{}&Ff.pdk_ ΜN0VG9ʱwDK4X=CaCɁg2)4X(rb0/s4lƵǮb]ˌ[r> stream xmTn0CƆ@LE"h.RC~8iZ)Ayo7?^$ŝPIs77EW]}==硫nTشxGɛz?{k۝=` 4vN߷u8NM>(s&`ywS0jzQshz+&TuS~Hxqq`P<+ OC톦}SWUn}@`T;P3qtj}w*5UWSܰo\ze \[3. 9ff ؤdF@!i @F\ ` H sn4ȶ` $(Ng 2R0zd9#Cb.k(@.0[Czr aà8SuX$Q:\CAfpGR~m%^!N%$h&՚R #ƿp'XϾ>AI }3Nh25gNE'bkkؿs %|V !3?fc91ӊ9|u 6ZcWCab d1׮eF-9Ag깐3Z=I= 6-7p?)pegT> stream xmTn0CƆ@LE"j.RC~8M])A̼7W?^$PIsWWEW]}~{SCWmݨMi7mv9I+ڴg{ҏÄ~F )P ǦkZn;@1zz5= 7m=x Fgu P}?i]X<;k C톦}UYoO} A`TS7~wpjmS!詺]]ꂅK(ew&97\=̒5⒁yAa>:M1ȈK,x΍t,@F*&" C,zdWXPv-hakH/]d"btv"gg?|2JB^G5kdwt,uVT Jb9;kBX!00a0bw3W M";\88̿9Earʱs ށ?c>+q p~PrL  hi˜c>:q-+01~k2#Ϡ3\OLqRυ>¹M \)s9O \Y!O>\\/Au*[ӺkzT%C0t endstream endobj 4963 0 obj << /Length 700 /Filter /FlateDecode >> stream xmTn0CƆ@LE"j.RC~8M])A̼7W?^$PIsWWEW]}~{SCWmݨMi7mv9I+ڴg{ҏÄ~F )P ǦkZn;@1zz5= 7m=x Fgu P}?i]X<;k C톦}UYoO} A`TS7~wpjmS!詺]]ꂅK(ew&97\=̒5⒁yAa>:M1ȈK,x΍t,@F*&" C,zdWXPv-hakH/]d"btv"gg?|2JB^G5kdwt,uVT Jb9;kBX!00a0bw3W M";\88̿9Earʱs ށ?c>+q p~PrL  hi˜c>:q-+01~k2#Ϡ3\OLqRυ>¹M \)s9O \Y!O>\\/Au*[ӺkzT%C2t endstream endobj 4964 0 obj << /Length 814 /Filter /FlateDecode >> stream xuUn@Cx ,ei#$JW)R w8`x3f_,Y}..=pF=Lc겺oxķCvYQ_s9;~1_B4-辒O~:p̵:롫9Dsg~&1^`32(WB0(~z?v؎r8ӫh~?u~Wu]t<(V4dqy5jޫ kOGKWj4?L%/۳v _NU4(61ȘH`Zp0aASgAQ@Q LE)58ZP\RC%4k(4mA%MJ$*C6TQ.c3p4ct| 1v9y\;摴.y.i*OYIa%a2A{&cxs4c̲ lcw36av7fgΘ4aʒOg[2O[1[3K?mgS- }3 O3ev/Nz}\-!={3pII)dKdgI$[d$[HI$[$[$[d$[/¿l᳔l1l/%[K~Jɖj%[^JlIo$,v)%sRJxʚ>fT+cVS߰n$7G"=MS8鬧'k?G}&馿r endstream endobj 4965 0 obj << /Length 550 /Filter /FlateDecode >> stream xmSˎ0+$1$#8h@Bܰp`~ +8*=SJ]sCM&ESݮ`w z\ħmbo'ޚr028~}uHXz_z.XA_`1o"xR:bct\$7҈٘TmH@ ]W0ywznͩV+1r]oś}X 6g1ͭnm{!^ ' bނP48YhC`୤\UY=0ZĎiơ 7([4r;"A"e"qDgs"2dK$#В%#KDDNs5&]J[/G endstream endobj 4932 0 obj << /Type /ObjStm /N 100 /First 954 /Length 3386 /Filter /FlateDecode >> stream xZoFb>}EۜMiZ flmeёDMdg ,p8߻(hARHb(oaD)I,\y)gx<[™#F#x9088Rpœ$B) %cGH퐈DZ4'qGH1Bi)heF waNc'Rz #X,,HxЌX xPQ#E @I<8fPuZbAgTd:$k0 ~;;SG K!9;υ!"^HAD01@$gx4G25 %ނ&0u0ɼ wA4B 5 BB)`L1##Wpܡ5H@~;7@o=õs7Sh1 s:wGwhnpq;*qu F;/8/0pZC!pk\W y2\kp5b\I0 0#T|Z2ІR24'1#0.V*$.`>Vc~F`ЇfKaF#,ܓ8k؞>W!qD䁇k[^p?_u8s.n aM+ˈ< xyVLe3gYCzȒ;XUZ z$TAثt4um (%zGan(H#( hЭ? ;@c$'* -8m5Gt|.=Y&CpU_+"(\7X}js-Sl~au*,'ezBx.+Y*<]$ڢJ)-{~^rz^,y޳_=-l>U'f6Ŋ'3#|aCG꬛ ;&vӋpd6=3uxr]=iv_N/5C{>}@o#>s}A'%}E5:Yt ;n99fu-Gҭigl1[Մ t f2ݧ䊾;~Y z&^߮/9_κՊ^9OoubNtzA0\wKsz=۬aӭSf`5Es$]]uWӨƪj6Y]5]_.] AŲ-?B*6'G|s Oo^u71<P Ϻ^ټ9h];1W}+G}3\M֗[(Gz>zY̟אp+<1Y 8 V)j\4 .` !.e\*pEBX6Rtz6]mZfnU@1sq4gSqs;bdG?4ӞO%hɺ'?q㗳|/hd9m.7|z ij髇?=9.`]ȉ ]슗EEN=+ ~4kiН*c|yf%FJ+>0R@zMn=[ED>v.vLbfI7iE(i9'X*4 !xI*lgSy@9Ρe-͐¢+ĨڮF9~ TLs U A I>MqjS ݸ=~hDb>>`]b[">䷟,KLwpNV}k| QMN5f2d/WpXj099aOےho#͉B6Kk;]ym"k-r)12܋A"vs[mȲ%2Rdq"m-n.aߎ)0-"33RVrWM"//ͭwͭFֻb\t+hl/zJ'~A\̧TmŁ3&7a d%˜dr3$KJ6dJLP(O2"P%#8J_a2NYs VhA>r=edL)"cT49s,OT㇔ PբPJcGhkw \W m>#|{ھ:O ԁz6XvIjΛE2 1MLW$f &xIL1b'}1=B&msYcxV c&XIx&ƽkTFT1br ƚĜ+e9kbĜiS11FLDX @sm`MEL 1m`*f0v 3` 3mt@6tUP c@U1l +r@j 9 9mD@ 6@ x^  cU1k*l]yU[z5*YʊP|]};V{ۮUCmWݪܡ+nUpPnն*cv(J[ڱ:;vXJlVv]]:V[ڮUaCYmWժ5. endstream endobj 4971 0 obj << /Type /ObjStm /N 100 /First 998 /Length 4572 /Filter /FlateDecode >> stream xڝ\s7~_ug]&3ΤI{L:n{3>lu,$I@i䶽z6 |HX }JѝN_;T| btD).:S"H2)>N9))v*ZKJg6ԋ:|XNd:,gOC<a]K2'dd^ b_.r$TcQ;f,`  8qr1ʼnt8ݘ@TjLo(GDʼn v9 6 Dr\ԟ8+ HI$"$՗EaE/F1dHDiNT$4'*Q"SG=4bk׊Sy=zqRb '%FxX Co`o'{H9ID|"&C"NS$!Q>iRkKēxOHē8'Ilx:w˷?NQ/+E} z?j t֜v_>߆#v"ܬbܬհÀ?R5VLৠ滶ȨjgDN z]>n-%ݻGi ND$z=Z5c1TBߋvA 3dӨn(ð G$_EՠfL)P+su խhNlE@y}Wcʀ&*7/2͏_M^kGp&]AԄj!!P"VMg$YdPk!C-a;,3lhoh\K)w맇q\a^ޭ6?ǿ@c13!0݋q}{3[a_j-Zle_56Dk_SHIYzUyBZ ؈ [~Q_Cr>ԛl[6(T6lUAvlDrzzXC D~l{8dVOdBNvqzldc+ :˅5XsrF+ 1hO#v5"r(wٵIJ7Ӟ9IazhKQ¬m_JXIJC!n7i\^?aOTɀz؈\^lQY,%LY7#qYc^E9Zᇧq Wtyg;Lj'sZVY5PyZѥF+wwxm3 ys;fF Hj5Ҷ(?dH[ jw=߭W،}ٽI# 8aEש"=Dkw5wr\˸S}Fk}N~#-;y#5zS>X ?K j~bz3 $9;n ن3%_wSeYZialC=7}xm{ƏKz##b;|큍})""^f>Y?aZ8˲Q0v]O6|ǔԗ7|3noqA(5Weٷ6*Wx-[sV42~gui q5W- rw+ni.1!9?u Ȳ{zxp=?OOx|m|a4EZsFy"LK:P<~)V@#s\> Y0&=9 \r6ܠEjT \U;I"ƂUFś} \XӔ.Fw:)5pQWO*8T)TbyTf.&:09zs;PEϱRigrEfY)7P1#Tәhbe? ?vrIyI=61,6phXd,+aaq}5аh%y Rԣ\!QG۳ ':0+2%Mjͩ* yRMIBMܴ6kL{>V3ωb&#c-)?N^':0,'s3󹌕Lj,d2S^*6c:5Q~r:E|mMF(QXd|}*VZȵҜ@W$@$ *KkL0O?E|a(FqIa,a2b &Ē &mlCa 24FXdĆ <:ijCF.8=Xd"9\2I5rz#M>ҴA*vtUsi.䦐BnP%bpd)BI^HS^I%gbPq0y. 91Rx*FH!E+D&;̅AͦtC˦"EU˦"EES F 41080ΕUxk*l6{n>ՂR?csUjd0rx14q1ù ~( XMoLN~fY .a&Kfc6?Ke> endobj 5061 0 obj << /Type /ObjStm /N 90 /First 931 /Length 3473 /Filter /FlateDecode >> stream xڥ[]o\}Qw8AF?$})@,93G;g7jtəss-{ݷ}+{M t7VFFZǿ6zFDzVD{ؤt훴V_XKlϵ%i>Z-ZyKxHj6ꖆ{[TZ1شi+|tx3li˒[-kvZ.ZuCOQT=>GZ7[K| q*|d#JGyE|QխFۚ2twFt34|߷vya-ڰ?ݬ[7:=-Wϋuj8Tkm6ro4Zfw_Dv-ٚ 0WG2h桢i7],VKMɜ%KKM/ɼIh7iP>{$;M[ě[JO[RϳyK9[D[*ZmkQ|YPͽو6S͛ ³ȀFⷮ]id]S6o6ټiSsߖ=@0f'Ia_W' Rp,8eVs^ wqG6wXP2|PPjۺ49wa_y>+ QƵdSJuN)5iq]P4=2o&`Q&2o yep+)agvaN2zua#%N8Kds.J}#;`0`|9fsxU=/@ 5a8Z{UaRsi;V)GSY:uY~Ԏ;9luΕ'`)s-^ -ˏ8o< n9紁siy]-ˏ+՝sⶃJ;'TON^^M6}Y~hB;M^agx v:N9NQ/41v8! sq?9E 5b,;Q;@y'j(wF):æy1U^iSFwd5ݑX*6ԕمtN?P0 {&{ݳP,pqimaNjSZuyx?PRMTxf;˗ D6wXFӷP>ZP>ӴL o,LEwXH$M$M||r` S`q*\$:鰂0w;S.gvbWsZB A'ֲE@] ZCJPAqy@ds  %m #B)6~B)T ";,@@`6*Q' bk;(6k YN:`s\`V;Ua ة S(Ůyb<&VΜC`\R왦bJ˵,";,`s8xCR<1_!σ,?/+B_WJ䯔 8xPtoT]0302:4-]'ZNm.?ڲpyiq vN3;M4׉phO/6ϧ,?\^pĕK++崃s^A^[}.?༳{p=8C)8'奮UvYˏ,?\^Rw\*rE… *RY."i\h]8*g,T!HD]cȼ<;A9HM#lD4h 藏|gyG":DDsOW 1by]c\4;[`p+ va_",2 8{^4WZ9sڅssi+ -Q",2'p/s: W~XNKyr9ȼ<җAVp(G i m*Vsmȗy\F:. |u ft3aԾ*\X '4.e4tl+{çǗr_7/r|%3߽{wow6oٱ, X/kDp2;>R>p; <0SLA}Γ~txxܼ֜9|<[ l )2"<:LJ??\r'(O8 p ЈIi^=[Cg'ę4Ğ)8b%A7$<>%OSREÃ=Zװw׏׷xZ~ ^ۛ;6mq".{x!w"x ʛh> endstream endobj 5152 0 obj << /Type /XRef /Index [0 5153] /Size 5153 /W [1 3 1] /Root 5150 0 R /Info 5151 0 R /ID [<968949306C324613E6EC87FF810296F6> <968949306C324613E6EC87FF810296F6>] /Length 11623 /Filter /FlateDecode >> stream xikyfo-'89áV+*ԪdބJ MT##Fp+dU*SPL҂ s_~I<3;SSSSozjjz*]驸ұHgrl3ȱ]-wq,qc\\* 7kW8vϱ%.OjzjfM{V:YYpu,܌u~Xڱic—Q6MO-:1_fI8]bRR ǺbZ2]w,YKo'ʶc)>]v8v˱o\) w>[8ȱ._rhƱw.ŃrhXco\<, w W{9S^xL/+mq쥋'c{)9pl=wu,\3y^; rqzjYǞxI.;vڱ.^]p쑋Ypt졋96xCn.mp쾋c9xGFj5u1};J҅϶.ر0/Աt1 Њ]7ܴp'tc] wӊ|ep\s1/Lʷ7 wIiZY}U-LJcA_8SfaNW}wO;βE=q3t~c8vEgɾj.|rs0d_Xڱ.:W9134d_YNd_8W_p;׋S|~87I*Z1<|9&%x dI<8u8awt~89Sr~8o8I9.hjpӎVOa3#/=0;mxW䓇Gr=<#:p;;(@t2orԼY7sΛy>ީ1w2;~Ny'g)>t0$02Ԙ3P546uD4p´<}=wӃEy+3#c-29LN!.'9g[29\0䡼7eS9Lo,_;쌄頋%|7]*dGSX.+dDJVE SSf(rn!3GXōI6KBOES~)ܾ-Uv!;e(խ=m7<ι'oI쏦nGr5g%ŧ匜sr^.E$\\p# )ܑrOy(K^>s~ޓ{'~ͽ|-e_Sfăpkml47Z[+.;d{dr@9+M/k>,GrBN/克\p2]5W%+$'ܔ[F;y% x_[uOy(i*DeT6MeT6MeT6MeT_____^-eVS lʦlʦlʦlʦlʦlʐːw9pESs$|,2222I1b^̼̼̼̼̼̼Lu4yyyyyy9NW]\\~a)|E|||||||FZP P||||^?X>~ilG? ǘÓI)$}}}}3hGsu3\ܙ,I#xXA߽7}s7}s7}s7}saol 0 C0 C0O7>s7}s7}s7}sw}~AAAAA:ooOOOogȨJߨJߨD_@wJ" ?]-%TrYE[!ZȬulO,YĤxDZ zD19.'䤜rF99/\d*Y&6z]nM%ܕ{r_s9Ef-}($;֧z _Ky%卼w^>7?Iﰴ AE-((((ƒOf0c}/|B(x(0/$,W/9(!9,f`, Ƣ`, Ƣ`, Ƣ`, Ƣ`, Ƣ`, Ƣ`, Ƣ`, Ƣ`, Ƣ`, Ƣ@@@p cT F`@ @@@@@LJ(((((B'4 C = p X X ( W`"&bh"&bh"&bh"&bh"&bh"&bhՇMpǃ_2IIIIIIIIIIIIIIITTȆG D = MД kE^ʅka>d>d>d>d>d>d>d>d>d> O3={B۳(. 7cS^$e,Ț(JY%eZY'% Q6fIHRRldlCv.-{duKx5x aZQ9&儜SrZY9'\KrYU5u!7ܖ;rW y)Oey? }y 剼FJ ['‡AIvz|{ lOeHHH2Y.F7E^x~~~~~~~~~~~l•q띏k =GbzlFlHHHHHHHcNI$2#d,L Y)d/mX+dxUp($=kOY%#[+*d쐝KvKX7^W5rPa k5HXqLpBpJ5 V^l8') ^EC]Oo5u!ܕ{r_Cy+|r+tqD<R<9($/׊ppppppppppppppppppxxxԛh: cV2%sP2%%%%%%%ܥm G>A[B[B[B[B[B[B[B[B[ KnЖB%%2%2%[­#^____,W$:^&WT`,a,a,a,縙ވ((><<<<<<<<<<h:0000WM_W@u@u@ut8||N)8g`|g||||||||||||||||T% a!A">lwwww`p  1*dZf$pKM L ˋe˖rY!+%@ϭ mubN/W\|E;3))IKFWdWv.-{dr@!9,_9*东~maurN*K־]vĚ˲mWwZܕ{r_Cy$aqy*乼J^K@y+|o||se5sP35sP[$|k|k|k|k|k|k|kԨȬmIԂ[6~ b^c^c^c^c^#][x v^.ښae%,a\ ! ’ 555555555555555555555555555έe###ȣ`+ß2111-Ÿ11u(rwaaaaaaaaaaaaaaaaaъh}"1/#/0#####4M(,V?========================bя׬E"Y,Kd;_nBV*% Q6fIHRRb5_"_V&e][^'c]K.pOI9%匜 rQrMrr]nM%厄$,2~ V]{$_{"_{&兼WZ¢NF>'g+h9|;ahw~/ՐȝղFfe_>wFd=?kJwwwNk!9'ooXt.QNA;;;;::a]hqAc:C<p-;;;;{,S/MI$2#d,L Y)$ \#VzelMY%#[+*w !;e}?o3Xcr\NI9%匜sr^.E$\\\rSnm =/axh{?ny(<V OJ5`]何AE4|#`hVhfU-=yB04?Mɯ㠘wv?eggggggggggggGggg&'#fοSǝǝǝayXQ !!!{ny>6cؔhfafhlfhlfhlfhlfhlfhlfhlfh1sê{cc6i???vڏююq7G3;P06 c0??????????&=&=&=&=&=&=57>) Sɴ"Y,KdxBV*Y-kdV:Y/lI6KBdd|%[eve][^'CrX#rTE3o?k>)ai9#g圜 rQ.eU5y$x? ܒrG=!(ܧL yi5}z<{%xgwAGyƮZ:pT@T@T@T@T@T@T@T@T@T@T@T@T@T@yyyyyyyeuQ4[oFjF>q***************jxOx ]]]]]]/PLNTMNT@T@5**IFׄc^ oc^e^e^e^+'Ni8''''' tE'''''''''@'룙''''''''''''''''|'|'|'&h XL @@f~; OOOHO+HOHOHOHOHOHOHOHOHOHOHOHOHO{HOHOHOHOHOHOHOHOHOHOHOtxߘ{임wl^f ??? GfH[4g$1sc.oϾ h(|j6oge~F$޴mZ6D3+iB-lm]v7}Kv+d޹CrX #rTq&oOߞ3rV(\0k1_u!7ܕ{rM^˃h_AG\^Kye0í+.5g.hf~;cj$/?EUsTQ oE67W΅[/ls,̭fo8q.#07cn[4G>9s#8޽m9nswPfO+%8Gp9xs%羟 8^ 9xs0a8|xw91=LQ:JϽs6|#TQ:Ż=$iEXRY&eUZȬD(d$$))IKFWUv!;e=W~9 @M޾D(:|儜rF99/\rEJVIN )ܑrOy('gYYo˝YoYoYoYnYFYoFYoٟ]'% Q6fIHRRldlCv.-{dr@!9,_9*东rJN9+\rI.*Y&9.7ܒrG=/'ga````````````````````````````````````````````````````````````````````````````````````````````````````ddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffUșS}2Z~-Z_=~Bg B'WEXdEXdEXdEXdEXdEXdEXdEXdEXdEXdEXdEfa,⬗/O:ke,e\V=o6I,ko͎keXPtvl6kynٌ~8k#Vqv쐝b}lvxa֞Y{ d9(6Y[fm:mLX7z)qؘ7{N쑜Asx.{Yl4*^W2k].{ gkA^Yd-s%k}XŻɳvOZ!R,׬زdڝ-k۲n-k?ݲx-ﱅﱅﱅﱍ3㰟5ט[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[6======kŶ==h>BB؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊؊8A<<<<<<<<<<<<v dccccccccccccccc 11111υusag湰g\yyyyyyyy.<<GɫѢG_|SђgJ{ ұWaS}c/u^MN䫣E_Ǯowf'ZF/]_-Gυm ђ?p3.?XHvV-r;  yd]a,wx8,1:-ɟE ,""""""b'pqqqq?o+*............:ŋ_]pEx)^tEx)^ lC7Ex)^tEx)^tEx)^tEx1NS x)^tEx)_w~q`^0O`l>}c '0O`l>}c '0O`lcƀcac@}6m0 `l&Mc6m0 `l?q.l0 `l&Mc;}v 0`l'Nc;v 0`l'Nc;v 0`l'Nc;v 0`l'^b{o%?\Sn endstream endobj startxref 427273 %%EOF DBI/build/stage23.rdb0000644000176200001440000106331714561352210013722 0ustar liggesusers |Y~&$@HHAH> U<H dD$@TCj[G[VZ-uZьxw=fڳc{ǖ=/2_(##Yu'3/ѤiZnmְmiZB=hMӯSK<_5#zm͌sѴu ̿0yb[7n\yo=7ـF ) _5*k\EbQXՑS˾ѴNƲg@/y[A7& oF[O m_N /5oߺ;Fڏ*_FJ ⶌLB>oڙ{F*gN/Ϫ̲X޵l[0ܱ˘7ywliEg= Cؽi>.{ml:UrnjcㇳO=|q*s)iPYiٚlݽ+o@w ?^[c!GsQ8¼io9n# 2Sƽ >*͝; 1DdFQ{^Dŭ5'1~x^{#p;luÌ 5ŒD*g}x)3]?h2 >} 3ɷ\C֓$rA1LSex0Nڰ` FÎ>߼7F$)ا~ejix*K> qqkju$'NfMHS,d~ [ԵARHfva*+Rgr1J*zo.X;u'nú\;~ X^}A**e_s&$<] yڲh0*w^io-ԓˍ*L`^hr9}7麟A<*&~$XA$Mc3R FêdiZP I\QϽ931'Zvl=LP*eRw oNeL۷rWȄg`ԤBe'W x 5%0!#؏j_>X ho 9[!>ÞvM 6Q9 KfIsk}=ߵY}t? 3*'w:7Z<4Ie+nt:V7RZWӗ6;aw־oep'ҙ-Nvwr bhSZ@[ GuSƛ7k'2l{}U69PBI3wcdr%YQ_)#A۰߮O;շAs漡OKO?#djjKA7a^x N>?  wՑib4)w;A0Go J Lq!tg-=I@ X ='5 ?ZeNhvZ)chyDIaۭ@.-^}q-j^)ax׬Ygk_t }.M3'i;1֦Y;:ʫ;knIYNhy뛮WfݜD8o}B}$y) IF7R (zSq']2a+lbùF jvR|-=`R ! [h܆rAl7$MvPr]+=KG¸ u(+z0ÌW5ȏ:'侁ADz/Jc#*h'' !s%وۀk]nb;Oa`c ?f /軚#~MuG:Iǖ1pr iʵ-qrr[QB૨mŮ-e>$J|//¾XH:`_rwI/"c3krnsf3-!{z_lh:>޳S3`| q2Ŭs;(2J '/o&0H)\V8.w 9L4L]ڞGZa:~[G1s4 5vG$pPQgz}8_ۅ&'B@OÖBЬsWM99 4u=n0G *e{:ܵ8djm+ Wr|oveܭ-_Ӓ&ug]g>h0Lis(blC+D WjY jXIňG6dL/Z)SPelcJ_ͅa}N*ҊX60G:퐥-QiE#4(^?g[^nLt83nޝ޹sVzN/#3"ͭRk\5:Ub.(ik@f9C2PxCis.PgWϻfХ43Zg&#ކ}[err[^,a3V6kAw0dsq Bv`U6U%H:-WW#It) C(hp,=|;t[M 0? n=Ѐ-g֓c씴'q-kk.ULY,S\-2Pņ\eD-yCaa$\%X%VGXR6"ٸ +Eh\#GjF"N\VY>}6Ӫr%>mUƲ"Wrvy8[^L+P\𷂂&;`uyOwvya5 v R;ȴsmQ< V2^@>)FWr&12+ xianpBȔ=6 aRfL +Wi+(K5w3F#X_W z5HBgRx+jYЬTH;%Lj'; X'0225saVh|q,'E\l,[$62ZY@ E Qk#2>}o+]|^KgұfjAL#\Y: qˋރ}O)փql@5xװ<3s:ԛk;`XaϚ i&\91F/HD}qδ+uIHCO} F~'blet16w!BM[#9H`^vPn|~D9ZbxcVJE+Fvu]L"%4Ouqؔxa[q^"8|P6|^"}x׊_VxY~$-uAw#l9{lԠWtNРَ=n8.D"=ȷjSh0)EGE"kz^~k/nrx|<˦'v 0| Sn-߮,إp/貦jV J6\) ޝpMҹPjAͰKOtz<㮘"Yx)pMU~U)ۆ9LÔVDh%o.;^ͼt[Օ{ʅt`w^.ዄݰ&DD?#튰~Y+L;:H;˝ ;N􆻋}An@= P!lݖ|&\(ܯu^bݒ,侁A1#Լ  <˱LO"nYUVia(M fw8^x pۑe oAzqv^RHJVbPҰZo7vs&~4f .M9JCEA2Y:Α$%w*N7SƪT #x]`I$AA_0u:A/ʟ"՝lº-J9P"%Mo _[oŴHWƔ{`=zrQ܅J RY?}0ΌFT2f3|h&*bRY˼ҬksNVwE3]Rߠ]bΝmϐV}*VlsUmmz7rzs49Sevp,7rNjb_ &qJ.)$-ȹPuU;G`IF2* aʹJ f[WϯӼ$ Ht~nf{ p3u߽UulvT!kv– %;];G[٨pyzޥ`x! ZtxPQȡܣEȇP>.[=KBosWF|i+%$h?["T˞3]ˏ_Y5NzR>VUDgx WU8lU?< [DXB TW|7=gp+/[R|,Aoߺ;F-f P;W] K Ig\Qx<3,i{mꩂn߱MeVnIl| >%2%ߠݲ"qyO a;vi^JGګ&cBu!`R]-/π a6ejke:$MsHդƱs+NDGQp^ˣ«z=[c:r pcSpSJi\x'\{PO {K6n=vt ݞQI{` }D赠%F.v166᱾8ƃi5? ݔDk-?EbLxk_TSY QY s`tOIE_-U7F}*}QYe=%o`N}o bO (^NJWb{)g5oRO1޹ ae%}RXCC:H5ӥs҃CI0N݅]+͜Gܴ94>T,|>gzSYD&^(+f9U\~gj'U q(=]9pphX7wiֆ$#<4=_4|3Z^"`i(篂bӊx, x~ܾgőa v4LR"O; C]Y=! ZTv_}A v? f$3JK== rx$:!K׵h>FzӾ[a.gMx:/@v*莤sWmԢ -D vKA+6uغBUؿ TLNBPEe׍+}(vo}(ep)& %߇<z!Ck"L\߇< ޫ\-efNUv)Jng"JvSoA={P -ήR2 Hm-ъ!\`Eې&a=+R?]E G ߸E$Q{y$I [w~y.M;<$솭'<7% ]dN&^O Q.t( Y.ȝn-h Q.FXr%=^BݔI]yn UTwHw^$-Tk˪twVY:@]NnunTaZDIU0Vä-5ӿ蔝u8>I`P$a]x" L}(M<֮o y`K~IPKtCHZ?,%:!$CB)2`h@iNI O]i@)dh-;[!DI$Bud"'$$ti{` '?" IX(&#(=P ]4>[nJkV QV+,C|c'֮lz+:IO?O:ς 'ZUVY?2 Z͂BaL^Q Tz+GP叒U菠Y?*TSבx%aBչS?mSVFM6NПA-ڵ**3(ϐ:©#R"5>IXX4N$مO$ [rI}.`7lkUwIBugIwzWVF"a9hjbUD#qGRD(C:l"%{D:,{P%aUuDv-=% *5Ȫ߇& l>4IXftl>467|Q"_@%Zy" L P̓=5HoR02N ]&u/˿u/QHRKt_Bw_V˭#2e Nmh46J ӿBJU&|:+hp|N^>ts&еĎ0Qviu'DIX{}I"]ҿ2ZKt̿<}O_C<~(z{ 9jՔ<:^$0*[E#XJΎ189#- &MeOgc QUkNܙPHb#ZX*~a:Sg߿DIhoWڣ+}{HGoe~ f|pvf _\?3񊿴cfO,t݌o?gSCJ>Ϙ3_\K3^J|yW*("Kpُ/)~g N?dlo#%\!g[J?2oX9#^pcn.O{6hbd写<*eqf:s+>*ҺY3V#[g6Tg>cSu{?#ڙ4+ S`^0 rTu8f .tw1!L o]Y֯t_5ُ9R晠>3]3(Ċmw0F<+ecÌo9'%Բ_"_=e|L`CedE3v %ݹH.-_jj"n2e Үb_"WͼKnZ7^XY p| _wU.a+bMABM5ZZhPVRKŗ󜂛"eYɲI=x񼙶 V?+^K+oEk\Zd,{V.]鲦dLV~Gt* _vZmyj.-:nF,j&a]V+kg:_cE[ ڕ}Y^`gRNB>W-tiܕ.Wֺ) N=@,Ȫ̲yk+"}\ʙ/v8?䂦o.',zx67O2[6?Ue W+1xw˶?ߎn&̰'S+y89obbb:05`OVEdCΖFrHn9>ܰC-J t Foߺ;Fڏ/|rƮ[)pƮ%BAyMf?=:Jرѣ#;شޘ7gtf,gyK^ж#˻BЄlP_˼;4t}|d3ߞzY{ش?wR66fcƱ'J]8U` Wʊ|.i!y 1 >{r{zppEu@fg`3W_x¢Jq|yѝ/sA?4x'?#;{NP޺33QV_s&0}/az+)$I\~_p3xs&GGT{;;Zs2xiwWLf7`PAG+^Ht+駂+UބC2z4ŒR^4~TgpZ9dĴ`%/4mg*{v)t?4F>XYVT]{iz[7դ@P==P/e%N 趫HsI}?ޘp09;yK[>/q0,SQ>_"ꩰoNQ^;.r%&3wn E챲RR(`BYZJeˊk%u/͚ =ㄷ˧抪Z!Knܸr"aadCW^)MaO ]U+/pQn{A zuu,=5yN[`SsXw 8? kxQ:U=n@ĈG2Y^YYV{XjoX@ 룣׷6"_BaBŔZb:I hcE#(Ͳt6E?RD--([ʶ P =H-[B8{H`ԝ0`ݰnxkǃ'V`_ʶ*'kׇ8 bopcwo^>\m, VO#{aUU67G"3y$: ~({hKTBo x)xOa64|af-(q;$&[ƨޜB~P:!P ׻V= _QXV'e^}MI=LxÄa?ZG["O7\sB |=/>#HGm,Zr"3*̢ HKS=/ZR!:e/_qxӮ3H_oΎT"Jc#a*=TꯖN؝/[ [hV/} X!O XЦ5S3r9A&2܍71-moNNU[~\mv֚~qC<J(cQvM{I d ܒ`䨯i moקhBہѠTy9s''z_2 EW қk/v'`OHgwOܟfOR h(1UUC-lX7aJ N luUK,k%>T"``ؙU Nl߄4ւita]w!UoQ;l3q *l>Ցib4)w;A0G3Q*a"<20n`7$~-xс6s-O-v 6޼-[8 mͪa;v0'?= jp wσ8$O&(Px+/?So"aZ]#? ZWԝQ1$_C0'i;1֦^;:ʫD{ V+[AFM+_" y"7>\{Ew!>Q(z@+|ok;\խe FlA2֧䬬^JQw$gˆ[xcNof|jUN+ށ}f]|0+{X]P֋B0y'}!Z{_K (zjE_ҒZE[3ED?P'q}ؿq5am$M)xd2̑+M-{kߕ&w}z0,~-m2M[~*[oIHQVcKdw/ELKh.i[)_W(U&zM/~xˊz"ހ}CZ 6x |Cv[ڻpvox ´YkY]ĈYu*J2YF](4l芿<[H|m*?BIUoՃC7+Oy>1ǰKjuac-qWQ[a{6l~[ 8=q(ذ٦It9Wr|6C/n=0lEiZS2T3o *EhGqK<^46: yA 1QeWxבPe!J ._W<հrRqRMB6#] I ?V1#JiLe1(,sA!%Iq[Љ#Us1lDW[*WVuRt`վ&wہ:l]:V#nWrf2V66 v{+7̧ [7]7kX95?..nd{zNVj0\Ǩ"93=÷\iTfO.eq;c+s([h']˃װiKw!y#Bfo$VV$D\cC*W Q.&*Mu1[{ttΦ8eyI;r -Cq7mB'0q73*/g` G`?;[@!d4~hSwq"*!Mr Nu}^;*!70(>Ftl$Scթt^JQ]P~_6ňFu*8̊N2fRHջw^У./ ԵȺ[Zt8.giYY޷ U鷹!y#"t# IӽBzbHb%0KfMoþ-V-!Z R9"-Q>V pX" ^Ԍ.~VZ*$>ʄƊ;1,#v^j@P5i;-ue"nO1.94%SKp_+@/.=)22(4$4ZrӴZ2逭ز-Q; r2͓ qaDصɑ^UBCmOA5૰$ &^[BlY{}-fR*M MWK A-9c 5!k+C2ڤ+1-tRN#wۀaΠP@ Oz{`m,˓M<}0<[xQҋf:LFVˡaYg^5Du[Ι$oj`jב+M5:g* (* 7/Z"ܢI&Wh]#vq~|# [l}SH!J١86$O,x4vL )k6;`^n7 l6nN@A˄ C&Z!l)+Pm&D  f8^nn8gycI*z SB7<WJ[H[J nl3;nz+[3Aw;n1xA+ΠJAkyxIFRkr\Q\]0TaG <7 oGcְF8tàTiu7L:Α$%xJTi~$_;( nlo*#Tï Գ3,^VJ]^U,E2GȜM<ˇJK5YRwX,"ܩQأɥH7V¹z: :g`eÚTIML }XfիM!iA=}c_}$feP8byhA+,v5p7Q`5~B-$TW7Pzp~bP0i:Km$~m48̀!s:q '4Q-TMM`'lZw&;];eGېpyzޥu`vx!:xuxPQȡ=G!s%1\| $h?[0deϙGG9~aWVMmϼU}U;<[~UEOO>\7 Bu%9,oy`p+/[O!_>H,Aoߺ;F[櫖mb [+ [( b$3I{+舯4=6T^&?4\+(9 햝 B]ש6I'/ Ƅꎥ'YU5*m۔U7s\7 Xur iQMja='Etgm< }-Y^>l I'`cz^) 6 |WU$~Qin}r U:O>*?&<>"MZxsYHVԤϙC8!s@P-3E[bLx[33Mq> 怫`KHѪΙT|6皅:Bxv0*ҹء/Z)^w pPyӝ3N}0$qs!wBa BdXE<'j-rxZ+ߛtܟaP^z҃@ՓuFW'+~rajm^ރ-J4}N_އ}ś~ -Ӷ'86z\~TB{rj᭠uJē4@uJE^TJCdP Wj4[a־B$w[aoΔҨ<zUk&y,a5c3MI:/c8lqEnZ iq3u1(&p lNUppUQ\n>!Y.}uj9>Q<5lzQ:U+OiQ#E> kޤ>E쟾{z:w疂!W_ 1h>e?i5pL· g'< w⤛ 6Ƞ˖,o})EPYi4tt}o.k5?GI q(=V&&"'`h4_uY*@}H+ $jȖC#~%aS>8HʕO$="͹iŐYp"%ͯ=ly`N}da+[?9$U}^:nBi#1k_ QqTiRkG70(ޑR 짴h+F/Ӿ[./$gMΦ{:// `IsetG9㽃觵hOh(*c @^O#+f?m^"h" ~b -b g n7f.n vOJ{}+Ut9)~b "Tz+PU/Y_*XSK%HKآ̾Li~ (<2%:pl6O_4 aAW+^ӮXMH{KyZg!IB' $g!In Zny]@FdUynf'J8DsȜM0 @9QT9(;Z"a{9c0J{U)LFHw^?EveI:;a,UP$al[(U8?jt=a/@%:L:~YC0Jz/O0iK&u~*ҦQ8m$5JzRX>~$-(ׁRS54~[v%0I_( :D N2DIXI&$ӔYNz E&e(=P" LP$a={XhP}^<*]»k״DϯA_\}~ 5 JzVX%(%'DgA?*?< !,PZ}gA?2 ng"Ngyu*PЯC_OV_*^g~zMF>\G7 Jo@%Z7 ohm俁 |l_2[4k)UT+P uSGRDk)|*(;?v;뛙i MJ]oB;a*O"솭r> M;NƯO(Ի>2-0lŪ[淐8‰#)R" [&[H`?ZygAǯB ~$h&8ZU% *5ȪIoCum@0f䷵67|Q"A%kZy" L5P̓=5HoR83N߁. :;Z|;Z[G]~G֑|G֑m(wjR.]M2N "Lt]hp|N^>ts&еĎ$Lp{%aV{" Lp{%a=%tIu-_2]=ZbeDģ)hIUSxI:~#*[E#XJΎ89MȳISHԦcdU<ꚪw&& I{D Ko5Lg*>^['}т_in ݺGH@=%I?Y6X޵؂e\t̻cKsOݧO.O>O=_H My'pkcө>f?=~XP. {le87e q97xt:LRkT \8:ϗvdơf9îҭ7ܬ$@ obR֯h߻:['7xw =[ʤ,LO eRl_(H ~iMEyުʅX5*kQWW:# oL3#Eftr֧a8(mK}^Eӓ_`J-(qzpebNkIfNU:W][soaO]sjҍBIS#gB2WjDpZHe oe,ifj|Y lݞ@07yU.|!ģ(_S,+fy{f&ht/'89Fx )[~REǓ=z&#{^N9FdAx$+*݃ G ptt?FFdae[U;es\q"7Euh}ZY)NS=t_}? 3emT &ģlRfUf}6x$j Qɍ @li2N:.(~K:و.oM4:l]aIӊ%{#FBԌdXMK4׳#Z1ݱM̅C^@=o3hW q_ P]%RkPTZ.-wa NN؝/ n=p'ҙi#^.;1] ]ls˽EկvN^{fcA+vl#)wL3'iU {k*'1jʏ?ߠ*(zb^UCZRIE Fl?MJX#η~G|_`ei ; Eߗr$˼a[B._T\>f ^LJ{+*umΰq::p=L:)w9tW鐨Dc\Q4s.Xဪ{6}To 睪p )rh,lad ,3ԱX"`{hɤ L%+1+%|;D ~8 {XaTyzl= "Պph 5[w`13밯+ HF))in9s/_ks?LC&#_ u_o-iBCDN~#BIBӆL=mrA+\dƙi 9#mE!jRݑףeؗbb{PinzULdvNb ؃BHX*--KRC0̲[[D`E/x/H !*U&D FeAԡRJ+e+a -v짭)3#՘?ErpԦLQDk?p _?j$H P = Jy/w`վڋ/n*ѭB18 <rnA\m#؏Ql$\ 7418 'Ҳ& BGW?y-'=f3g>P{ѐn l*ݴ{z!E5Rχ_:!\Kҵ'N[ݰkr .iPGy%CTva+|x$tR!Z+|b$cIܭ;q`iJ/T}f'pq슿LN׾ L|ozwYՂ54lb"*,X۩`[sf0J lZ8OVe-Elq^}QYUh 췒ɣKa|0G6b=vrNnF߭ F1S /M,M^DjNhM9(晌]+Wރ:$hQ(50GCM QT #~s:`T}e3Gń`o.egt;n(92V*GiK%oFA^}E 6.X.px(VfMiv}v"-yI~$Q [K i8{,}H:wp$qAQ-Yb̔^`?d2e'pPءFMHKKO[WX˰Nwpmx/_e_mJn:(KVΫ0^&kx`#ɝV9qist޳9D45a"dC;eӎh 0',X'%݀Ji7gygnLԝ\ЈYR rWnMYƸ>-7R0@dž^wj 1Q 'I'UPV6(L0';I8 {T"z5vZҟ\%LdYiB 8:luU lo&KvF1|y2z<h dD; |{ҢmޖI~'yE"k:~ە͙5 Oڝ_'KX`))H]@k =.-a=:h9\&[Zi+4o#j v<})苆a4U)GB7f(zAJ3dKQG}5,x&w8dDwtZ 9'Hn122`9:>ʝYlΤ.E@"vlAV&H_ހ-]go WSOGǰKt M7I[;Y}s?FmdW+BU7n> N ~2k–6=lv?:9n!\ʷS&(exhUP.}{ 6o j5aNnt+z"W$/>Rڅ5;3~:HtZ7]t'Ehn13[ s$exsQ^}1(CT3n+g)1[hQW^rry{: vxd:-,s1M2܊_}= r [`H^n{[HShD"ІmKSGNiS=PjTOqM2[Onzu5}`fM%Z{CD}J WI-D<`k!r |e{jY3=c~0`a [a#؏ywbkC!0wR;`{hO kT^+ ,mpNPjhgʧIm澙, <%%; {l/ݢq{q ͆/RdpCmFFn:/,C 21$_dʖ1k]hB/ǟ&;!%aYkؚIjxp >AxvB['˹ 0OI>kGqv`f./Ι6ڱ~r1ى@g?f0,DlT2B7}Jܬ݇`>ݠ(qƂa f,:Lܲ"::l*&cz!TdԧQa/0gx~F7x4npk1c%$&P k1X53 7㰅6V7[&˨ WIJ<DFr < [a?He[/䗍_Sa_6^dQk0q`j~p~ 2 /wR8lѠ Xln`cMgLAXuji,\x]SaTY']:;*!ZkӌiM+Cx5r EIqO*xc;M/p#bOb UeA(i4y#~>ӢQ$x1$?}5эq$.22:I܃kO)Dk*OV&(@ń)iB1QDm#-'(Q=bDm xd:2[iUWQl ~P1>-ŗ7oksE+zԈX=>P#FthöI5\TgG#>ep<{ەR ^-E$m\F^zpPZ񗻀a_}"wۀ`o/R2 l8ɻE\ZBy"g?=D\},PA ]Dn?6GY# ]>DF`"rw XEVE@!{Ta,t'EC& C퓝 +1Er %S nKP;HMOV8J6Nµ_n-Tr =)Z1"g&lSYHD֢E` u+zHF'ݰNKv2vorO _HF?l͉W` {篬eĉ l{_>["Az܍'LŢ'Vy" ΉYp L(W0/ 0cv;x_IW`ˇt1ԯ'(l9Țl!jS1ԯ^TC_<|%v ܍C?D Mig~ ŇvԜI]<; l:6W. L^m囵a]I:v x&2}{d9K /2DFS6r_i/Q9"v9*Gd/oh*/&xTk(|<*Gku?*!J &؛J-eG> <*G/Q9b4?*7$;3u-:cGy7xQ4C8{9甴GWuدKYd1rJ-Pw ѫѝ1X*"簅wJD l ը|8[A=hm0 | ZV(vs}npVσĠ 2$ $w;=K}В(/j(CT1n+ l5;` WWl N;ޅpD$p vB>${NcL:Ö,]|ty:Lb?Ë>!Z,v:D$>}G߅K!28 {4R{JSKh{ D(=$J<%vH5_CcxHףRbDd _C R/!Qu19$JTcC%yH%7j/^&xH]ZZw~T$B=,V?$u-`Γ(J,^Q8hR mjX9*KAUqR]-)v M1 3 bO)pP2G턨;` )&wwBUR)N^GmayѩpF>C-CNhN8m,CPCp\8v[b? -Ͽ:Aq?1>}$$ `isܩ' CP6gs*UÏGJsvx*n-b( wj)X)~/hKbD9 b)@p}Ts!9*)S7>wwA |o-D͟9Zkuun^&`3wr:fb2d`+Vi"[)M>/iCdT}F+t/^ؽOQ`DVslUNVX٬tR 0&<[h~`Puo 9hÌN[L8{\>aj˛i+k v{1w|`@oN+0-T7K[N942KႱ+(-~F,\٦"*>lB+~"pʕU}8[hAG#x^1?1w#Qyue߅Kֳ\$MF XeQw&m2)c-cM2Ƙl.$q dVu4JY{'zzV &80&VI(t/Z.,z9H}V8 ӢJOy6niܢs&?aG,ށ%jG`I뻙[Nl5b/VyQX?AI!<[ɲ"=<r_:Oga'Ny| x]eN`?; `D6qwW:𛰿zeA? ~  Uؿ|?A<4N (g{{eTFB<[`?gA dҕ":{C)fJVg̢9õT"R/ Mҍ `LXRťَmzCz">Fx %iqMq$ l"M`B9ky;_q?P kD>섢˭˰/+i~Pܽ|[>z}2xKQx8[,qMGZlH/͊|#-¶TF[Z(CC{Zw5;Fj޴Z;Q-7~녦.Idr$5B:GuM7e lW͠@LfagőYH3f)2G|ȍqY!:U>۾=I?Pq[)˓Xhk*cym.]JZJ^!6^hF>E^b8[h^XD26U&'=[h_haOKv:w"] [}.#vlne{~bqS4ޟ̽LrwBR''Z#A:ZUUYOꖻ蜩.C<U]+>BMȀ(ovVR#/_5M|O`a'NIؓUr#^tx[Sߢ]gw` fh~] w` 'JEX5mv2Yv ~\Ebl֦ l#^r 04[&˨ aJCGj_x]#(l} Lj 1UW_8 d-oէ-$ o~2D, \s n P ?25:2M[ 8=<=L{(Ho-<[UFFR]#4l;`hپ9kr7 [ʪ]D!lᘚ|9t7shPG8 | <_ %^&L=.^CKHaB-?4:t֦%lΤFoXpP2-`dmݰ/MZ-Zr|+jTlwx iJj]'r;,Q9 < l2sx9j2%ēTe_Db+b֦2ݚIjx|SU \Fm,.|pVZ_l-T^r<[65*8< [W/\]+)S9k7Tr׫u(za}jW)(-N}xjXK9aO FDb8{0VEp#"1 ݫ5_lV9fRgΉlD$Ga*FD6;sQ2iUB_8Ɉv m{ ll_iV޶_G-DR^Kk`fXv%N`%5bp.@5` }pC@S6FxPD4#wg`_7l!OZ3AEQx+]b: OS~?Oby.x {|q EE Q ߄ GoˋCS, & k``?O hص/aX E 9n qu@u@3Dm0섶M fn'vb#o]3(lMb]p 8[++$/F6VPI۰Jd@5MpMc~8ʱ͠+zt{x[wK$l)6G_X9jr 7'TT֧) +uh"l0 tdu3/RS3>(hU+Hx WV6 G]7Ѹ|vjQ/,Ƅ'9 ?WZ:~)UV0 < t?gp7lmG58Acj_]C%&B VgI"vxdr898EȤ{) 'ZOl/q9qj` |^o}~2z,6]>."lLb :Du aw2N}TWuKO]ON-)bw?-t|O￐rO _ /H` G*[˛㰅fJҿ`px:J 2g)5?of-!`F8[h&, lqi‹+~y xФ)_"wCkɏw+E$^ބ}Sp1xӁyIt\*a)3_/-eQng4‹/*h[x4GKēToǛ-7 _?2n'8:JIR2%gplHB/0Ri"urQ `:gK )jȝ[ &a V~ڐ;x|dބ-ԆU4{^$pյ' R4oH{AＣAl.UÖ}Kla뵯>B`_iBơ{Bڽ}dC~- [hPFu7Ԓ, 4>o!&ݰVOw Zv:WP~k?<^$V#;r!l*^* ttz -T&Ep&]pl>;=e١=A^< [vt ;P`-A&4BR(ixG%Ts@'C'h:PML#S0R |8I{㰅=/^i^zL]@uS̄ rU4UE[_(B9+CU[b6< ;3>nx|Xc^MI&qW9fc㱸۱G4lr7TFxye呪2Zp -ٿF ӍF:m}\j1 FvViސ75Gx I6꾤`4/ v|KU+^^_p#xO MevNN㥰wHML1`%:'ga}%w`lpk^}E@ &٢"~(N^WGT4_Yv[yu CaijVq1SNb FFb!n`_d+r%#[l| 4Ү[4#g0Bf{g"[AWh*-.zΤCoa k0)oF tU ZhY||uxB3|!WVJYLz2zd+X\;'$px+%B9m@h*al: 4t`(*$v/@--B#[pqRJ~G ')a6Bfc9fJ j&(Fl0#̍ sc9fΙFNT 0Aan07*p8tV7BЪ.tnnV7WQV7`n7A1-`E§MP+aڑ|5Ju0~$i ^L[FN/O)*Y OHIޜnsd%Ox\krT\6d 1%؎^֌F M>Z>r vo);8 BJn Kߢږ=]6C[`7--@PqZwQ p+6e E#Ic՜i _]PpB P!jrT=F}i!`cV#Bucͺo͛o&dPl!nFW[˱&=i&ѭ֗F[ѭ(CFQF7flHU p;D*>TF bl {Qt蜓?A0v 7vhp/,tn<(4C!Z\'Wq$,Duž) 3L }VekpTtwB;k_G_ K:_yTIy`(el*o޿~ZJUBTiAdP-Vp`/#VRFݽs]$A]MT݂d![u5:ޣx ^ÑTM!iA=}-vT/wDXyr(SV%fMJ]a @JXsk:Q%<3 ҳyg}a'ag} %Ty}Q:U[40~U VVtk4= O sPpi)2ܒ>CC Yӟ^0]/~vR?:z(<\(N F h_6tAw8{SYD؅D ±i&ؾ7EgN&gK?< ilx!9U`Ve!m g?= 3#z&u):<QNLD884Ơ4_XvhCu^蕮pOt{tH -IJ\ 4r&z cT\}6E'8hBSjKWVJy(;q Ni?W_tO?_u#vWo6}#7s9ӏ")R}8Ƽp82xd?$ï~04a.DuA\zHxFS1%&0UJO0$D?0:1scTTgN֛S7|ݱUOW}!$aRVD!Q^*{WVVwiS= z{I&O_Zi@:=A?ϧҟ SY*WBᅄI.oG*hCT4>Fp(x*>lq&6̊^rLi~!843˖OR tA]LB'GhOut'3?9RrFw0~e9z_/^ ds!# %yCzU}[v2 ES'@hCJT)Ќ'8x+MNOM2#+NՍn]tq>PS=nVQ VҬz01axOz^1$bz"vK47g|_94Rz+x/;x;O6H4!ej2١'?KpR`uQiѹ_tD V= e1)8W҂rZ*s{ ڭYOWI8s*FS*Z]価Wi*KjJjd?u+QKSc;"KmIEč U"q-7 .x 0Z܍‘B߀BߨB߀BߨB7[0oOY(N43oBo\4 YwMMM半}3*!*h#f9ɽm&/-hP]m;ʧͷM |E~m#VpE||[K4Pۚ8|;E;!-Gu u UV:7Pg4#x)ؼ(tFK9hu|DYb(O ]mŜ5'GP#$WhrT)Ө|$U(ʖud^{>J @{RlB*n1$J *ǐ(.HT~V@D`7'*} >F]rK1JcQ}.94_>D$+'zK $$Y>DYO '5Ljʣ[vn;(aM@uhz'*!&8V߉wb&6@94NIX<&87NC`@4d Gw>:rBDSZ-| Miunn`-| %g OV뻖=I1 DPhZ|S:*!&8ߔBӚ&$`?I 5#IC_%:)KS=ڮ|dQ`"ʔPgQ P MO,_ڞ~i7Úlk,A`m? aֵ' P(a=W/O֖y$Ns(a3sVd:wa.*!nơ襹B,iAZZ@P[Rz.~`M$ޅD yx% Lp]H]3+[Bk3u$Lp)IXש[" Lp)Iuws侻4RvցI,9YyT:dTi4ZJ<$ *m(J j5܏@ GwMºG';ZbhN`V23y4%:㑇@Zg<@70<JX|g%6 *%nƣ)YBV<]ȓT˓J5s|t!OBjP'ꀯ*֒h%:pOd V嵛4!Q_Kt؇D}Γ~T6BLp؇D}~T4BԵZM739 ONSg$ } dIݑ|Vg,h*Q변Y-sXߜ, 0lVDiNI^`&1'PHu^T {J?IXDjG@v ;QZǖXx#K%h.-%hº.o]7 z.o^T}QKQg{P'aKAZ҉@'0N.SRT'tD߇J<LP)a=?vǭ"s4 - O@uDT&CLp'Ddz GoLyN˫s''de}e\aN~ҢǟBlRZ<7fޯy PZ1w} ?299NF.}EIq1KF.ks0~Rw7'ϟ@F d d^d99"J?S $?@.}xqA}(Njά3xmMh-J{w[E?G )qM!^˻BЕ[0ܱ˘7ywliEg= Cؽi>.{ml:UrnjcㇳO= ڙ Rs OsŜZJd4OF*`SK<_ Jؑ =f郹Knܸr^X;E6+]9}˸6(W젛q3f#1 a4~w}i?VcGCM˝KѼkoN\Qr*_Q[݄9= 8 b>v4<3eIh|jec9p&=&͛;!Ш3J՘=2}Z4&l.¬nv n?O*_vBUF6B T#g^kaTƐ Q1G.͙駺 wtQ;/_qWO j%7R9˛#a+>szd䳏ܟf`5(jSx᳑A<ɖ0rֹk6Ym١i']ܸB`_z !兗4sj9Vح(R=j}ƒ&_IW#Ij``ceZ*цF9yo>p|c|2= hF1'iT_UԠIMj2Bg?gھf4 w6t43 e9,;li4Wd3k9/R/+dLSWX^_WvvJp7"T CwPI؄`n[ɑ^`bߞdlbP~lF\сG+cC+'sWmj9 -4#a$Iu9w\ [ϑWaZ5e9!*MVɓׁa?Γaӣ"1d2ct4þϻN޵ +}'BL>9)QUA1cW}iCc.8}0xj=@ˆAj\(72eo)9*ބndGeRI@#X,OkrӡAF,t\н`ezΙըOeuNnJixdVvD[Wxkx{*Φ a##-Af79vHΌO>L O>)3;t]+U}Дmt xuM)laݕkrv]놙#W]Ck+@kdPladn=]avy_v}"^ -TUgJ6x"m]w^˛Cj_v2x:щa=ru-i4 E˟s_]/e6 Hs\'Zi ]>cf :rcQ<ҖC'o^ٞ 7ىJxeobg偗iq٠Sx5;Ǽ!t}7i9e#fH0TwkDUcaRrM/Jjf(Y,XY}5,׼i̛^HwЭz~o!}ŬO/~vR?:z(l.|}y&un>7*򦲼Ї'Ժi&ؾ73Zz 3?Sjf$,x$y>GY(M_hVQ}U5ysq&uʹeHGju74- i'eDK/4\H@g۪cʪo.$)QqA-vTRDC+̓w>qAH'V᭮efSv7 EkPV}mٙ}][av-f6v42'rDx]Z:QhKKN#ȕDIX!^b%=^mEJuէнɊ`(IXt>GHzVX-ny~/9U \+Aڊ`ɩumE0Zt $dS$ߟ{^3Gۯ6>ʲ%Nt V(ZLk Pd>}g9eWgO.ZeOPjp/= Xa A$ҎD d&z餝)}B!bMZ1eZ ܭB!=^mN1٨jq@ q :'!|R:vLx$SUפa)i ;i#S(לw|sHhN ~ٔ8wHf (F+ *!*YfΛO縩Ai1ݎԒN0]pi&8ꄬ(g0>y@aݵJ͓ q-Zq|Wr|ms6֕9kP|h7q'bgѼ=pN.#/@}8{Jx~xGa?p7VD+T ٥cB6u2Gx>*S<W>Qj`P׈<#q0YfRs)A 3`OEc[ϱB\(q<",ᬵ`F!) bZ0\ 0Ɋz/}\Uu%.D!Gh/]luH(uXB /¬KAƸۉ>' [S1Q )}Rep=Hʼ0oqrfS7FWsw e_a)l8 0> T밯+L*}Ar7F]2&;ʥeSQ~^7O2h?Z-e}{)N߃{*OHhځbhBW$۵bZqQR"fO&S'KX` T.)اj_]|8qi sVzNB.{lJ[a}3=O_r aCihܣs(uǍ%^lhJu}i%sƂN XRW|)ꈳF 6 i'8iC 1M/D,oNc>-T"v췒oM 7` u+Y۰߮} HNg` KK΅Gǰd75:"9g?J &؛J ֬m9؟IY#Ff.>W+BU㋄ z*êa -:hM3sO9)qˈ i- 7MPlfPV5eV9G0=K|l$U-}ðyI0n24^,zz>g͹(V/}6L8lҍ^!=Glذ~u֜FJ e^0T[aoK}L ڀaѩ { d.`H̐=oXϘ`tnˮ%o䮎b/"GlQ]ϸg\`i&{ƫs0oSvq;<\2I1%=w'\# QtfJ` >W8Q8hG (2XFigLhpFT4` MU<;dhgOҹx9c4,r(H8ˠK(޹4%Fͳ2WY7L@Tآ'^0438-UUnxO3 i{*ʝf?}% 苴|1Gp;5$dvJmWpԞ~6[(:?^fO(sB§5H+~8ړ1CBc7 ߔ!f ŇvԜI]<; lC-. L^m5o)=}{deK`Gk(biee6ĉy_^81D6c'8N Y`qb^G#gX{(1`o*=췔ʼn/&'5_81h('fHvf &'&KX7 nB3Ǔids ʝ+rpʥ* k-?Tx1 0 ;sKbvhINjJCw4x1Wiϙ7 tK6҈v2m ]O"T6;8lJYREx=ZokΜQؚxCiua{ѠC"p T2ͼ`С;>9甴GVJ&w#a :{D o\R D]d*@AtgwLE*0"簅bID y$th:*!ÖoE— he2iWqC6Z_Cc0CnG{^E-Cl% :tBCU[?EBG\/< Po}r}c)cC#| vcr ||xCva>eEX]aMsQ(D@ Nw}t?*'!K>z꣡DEG! M."*M-E D(=$J<%vH5_CcxHn!7A<$HD(Qi*/<$Jvk;$J &絗[9$J,o_L(%218$vT$BL <o`$X&#t G1R FXhUQY-)v ȦbO2+:؀kC)l}s>G#5'vk/2Bxxtp)v-{"=,, `ꁕ$ -׌Aw)9gvy፵U'# TB2N6-!&ńX '`'p-)XZa݈'@|?6ɍG-x{&Y.}uH_NծE3D1Qq[ 4M/ow[?t--@А>HbL 58  w-͜^6>A,o"xq`pl8V^ N&g#;K;~fD/9BOLD884Ơ4?M$#<PocTS ^zuAݽrʥ{a[;B[OEr01=BT&|Ǩ&/ǰA q{da v8O}y_X'jOhQN [h툿vPnn(K8st0?4q}?諲t>E1L]9ՋnY6]+M?rW=Q:ya?ES-?-$?rнm#p7VX@+اɬbI46* l-)plKL7; GBu B$Ŷ&4);p2 DML 3%aztwVYeWg JݰlI`/^m8gGBYp;l$;j1>m~z$T['K67 jACδhj*9QT9MmSAkU!N j8VUgKOS^H}u(ׁ{`U嵛-dIl oiu-ȷDgY~KlPDrY<(BU^YRE M~}.`&qg >$Ts_7Pxϭ/Ldm`آCXE߆0iNI^`&qhO߆0 uغs&= IƯ!bT1-jy[WZZ-# ~]ZTz ۵5]#D`;0uB\ ڭklʤDWr=-Ax=ddO߃" ` MHwkwI:6įC N:IX׉c"Ե&$1nU߀.CKtf7Kº`3s]rfLu(z{4rSҿs'oF%xپ2v0'kQ4c]ύ}0gTktƍ+7+i錅7{cĹmwWty߻:r*pÏqg?l\Q0Ao9 Fb&̧Äi26/tݩ7~,~釚;ke3yުʕ\5*kU֡aOKb>v yόtqwꖭObp 4o##@C8J++0[Elv"̪qmcw-'/~;x^|t#pluÌ 5RD*c(ʘ^w>gS{%]!{¬-?W G?"#U /JdAx$-˃ZQ Q-;"-gVK܈oʺqIecE#( tZA<*U7k]: i.4`N]3`=k=:}k)8ZGaVV6+w1AVx<|YHI(Y9_Ygi9$M)xj EĨ6jOYNh_#pg烢bf;9Or*aFxD0G7J;IOթЂ"\GM>mdPYhjQ&pZTYn:wIe `$\Ӎ(E5M^j[*[P醯|Z0]ttONIzC?-4S3<[ll[NKlV-4!-G`J&[FǥM\P7cUe5دI$8y2rR|!QأҜݛ3yLw觚[aoz`; b-z'^&ݟLt`Hg˾bN;ou\09irM_4q'.R_CQdyzW |"JCXïDkXuU?Ww7꯴3vq8)^ހ}C_>|/n췤݂3g҂2BU5inkAzt=ߨ D$ځ{aUIsk}ɧWGaM&>&O†ӱsKzqu]q-ط v\c|7yQ)8ñD`} <&7#w@u}(Á<42zʦSFi[܉ m}R?=YHLaOKd! ISA6LSLGٲ-2r{A9S v\e=VMRf\Rnn:-t21LoN6Qf1kL/Sz+bw0`f愵a.BޜSe9c!(/>oش}yѣ?Zbnmx:ػ0/ĄnQBM#=W.Q2rIb<ҥ},ve7 S[%ÚiX[1>}WpJ[ARVh_f-NPnQoQ(sbu:lV*獓BiD밯~Mƀ7` -YA=!7w` <*Ֆ(ÃBz~^7O2h?Z-e}{)N߃hc iA;`Qg`Fw9y F]+vͥh% {B< d2%yR8>RR`'}mpϰ8gtL+dV [ƈ}3=O_r aHJ/ᴒY5xOM+юvԩ8zQG}5,x&w 8DP{qG7` C 4m^0YޜP -TìZ61wHn߂-k l, }x#go~5 ;-g| 4Mw͠yoabzDeMLPRsM73)k,vW+BUW+Eve5iLS=ܡ`v?:9n!b)NNv ʝժSŽ{F^2WGlTm12?wD>V ݯI_l} k-,uvBie1>d3o'ǀoj՞Ӣv}ETl^ VzV^P];ҰxS y.:VlWѢs5BGkgrb:<~u* Tnx\91 v-zsD)pbr ѹr8{NhVxh`/ա)"߇4p2)⮎b/"Fq[YX|Q;` VWX<8}.E\p Q7׾gA:` )Kh*RieB/ОomD"ІmKSGQА6SFEyYL:l=Yqk7k*|hJ*=}vZ~ xB WzjYӏ6~0(?\ [a#؏ywbkC w t"*%! H!LO0t 'YYkP3qMt!iQ;O),$hoa&FԳԖnlfn4d{h/n Ʉyp6 #(!S=gk"|+[6YZt 9BHBR3pIXkؚIjxp  JI1nAd9w}د6`\%5aO훹8gTSƱ~"64aP&"I{ZnVCTv{a w^_\DnvnR؎>P2U6 'j_5fIbO] m_6~%"N O߆-Ot4ȲP0q`j~p~ 2MR"3Bbei麁=ԢN:]pi%5Spi-V2=0oJSkA أs#ZGau'AZ p PkZaͥj-GvEdL>\[hAÝȘYR[Yس(9"`}Ce-OlKZG <ui{4+vf-KbT{@SE4cڅf cq&}y4@Cߍ"嬧Nn(H"/¾B21{aP좪^ҎY?=$dI.CF71N/ȭU"}R.AB %3Wð.*jSx@tw<>?Ksm{F"KM'N^o a;ve%ޢEDݰ<_"wۀ`-`+kϣ/3rDi7Cɗ7ՔF- ~n!{:-LOͥED3~P&s=+o?!3˔t 1&7 o3J3;}uN?B (7nyQ:UZ F<*+M*vy#mO%L?OOmhH1k NGG.|'Z9/ܽ6tA1,o"<~ecLƱ}o.>#g`v\5 > I~fD/ECOLD884Ơ4_fA}gwj*C^)TAݽrʥ{a]֏/)Vvy v4{(e@p3lkrJ3;F5Jk/((@Y!/#vOldfUb!v*4a!1vdIf$3J^RZ{侁A(ޑ&Hʮ[k1Ҝ>kڦk SdSi宺{Hu @$ւ.B$L/gp [eL*9dai@{}PE"CZ">EC`ol"Ksr$->,)M {riJ.]W Uv[|T(E@* JzVXʳQ,=bKӦ=n-v>SRD`P5ƧMz$Tc['K[MKkNT7q!ychA6кwK:YU%}6N~iƞ &Metc O;m*uB3={D Jo5Lg*{hBhGn][ ~f>r=w7 w,6ywliEg= Cؽi>.{ml:UrnjcㇳO= ؼaG|-!`)T&}5*VԒ:ϗrvdB8|`Ψ ҭ7ܬ$=Zbeg߭_Q߿wua7xwacgFb&̧Äi26/tݩ7~~釚;\_̅yvZ(W23WyA7J^79˨|rbVJRBģ(Wz.ŗTU3w9GWaNT~ k )rA<9tY7 b#,K2°>::w]R 1[I)q_l4R6F[eINl#.܊Qr$4\cua#.z?炡YיnNg*+hiǘ5+>']WyyRF[7[O19I5Gb+lf@1MTӌ}P:kE܉XD<4 r [,R764ɛ9^ylS:&m+ 5rA.(4MX $$tH6 kc ^]̐&]Uvm]][bkZ{;ӳ}~ߝ{'/ވ'2OJ2gV}g?3WcpuŸllnNnػe( 5&Z* *W295V,V̑ ydrp x0졄re8{D_9wZ#MI(xr0 3 Y1}9BWeURA^!i4L+2N 6& A0+8{Do O;h-j=#Qhz.GtNBÿ侁Cɮ>勓~Fج\Ž\Duh7{WD__ޒ5o> i n޻~VYkKXMڀaKH&1ߨ`G79ӮZʅc̝ӞMBnj@-.!]EfU Qi6kCwq!w@Ix4JI_ .4|VsjY< [jTQNB&+g^K/|%[N"~%[j¢rqIQrj>V-Iju`j2KK#`;m %RR,Y'mf,"&m /'Aw0Y.C"Y;+AwP,W\e<^}1>ACxhꕱ!wȨzwW<VK2K.buak˧FdL.O>O.}R90 %F{6+)󰟏/y`Aet*9rupP!> k~ ! dricP!w&zV.N1'„"R BpOGfGFh".ڳϵ(ڮu6Hʹ՗{.N 0FԽ~GŜUS!|Asc,utX?ظ8^,Q/{U}`{ĤcUYD'| [ Ƈ'W5\ r$ xy'<ڹv-[u"&W ^{ft4ľ~^WⴟU#}t5L=Z'@-`pGbi23m0M }*0jʺ\:|G-.V{% p݄$Ю*Ztg hWsmWM;;M,8˕:nl6Ck:&ݠdj.@6rkyfY|38V@Q ̜qmj.zI-5S^A"R_)'m45[Wj6M.]w"1j-R$2F^{{侁C1IWQ7qrfE):yB!ݯM4zt^f`'NY+~ȝ-Ej nG!P,B,<4Jt~ܡ4>[*\ " ;Ka؜Y+o|Պ~k wS|El%eFn1"tH(tkPkXXҗ%hTH K[@pNa{ |ɨ8 :vml<%&k|j{$l^y IvZX*O" [||٨8H>vy]ݰjS$a=N!·$Ӽ$IځcX|hP_).N -WHVU0uEbgcM uEbX#WW Y(|d:_* 6,3s+]d*DkUU#ȕWUsHLBI6=7~Mύ$f֮uVg-zA1נHD'>_" X5)X):1(c(@͆ºϧWǠLreWQD`cP&{_xhܧ87 )ڞ-2H;^3v68m qνBnSO#?sBޙy8}mxjhg3N=~Hz/ fnz(ʄ<{)i`?Je. g3tؓ%e2v>7sƢ/ݺqcf5qF34!+2+ Dί\9o6 a>$L㏖)!z۷N.D P>ȥ`WZҽR+ U_U9PVr'7"v֢}}0+/9slje!.&.P.x$hT"jQ?1u F# rS(/_8vrC<T UC3kWp"ݝWΐvhʙ0_ (vb7 k̪]V+Dxqg?!ɬjxZ:5ADG1YWf`xlhhhox= oo`˯]ӥs_;!!KզgUSXTo0*q+lC.:TX*` C<7^:Hd4UF뗏3 >-O!je}ڊ`41nvV|wQN`d~j Q~OTpRU=-HvޫպV¦m *bWr#p}0S[S$x}SrXh\u#O46#"o)Z'ri-f(Q=V'[ƨnE ;acMr_Fqw[fN)X+Wƫ9׌k!VЗ xU-qp({ qQ^~(D:nEtɗ^e ZޮEkXrdd&+ʼKKgMhF1Lx5'DӮCP|EP&He nr:V]ݑ R5JT,G/mvN;3G| }Xe;Z Va J[9Hs]n2#\yp?l}ÕVk&E7n`/^-5blv+,Rq?,䝜0Bg{hfQie/+3²z`/U^zZ0K-,Kj(j5 < t({ x(g6(߽s]B– U5ź1n ʹT>kXr[}xE@nӨ]Opb{"Y[`/ 0j[j8]R;C|5qP ]; l*\O}RVXX̹ma֖i#"π3ܽ 7n3Zxk4$'Nqzvc;vǍnțu"|"n5׆-OQ[AuYl,=1R E3[t'`Oxe7(󵼴)q{_cHH{:^}-vt<V'bykLJ&uR*G 2]W(=(aʘ0Aj'M(8WьkܸT+m6< `iM;ޅcRT+dgL4&S6\ɪqJ+Yz B,$ҵCUb]&# ?!i""O`А:F OɛVWۼd8o}f7#/%rCXZ.H/-ne6(z]UvRۡ+-گZ#u)Hp/lQkT uA}U䞛Hz R-2Lr(E^@u %,eu%k'g6vr;FU4]="nvSQGڕ6B"a18l] baf E/x4}Cӝ v`Wۭ-Ohod]I98gX-V75|Q3P5rL Gp<&GD [.i!~R}zaC-ڞ=]?%*O>-%y(>#pF8T g-t)!TLc2֬Y CBnG$FK\Srm LN)gS ElQQʨzod&Vcy lsVo.| G )q^S~.Q: |s%Q$IG  R|[y#;>̊0!pmj!5d o Z)BT6[`K͟z`+V<[+V0">,?}DUߎ `zi,bcNDHC|_:3u'ONCsę6Lڎad )`:,i-E: oY> [n8c| Dpbp!})]gp N`?P-ofޣ=nRTAbP:! \F P6am.(Np;QM- YoQ sazތƁߜplQ:-$Ӱ5긮K:!H7:!se)Qi6(9-[dGؼ "Qj-u~qU78;&tC #{y5z !.`?~j*QCon[ZNSwAT3N> 91dWIiv`'l)'!-!*fr nm9"SF8&GOAaoL ?P߆ӉZ»8> l^GnQ-UI3pa|_ϨzVKr!i|)ڢOKfh ~oϵ(ڮuZI4zЗ{]R*dJ1g/~vnKgύ Nޏfe=Ozb.䳖79+NjtS Ƈ'W+V^hdj|C<߁" q_ uEP'tP;P$A]qu.RDpLo]]#PF½w51߅* ͓`Q|KfUxgY4jELAAy iՊD߃,3tn{&!Q: EX$L'oCIV X*)P睢Usj-~߁$cځ$#w vI~HȒ~ֲ7*HwH[E&%[E&%]@y Wl+]J}F+W!1~$L2|n`gs([IՂUuPGAeuPdGAeB;)UB߇*OZCǫVPuU(*`IT@1V@ W|`ZQ~`$[QJ~?2͆޹*!CNt(0"BI.')`ov 4I[j\L?& w– ު$.:zkG$=e$JSs OC?fCo[H a(8"%=@ƘH a2,=T=zKSւhɄџ@1~U&["1~U&["=@a]+]h0jwIDy" ]hwdyXjOjOXB?5@0j&!3`Pw fcI $qϠ˟ / όX ґ̨ґm{N?6nzϡ͟) B`"ӟC{a*S~:ݜy/ JQv .`( 'ߗ*$%K#_B4'@f6|K(PO>!MoOGyZtC_K 'UXJG./ϸ{FxAMΖ_9FV 3tu3PH"#[X~a*Sg }7o-un5\~mk/Eu3/?:>zrkK(>d1=3*,䝙׆fv6sy'r1`+{2"O4Z/eOq0+4]rJTw'K~A;2J׿%_V.f:KnܘYM{\l .F:roW ?|˸6(9ss@̂T0?Z†nߺ;B2B;۱؝RvlZ꧊J=(]~隵)^+c x\mEjs0 xw~ ~k'jfz̵ E7tENa+e[U03kK:{aՖyh_/c4V-An8PC_nOcrfjaW!t=!mooxBA}x⦱)|Ka:ܽ|jf(Q=V'[ƨ-_<~IP2jVl׀a?'!< 8L8|+Ä~U9[{3]kT4 \ ZM⑤cVa9 +fIfƷ``<ʰochڵrxYe뭡!&He nr:V] R5JT,G/mvNR@;* ]B [MTlV.!GuʛaK5+cgn`/^-5blv+,Rq?,䝜0HT %FR[)R>˰_Nh B!Tyykdc,Z/GUjDz34^G)3≫@~GW8bԫXuᚂ~h/ lP%^S K2LKUA샭of%w[GG]th'/~Q9{ʱE˝1 6%#w(5[Tr_M'n(l-:r<[.@ ,x4~?^-ZP9 OwrCEeQ 7)YV`xr/&/^x -eY1o)f3TTK&>&lSW7Vȕ¼E G>3h[{;!wGJ%r{ðgR0|[  8{eܭ-5^4ٟ?ݚ)v<\1P! {z;NpUvtiM1nyP[+1*7oT=%oO4Ƒʧj3̲e7E#<ݰ- G4xοKȳReuY1QCg3MIXV飰v^-|f^-u0 xxme:zYXvai<63•7S$|pXtkI孴=K? ){ NܦbШG(s8HI0T\xfRmG4*+vʹaLtz~NpL`KgyT ]?=?Qd, kOF8L? RcYp'Or}fImV-0RFs?R|MF钕yɤ.-7S(!'I lŊi8Ӱ\P–ZS)ofc3K^ s5iʥVOXPEZ.NꋓI˛h0X9[m(N+E4i: B"=<,^7Kþ,QToPc4K ^yymɲpPv{n侁C5xC#cHiMBp\Mq WѾ"R9P,]ӊ&W|^P 3a'XX F ,raB R B=8)F؍XVO X;mvVn\1R/C;`Khi,pȈhir8l:Z3-m` cgU%:X@GmԚ}^0##(<ՙ`_T2΁!!w"ۋ~;LK-P;<<[)yp'{.l{G{`+RѕT2^׵*C矻{:{d-=v\("κ]"Y'ἁ%%9%pfV0H\X0˛i+|`Tp݂/WK-EoR G[6mƦ;##n;pa|[^kNraB}7{q-DF#ģ3E۵nRїC t'Vc90N_}K:/kMz:BSˬ'&)MΊ"4m|qro>:t5?IgQ1.A63XjtZpܥT1 H2#ʴi7~@`Ϥe~ٵ}L`G*Os?Q3~+p7xEfIGff2Ã!1;-3s`&zĞ a6m~8d vWRh4?͆{kS槌W)`="L?i`) [~Nn@zIOC1OCR" c 4TId %=&'ji.-H| $쀭!' 섭x֐[$al SXPt*@ ÷!ʷ9͆@1 Q ]4BUoC!o#w Ɂ1 Qm5(u:@p'l:?EvP:IJڟ2B5bm~p۟* l`ڟ-VaIKc9sJV$9sPEcAB4?ՊD?Y~йL\4 lV*ޗdny(0*P$aU<X$L']UM:+k$# / wY~H F/@)3Jo`loBiNEnR'VL ]–ki3$Ň 2MzZV.+DQ8E0A&"q%aLXAI>Z%H﷠H[E&%[E&%]@y Wl+]E%KFK嗌痐+_R!1~ $L2|n`gs([) U~وuP嗍GA e~وuP嗍dGA eB›3)~J T+*+PWVWʯUy$Q~$*DU#J(!_5b Q~H* WzV[U5Pl6ΥPנ̯!uSGQD 1~ $Lre=O뷲~-MoC$Nr)t`뭡߆& m'' T]U[8}ʌ:6zb5DuHFQ)*5Duf `[EU߀* c-}$LDvc-}$LD{JêV.#3+Mh0j$a<Xl5OwZ͗)S k5-[F<X $dFr<_5n,Xt wK]c$twX]c$twz.ٖ^%=.A B)]dR0&SuJޯ]33\[n{%aAFD {%aX@e߆2m:|m(FDȌ؆ e>ۉܧ8ģSxĝ V H女Vkn}l2tt66$IE!plaL?k2o47+mZok#u/gw$Mwxf,μ>4铏s-=z[xtԓ\nxzxwf,N_)cӇg8:^yxPyB\})7|k)-~v I7,1y䗶#t+k`e}0oj-ntƍY`$(+~E5pog~;a9k;7WΤ ,HO eRl^/ 2-i&lشK/Ob\Q5kS;W4AD\ng-:=PeI@Aa0jmJqG<'.Vkyhс5ܮn5\!mIf3_!+U+[6hʖVr\@il;=N[zd0aV jei=2pHFsG2N;3Ȃ(&rܚy}2ďnZ6:gUSLTo0v7R̆0K)t!N ب}nIZ@i2Jx~{k/ͺ<o_[“#D,ڊ`T1`_9(X븢"fm\3PH+$mvM(uv65omvo$CP=uV+'[(Q"Tk]u?h#F l.C2E4:9wqSI\Jch<,u\jNh--, ?ILeOB.Hj^T19< 0Ts* O>yKSY~/=ʊ^-WTˢu7].G4(/Ģz1[G"$\_mgWUEնǯ\ Uj @8L-{)a}m5 )R\kΪ0idV xG13i3\;c4΀!7PɮbZIE5VLA6zMcpև`e/7Q&w=˰/+kyc4+Zl^ `Àp+[/;uz4?Uo=ӥ<4 l3v5ݥ̸,@\(iAgghiMjU9 ׹dr ƚ'&T_9b_Isc'S"> Q-Փ un=p(m+V̳aa؇y OBQ "gYYQ.‚ƍzMP6VއlϏ@Sr(z/ ;B 'Ƭ3or;Zv vzonE_`Jex2ryrp>yJARȇxa.y4!/H rQ޹r9qȦZ6m<65_yp*Pm 6`;lޓDf`Y/"KH+id`/XR:y l-UnO:]bRW}}LZ d @K*I6`KE]1}@a2IIwޡ̃-zzl&x"2L偠/4w.Ȭ6\d5EO&"aW8;=gM@a QأBnXaQ ^^ؽuʊɔiIΛ>(Gz 478 {`RޠAC{솋gDmiRԫM)$BGaG cdCǶWrlǧ5-ִ05%Z y\-j !>CB0vY1S,7o&!gW|gŏ>jӝ3&5$8uSSo^{i=IMT1Da\꠬f,mC~1ކ* R7Q"NZI Y#NsM}[%ǸD%<2wSpaB˾diLt4=4vg/|C}"rwbT:(bXSjVCmXEXϥcVpA0&,7cӬ*D=zL5)iWx},Yg矧DV{`奔^@`0j)}f BHCcU?o/zVKr!iP>5ܲSt>4Q(&N&yw=.~y+H"@ګ'*FO;7!5p"ݩ7D},?f{ƒdX`fjeyjUl J>.π2a'OXʜI$AP_l4#皏FƑ̀%at.óu}G%Ydi5,|GP-liөZzўe}FvtiL[})[b,X }?b*L-Z.ǃsc,utX?8aXp.ge>2,&gEao~K[3qÌ+xѕ+\ tJ?!yHcgYfA!RJ.X 4/F*|G'vp&MmJjCȝ@m nPy˙ɵgs D{99ƬZJ}8EٖlZ)MQc3 %T:df_!؆uP__o9K] X tyk Z˼xuRT'+IB 'cPO"d{i4W|O' CM[۾~F6 `K-ot/!1&ԔCwsG[DSCǵVx`7pGRU|xPϙƻ[Jw|F[Q&J7UՖr7:>57pɛ ,Kzi5w1&vfķ`/lWtIuKfhAw–'NC @pl墆@? Q~'Q@> qv*Ѝ1Az" wS秠HvX uN:Kg u~ $TVS'*Uչoip;!OL4ʖ Uq~f!yXL ?m蜈Q8> av[?$t^ YG[P[F-(-#Tk| |H6tU/t-Io23r%AoCo<߆(6ny\y[56DId˓w>E>?E&>@0(0I [33m6(HPgQ q1~$-WvUJz 6J? eGGF}C5/B_fCm &/B_D4J'L-dEH0[- .SC%ע$oA1߂*  D`0@[P%aH9/A_2b _4d$HHi&H^`f~E /C1~$4%]p Q&9KuxbZ+P$a_" %pEvP:Im&uy2ЯB_5bm~p;ۡ_* l`ڡ-'tE_,4jEL_,U4:ւKHkנݲZ ˯Ak -+I ,qm(0*HDx"m(0*wW7C7 :$uYV'b:$u(q<Y~:)1y~:$Ҿ!KBͪl-Sf7X|-DUDԉ7K^rm?5Tc*oB12}$Lttcd&DI uIn෠H[߂" m`-oAI@ifDWQc>߁(1 WQ!1Q&>7~9AB Uk$< .(PFBFFAЩAAūV{P{*=T^]J>G!J+oC6俍m#J巍d+o|ۨg%53sɌ+Ѕ) @1bݫ(;F{U@/UI {o 4L$쀭s;{ }~$ [vvq}N~v1}~$w>nTSf{!AC4J'H@P1&&A 6K@0;UҔ,J0@.`߁* -Rj$>4Ih5O:1V߇&o$[͓V%}T?0`Zp5Oz1V?0 \5OWͷ"]E(H}0ƥ#C /y}#֥#C.ye}KGefPw@ Tu2P)hp/l[uJޯ]33\[n?!JQv .`?( 'ߗ*$##A?2'@f6|#(PO>!i)!E=ˏrT xPݼISm<[~ /@bwHkG׵>pa Z ! .h%$섭-&N߂-tܝ\?0 cI $dFr!/lZ9DIc%a=:"GsP_NJ9ģ7<,zNϟK<N_ŪxZګ +Fxa/l}1t/P 3tQL"{8ģ)vTL Rjy+˯ y+H$B&-Z]e =d .j{C=P)ԯVTkDo47+mZokۆ7BWHi`?Jga3Ku,(8, ҭ7&nVWeDe֯hCݛ2x*_/ظTN旝+gb$̧i2 6D/#EZ(Prg񄥌شk/O 2\QB5kӔOͯh9Ӄr3rox?L uqEZ`M,;Ǧ+sB\ L8 {XpHА>N*a v PӴyAW";_v|B6R T3ͬmz5n-"JCwpGSg3K;A?`ИWV#>^>HUҩ9 B<ɲ/}lhh_^#r kq{F=sZj|Qѐ[-<.!IrG7=4ݹ`ȨZݢ,c$hAP'LZ'88%j їaK>U~[FO71,{`hˢuS&d2f? 쇭޴n`vnҐh}B[J$ac<%@<ڒ ʜ1M$kDr|HU-b.? c(~ȳ.B٩PVAW4D 5Vq @f8%^=%nLSub' )`CG[k<!Ncy @X7~9h.Q** 2*Ɏ2 {zBSW +,Ty6^*&гPxzRcLL LB% R2Vܷ4e-8RkǡJ{KP%a%" coi$LD{JêV.#3+$M&ZN`Ehl5OwZ͗)S_0/V KF|tZa%U~|k(һ`q$/C1. ]^6^:rґe#٥#QF.\:-3s/Ҹ9az9a( dR0)wLCuJÖCn+%aW JN#{"q DI=u,P&U(U(=2#P&{}C<ޞΠ̬T|/O \XJG./8iGoMBMΖ_9FV 3tu3i$=K+|F\k2o,@B[_ 5x9&Wk߇pĢXR> R =LLU*Vf!1Γ%e mf2UTBY$(~Epog~;ar9;7WΞ ,HO e"l^/ &-iͥ\ش;/O *\Q25kSW4GAD9kvp3A(ʌs3αa.ĵ յ*IZ8^ʧ5._kLVح2j4rBZd`ܙBr'LTTC3k{]Xg/K\!mє+;.uޜ2fѐ ݰwk̡]V+7+U&>!r!jxZ:5 "\vdRsRn`CCCgm7"0:㠬gUSMTwo0*R͆0KW)txE\Ʊu$AfMHS-,`~p8 lݢ- 7W HP NJT6uwq[ ݯ\v2'\4L8Q󇔏WʶS.}}E]v {GY7/d6hKn+#5'FQcuSEsFÐDqKz]q׍%≛f@-č*f VCZVdy5z.{纨 یwm![Ѹ*!wVb"O7@ZG HSp8&5/^|E{yw2 ð_ѭ7#/%rC<޾cښ[P"T=p]FCm4Pm[^[aK 6}^2icfuG^m_qV/~?kR7׌5kfń`Ѽ EI'{ b!;\v[E1.bsxeVJMm=XZ;u(Z6C|G-\Gg,X:=hK6wҊEDo,0DC<{* MQ"K9FX! VyC4$k_(OU-4"!v+ 7󮓶2EU>9_FESUrgw I3?y ߺre3^8Ѕ]Erx >ɘ=^TV_4| O>LfW{7VA+lPmrZdꞼywbjMޜEk7UsضA[–-wۍG #J@ u/m]؞N–=Y˧/~+; |ʢmL^2'K4촶dෟ ':.n_W+'+ ||v Ӏ:Մ#Cؔf->Lh2(ZTh0ĝ NuYq[VP1sT 2KBtO&@ήw=E`PODQE7 ;‼߱vaihQ "B}Ͳ3B w^/NF{f( H߬>.alɜF6 7].5}+jaK*;t㴘 2dTиfc Poh/,Xs^j {GIKaKcD({0tH |(-#kRKxa|; KꬑM2R B=qhfъf2Ny͔;#g)ݵQ˷KK=2Ǣ[˂S_ hrsA!hq%\]I@u ErKNĝq#"LHz4n 4M*ބwuikz= =rL.̤aaO.:"xyӹX>PcNEGL`O2^W~%U_ UeUmC Ԍ.a++hcΔȝ)R  ک*lqCpStGx en#0 Կ+qKD16=uoB`V` r [e-3`yI.S'…r" x(]HjUv\E GQj>{6*a)oe_lhT +f)ܝʇQl-5)V&]3l2$6i-^KNTTDx'lө*_Z00LyVTF\+k-B?+8XE^K/r1<2ڮBf/ ظ_ifYwrWD!^}Q=Ơ4::akT87gyp`!8ǥX& 6$ކ$75[ `ֈ " ^-:r7  {2=OLη_F3Y?dYאV{`/P^b1#"THΨLRRبZA3 h alh}Dk?c/x8]ܜ GLNaK3(H\(HitdS, =Y$-49K R,5U^M EUa̪E^j7ᅷ*Cr>l3͈m>@}{E+77_N /dJC葉 o^>2:cM:ʙ-plaKtEAj^Z_+l;`K +qIAS9[;XI^)Hua[z&!Mo n+ ZhRyL4oO,I0~lD; 6`?lTSMD 1bH3mŒcni&|+aa̕"jQk l-.ÏilFc`FPrF6s |;!$ӫo2^`p;|W%f00x~$,if]#P_9 X8{06m}b$ڦ% Ji%`l,#3 >xIqv=%@ D(US{ ~#| } ÛHSChmF;1B`SĿ_ZX8of}}FO㣧#WA vW!kpN/yGbo-!w\1זl{P7`o.W!mIeNazoioDyb4_q`ݶ<E6nV*UoܵrZlW<{,xv |] ]"'g`㷚j7gfZy~ 2o `OiE یGg3g獐40;}^꩖{o']8ytrte_#6^ULgMO6am%e|F _ {zQ^(MSJˣve<)Ha' al ~G.n:5]vw %=^B*:Q_y~86zϬ!AC4J'L-d=H0;L^>H/IGAUH$L4]@IRk *Hi~߈5~p % c >Id %{ Mf^ʋF@/@J'ʓvYԐ IBsp$JȪO( 2||lH$&!FY] }(}N!9a$&!!5P(>?!: LC#ֆPF X@6D?2 m '-?,4jEL?,U4:&%$CHnYI!5lR!MBi@YGޏHw_?" aK5}UI:;alP珠HN8$]@·u$'> I؈cHF]C?6b"lǐ%aHeyʌ2 6˖!1 ҦQ:m5JJ1$-S(g@AOzV.+D$%ax"%ax _7~# E)Ic P$a-P"S(0(֯Wb[ٌrA?3b ?(f$>\j g%aw: J5C7a*PύXGAUHxPύXGAUHvP&aQQP(t*QT*BU"iE T uU(*`IT( c QH%J/X+_B4K̝S&3V`ږ+HWP@;RC2iNE^ 3&ST+(0%?M&nAM*5.߃& wVLBD[\o }4Ioc>nTSf!fCo[H}$Nt(cb"}f `[EU[0P%a%T*VnCh0jIDy" ChdyXjOj ?2b##jc$dFr<_5n,Xt ?. c\: /c?6b]:.c?6td[f^ q?6ĈD?6P8ң7 GO=YL冧 ygᩙ>f;}x#a? ctP yB})|zk)yz)i`?Je'a3Ku,(8, Ysҭ7&nVWe4֯M_<~̯q?l\Q('r~ oy aL ݾuwt!d5-w0RNlZ'J(T~iW4ADY7Zg8263^mi#ąӏ OL]Bm >=MPiA3G!c(nn-BU>ڦWrI3依C-Ɋ j}c%B+a+ Nq`\PtsANTpRKW[zZXf`DA1+~>Qc.:MZcT(CzC<.X 5 Ian$}≛f@-Ur5@DZny ݁}t+8LjQsݶ,Kx xoۘQ'Wa_ G~qUد*!v+8uܣGEk Zޮ!I:hebd&Kϛ.X. c<]xϊ֋ |]>F]+gaU&bT (c} ^TJZ}tf`-S9sw:Uvֻmj-`٬D]C.4&3•71JÖjWk&En`/^-5blv+,Rq?,䝜0HT %FR[)R>˰_Nh B!Tyykdc,Z/GUjDz34^G)3≫@~GW8bԫXuᚂ~h/ lP%^S K2LKUA샭of%w[GG]th]zBCazǜhآΘ{aTܒIjeA⫉ -TGځg`hSzܟǫ%@KYjcb5S3vCίkY[~ю>kD[5(N*nּ1`^倲y'pxDl!LL7#/%rC<޾+MnkTRDdiڬJ6p(Ʈ+~p `!Jw B.)Jeв3ggL0׺Ph)MOݛɪS3*Yuxx;gfyv\h[EqNR[g0ŭ9kug!*;]o6/<@򟶱 ץzśt`iˡWƯ.840pPfPYC^}%vwԒ1;3dqMw) EV(hJd7h&g.b5MuW֤ArZKpQa:FߎbBWNZ??CUb$mRCF-Rq\GG[,i0EGSQ&iΗW%Tt“T7oNUOZ!+-[kAԴδ [PkVM1! " 6 hqz<,%~m6 K=*|ңUft%J[N1v"]ҥm!y p)ɧ-ˁeFјr~=*Hr6E[؝R[lK]vX,:i+%f$r[nyWI˰֟ȿ:&ǁW`KuV0!lWu?R+ 6s\јMe&{8{G` O+gR `m6ꕎJhpG zVKr|ZR Lp6 mӦI$M@6~jNj "LHƇVŇ;!w DM= [%V'Vحy=_] x}eawG~k8k3ז,,?ʿ4Pב7p'nHFyx.-pو 3D [naג3 p#nǁQbjq(Cqb(>WB;`$yH{t$_,Ol-Cb}]>@4JF@7P %a/4JPiúޔefn岢A0. %a]x" DIdwڅw^" clE&%[/BI@~-^+͈.%z |Ɉ5|Qd$>_BCb} $L2|n`gs([5_*_6b|Hx*e(e#֩ʗd_2 {zMCSiBUCa }U>Wʇ +!T ݬa0J#JWX+W Wd+WP@^1YoU=U(UPl6ΥPPHFQT)2Ca2ELBI.')`o@̚נIRb| $ [Pz }N`ls54IoO>nTSfc!ҏAC4J'H@P1&&ҏA 6K@0;UҔ,J-7J{K&TIho[2J${KT@?k223$a 4Ih5O:1V3䌑l5OwZ͗)Sͧ!̴k50F<Xͧ!LBf$W͓=UĤE @1.@##ґ t1]:A\:-3s/`> ,W\\|&l6NKk?З|b\"+aȍiF#ic27+*PJ[nn"BnӵGb쮳`1n* {l\ 2?n1nA}6ͨHZ,[4EޕmdKI[Mc۠&#HSUT/'?Lt4ޝrrT/Xy'#,h8{ށl#< pJ"G8ģxve+%A;@x$ S*дCaǤɵ5܎ 7z71Ucs+]qo2l">[))mԔ1 Ь[a<[_Ɠ}T9 n-A4\ԨѢǾ^RZa7ӯ\ዢ;nB}5-.ƳsįG}4l< ޙ= ƔcT&vٳ<;緷V`mTHueS ֩z6)j }r@C\T< 0 ,uL+p;F`Ԩޡ3Tb>RE3v5%~x^Y`@9Z_KaУ[&GƵ-w à`ڹN" ^ȓ&T h$bvMgrZy(0Z+!p)%g=)0AR)da+lvshVs`f KEށ,/-Fř ysYᨛHS䕥oɂr̿[}yIMr;_8p;2c>PO(2VgNڂ8ģl~ks6TPT|ljzbp3h8+7Meiy ڇ3t/Pk0:voB=7 KA{@勓,;|fEطo–j4U Y~b^urisV GZVؘ9 Կ ,lS-Cl֬Wܢ".ck&+Ϯ /HBM%LN_;n;p/~ dfQ^;ʅ-]H3-oV_ *ު ;;㋿go,E4٥6cnO+˼,Fi>Ls+'V`<,CX91^}AK`_<|y V_;-3VN noþ]քX9Q{| q| ٱr p6>>s`.^J*"~'yl/Jkf}avry,5|x(|xHqA6P5kѩq2h6i/ZL [`oI$6TV͏}%2dʥ̐ne"'HIfF,kGDxZlP_xkEXboyaKVmW3m: vq4,xakiYGq#B[8[j-LEVzHe+tZ*)~7h'99eAo)"L Dl_lK„GM9ߨ釮7_`?xBцd(AaT_yn(D6~BsVx]V1UYRCw Wyw`}nbXJ7~y',*Cy4_ BxCw&2\6tn~ ԯ['`h$w'a˭?4Tαb~hz%"N O_-Nte'@]b9ts3G+JzX< [!sԯc|~:[N]I]CU&nTdpǜo.H[!)B]oⱎhF 6aǺ c -A9:kTmZS3c8#~FD31^}AX[hBX+ؗsQ즐x[ RTyKD;aʢ@_jɏVΣQ`[qBtpu+,–ZZkC+W\\P-ע6OܹF8ģ) 6<'U ;]vrn5CWK! RÂO9sx(63+Ӗ%1O`ONx)i'lټ 7 -,JLn#p'ʙ3Bk+vdZ0sv O шJv2MfaBIj6v5~೤ <|FGa4ely ;aKDZۀg`0K6V]O DQV_mfGJMWsĭj!t<zEb|5ݫptMWj#[w5Uj @87!":YΔhhQ#&45̊0!:ƾ`<.o^$~IjZQKǢ;q)[yA8h[Kx\؍KKԃ\wy\Zvhe`Kx 1ef蘑&XbL )B=o5ڹ5'< JdR>:GNjܸMval! liAR4kl6V#WJRc˕م/%-(h4=  a aLn54&\Sa.uBMW/qn࿵v27+A Ԃ~(B6wV{#"Hv`Q;K+x{eH% ɷg٬lQSS<6e\B{D>WFG [f;dܞ?ŷ ;n*[aoUuOYn/2!ey4l=09tn#(90'zw5~jipz;`GJ.^-ۄ)hZ䵊XXO, 6Rd] U.}XќPI[?J{T,CUPPU8J $IA\/׈WՄ5Cħ>kE^ؽy]e~䇳s$Ͱc;er 7].d$*==ԿHvSG6P\bx{r' 0Ps$7}Gd1Nv:pۋք[s'g Ua+Vm2]뚢vNRŢgEN؝L֙)DBjs5+Vc [Jb"[`oQΓn?lPJFԶa˯-7D!+Kt+7SQ$6{vrmU_4fގydq15a %(* Wn 'J!wo錟ⷷSKPm~!~[D .۵n+0v- Tk 3|*((kFR-!zQM&tDxTYùka9Rk;ŴEN'aO*( [RK)BCFy0TWpW_l:U/ UhZ밯+j3Q)mW,y# SuY. c5;NRð+Z KgMtD}^[T3{V4-a\ `WKQ?!Ef9g 7?3575v)էs9}np %#7hQhr[o)O:ha[׏m叵f9v b޵ҶG-Z9{\Q$1`˭JŸ ~PZy(+-+KKϐzsdxp}hrC}%e3wF(En9pD8L?3@ҩQ#j_fϓ͇##L(~P>5(u<-_]Ԓ]gYnM:oQY}w75OBv{90΍ѡcK8^,8y0+QM[}`{\trV4~'| [ ƇS;k^|I( 5b}XjtZpܥT͆vMڿ$#=@>|G'˶FGqbd2j=7&#]Xk/ʽnhK(sj_ZKoD_p:B9iӮKɰ9+G_(%n躂jh*Q V9WF>_d, M+6wW, @ [ !2{aJK4\sAn* l-FSĿ Z^55MP"åkH_C&-u lVivgoJ.rMME]ݰc$L2x`fǢ['s ÿ(eY / ʿ@h- 8  /P.Ȗ E _@݆0jݘj$oHoOP$a uR ' EvP:IJ*x_SKN1'Z%TF_Bi$\%0 /J$+x_5R7>;k hG鯠̿Br5&J +LcQB!dYUWP&{P)O–NJ[-k$삭̭w%.I%ݰuw%al ETX aGrk_CDx%א_',ѿ,;ޔefnK =DIcgCv@0(lgwڙbAz$3HD;Dcg?@Iv~ySt w/,4b#dkx"c !K$kx dFjfHnss$qoʿ1o1boo M I$-E),,\By@fVaQf 6^V.FXt یV.F`+v`+OȀpEC;ѕ $OP%a OP%akqB huOo!ʿ5b[o;%oX;[#E[[y^`43Xg3gވ@/ͼg(0ə7o)y /$a;l< $I# yN:[95_ IB@j$JUZLE_jĺBP\Q" T4_K^r-@5[.of KǍ;#qC;#q㿃,HvPDΨ&D A $-UߊA;a s(t`,5ߠIB}[IwSfCK w#qGQDk( C 6S~9rC<ޞN*WL4+,Z%#YHζۄFx.|yVP!' "єA5I?BŒKrPߐp.x`ŷ2U|Fچ!AfJ[ۺGA#x9λYMwxf,μ>4铏s-=z[xtԓ\nxzxwf,N_l2N=~Hz؏\ fnCCQ@ 8,ɭٻLGU*Q&u'K~;229fe}0o֜mtƍT@#DgC+j{WO>eWɉ_ I@̂T0?Z腢K _ jZ/eĦ_{~J藨Y;krzC9Y jŌV#hQq/Q\IqG27N1gQL7lDFa0;4s^bfq HU:A vjik &k QX@h2B]9:!6уH)s3p?ByKiGf08^}A[Q =8q.|'ˀal]ϭc3ĹXe<T1){Yz&@HH )Dia_J$* eFJQ"""%TvU{_q=vqwv۳3\n/KKjUoe~WNd_~ :Wѫ'uzmM)L,\u an5-QuJgL/1Uw:]=OJWM&ہ{Eɯ*L:sn=s 6fWG/ߙ]ƈmo_O1S,iӪ8xj\+HPBu$}z|\A TQP B0\b[zh8]ݲI4N1'BC!1f4gN(qjz~L.S;k-45 `Y0\ CB %Л$w#N!ܑg/~/r@P5c?ށ&ljR81Qm)%}Re@t%HRq$g''gfR=K;B&` Mw&2h^}]I7 -۰:K|Hr7 |_׃ZC i=彐^?><6 }$s@L3%KH1cKK;9؟uh2.:8P$[J[q^a$cZeeh m/IFlv/w|"w;Wa_͠HkqBc<,Y9ݛsŠ@W.0^Qk$xlM/t|X0A7{qKˎ/& ,{&w*[v`Pαm {L/!-oNraBڵ*tiȘZ#b`?JZk } xm%Z?DFl_F~,_q5> '<6MAQs%pMRk6}XF~sf^}HxEC}3kg8Shv?:9n/ oeBТ1S=LPd>lݤ9?3}>VIqn-\ _=C6GaJ뷏za3`̱W)7N,/Mئ6Cmm#[;^닎 Fb Qu2[[5ꘙYVXw5IX\g,;UFF^[L!Pq-5'NNÞN'#q ի~$lu!y{%-2'NT&2'NJE؋UpNa+|[R}{) '<΅sK,QR|#jr饢3`R9oʹ9Z ds 8 TNDc+xI{tg{[&01 []2dU If.`. 98R0N :Dh E1rς# Jz=c^Ln 1^<[(t?yTZ0{(Ux(uz.rJDӐm;MP&ho~0"ux H!+d+NBf)+4z̗0KCUkGtg6W+g"X08mȅE5i"۬Vɱ]GG`Smi}aJj9^y*rn/l'0&˰/В;27 +GYس(vsD<-6!l5p\:Z-ir 2G`PכWvh6DGnsꥢ kzl‹߀Nv(J)W(eVd1 '@⩱U4T%'4nnX33wqY1f$QUJ☭oΗ Wt((3`s ˋ9 "x_TNKppRrWrZ" fT%!bLJ*9`LyiWUbl3"bHRu/=kr X 9X-t0w\:mūY҃Au5`[EƓt|x53OǓBY';O>* SO>* 3O=ǓϠJ,Ǔأ%5lx\z$[fz$ [~s6.`ljOEP6n`lXsP&asP&asDkuCYu^`rsM˗q!I6*+:!Iv *~y@ZO6$I(KCNP<}@6k*\Qt6i#Q"$.[Ө]i}Ū䦋K%a%Ȳe<]\B)iN ˒tq E%9]zI#hP{˧ϏIݰf8$I:U:$T_/Pxmn ͚ɖ:"u!L(8"%MbO.I֥ߟ{9c#&N}h ,ՅNNmy!&Qɥc̒_:=w.^ʥ:^$șrTFΔͥ2r&F\|  xmMFfJkw-wG?G ZC귱K`K/=;>{~̢tG= ?_rf.L)[s N8yfc|(bqo+0|Rh7XxG|)(gGێy˧挺+W޾=~66AE~U;` ߯~ظ\Aoٳٳ 0a\%†ݝx'ǚ /PS&+J5*[A*XEs(y(gOU'&K3ʕ`(e5_ NxIiiHO1GܒNK^ӢAa뗧Wn!Cwޝ~*CFnBTF2j}9VsoXZC;&;SQl:5g(l]Cڒk.XN+.UD#] A`Y/yJ#[~Vcb1xeԝ؀,d]U 7 8hDna&*TL3fk)& hVM+Q>Wb6ҡ϶0G\5#r^oD@1B~b5Cwqp@˞ >?K[aTV÷&_vveeEmK8;u9̻!1<ؓ4XU{;RU+ZW$7\'EVѵ+uiȰ}Trـ87kaW*u&7GY\ n/цcH ]O2G׹y{澳MrAvUvC:ї&5maݑr2/f0*]c9k^{iH |lZ(&p T"UnaOKކ0o<>-4[1#v)*_kƗ"/=&`|II`ŀeWŜZ za GWPee:]X+DuT7WI$N$Ǧ]lxuJc04M˴@"lӎ\E47B:i{ۯENf I~.Z3+C`њraoa7fMofdVHZ,! þثuV^i<- ~ ,.+u9%ZmFn?zq>"_TV4>.XeV5C/t˰YZR&oWf@ WaUaxسu kqP^=1`]:쯧?`O4:1i'k}Buc-G3k,swd#{q$x5s@D_:'fTc5H h뜸za zvՊE(\vr#լV/nR"u&kz0aiٶ/߅]QuӯZPbTSjkݭEF1Q-sR=2FߨO-0DAQbA?5U ŠE,#mk#2@&-D=h0^4NM]\ Z tqgY0\ kFB㥾tk*noKí?>AWm3墁ql2*&ܭMB"Jx~A=0 mxm/S xꌬمl  2h^-ԥ˧o~;$>PZޯA!߃-w-n^H~^G[9 V&t1쏥Ihe'3qGrUtUᄸK;-Q$mD{C~x [l\"׀ǥyYrs7甋y + V /AfZD ^,EӋ.3L:c^?^\9 ˞ݡo‹/JÙVv`Ǥa# UnG@ 3+w-VkDluG֚֬F+H_ކ}[Iv"#|PoB#wgab?m.k}Oyl2:9YшF~ᚥf5kogA#`93[HxEC}3kg8Shv?:9n~\ET 1n>=2'B%i.H7`&͑"wxtZ%EĹxpmꗷ/*V| =*>Ft]jgx ;4a 4j-EG)U3͒ VM:ƫᚤQ,. 3*##Oja[q-5'NNڻ_Ỷ8l{_> |["AzzemBSs [EsĪ\^ĉ,p2U!K%"1؟H8-Y^'MWTɆ9tT_hK.N42GLwMmeR w*ˏ2dƽIf.`l͓+ yíщ8B2Cfܳ#(v^x!fd꽰ocՁ.tB3p6He[/O_ "g׼auvt=گ0c = \'}2Hg3h +4z̗]eR\~d E3Yu|@O€(e!Yeoc-hI8 ðrU.թ^b +O`pM Fa_V?@%wd$oLWHgQx[mCB[k tD;`[ҢA?d$7m~?m;+dD. Eش5|pm|F'}x%psRKd#x@y@⩱U4T%'4AlnX35wqȬ3E1[7|ߜ/gqBPSfms%𾤩܉͝:F/XZ" fT%^A ĘP8(r4E:eSht0Qx cF2q4"4_2{ }b.^;B|$Ӿ`9t$ ǘ] I)DqF c aN4J`< D+ĬxGn7c41@+ Hi՛RV+zlv ʺ{Z Ex8{BaF1mwMVk4` UC5Q[/;i3<`%+W\\t(`&ǎIOq츻$:Wg f4Qnht궭whE5F=`_?tH_Jձ}b'L ׯ_{O ce)OܠBMxSR4mzwlߛ?rMLNk&2GќccH}zȼ /Fz?$#< h7 1*"gA*M3E/H zAщ $=BucD$$NbO^TΜF:5~k~D>y62W丞[*I6^}EEAw}"*|6}TZQE^??wP*R]yA*>GJSu@Dd.<~_!>TA]<ĉ?KuޞhQvg:'H BuQC2GYęSgATha侁A u@pb#*Wizwam9ehw%gȝ>m#Ps1~y: ΄" FF7aˇV+XQ%xq83Bu]5ScTS_э+c賦mVyYP+v;#yibJjF>La/^idz$`a`GGM}lP [a Q w 6/O+yi G6mH~nlB;W,TI [)P": * `weP ݣ\[$~As(C͢eOs&y!@PB NMe(4q׸:2VO-+_99ZiT:ՕYZPF2d%jA#7%-Q uҐ(uݔ6:?" wVH6 `$@N:?" ;`7 c|r i}$nb$N*g}$${RsM}n aYS;RGeiNIn`&1'2I֥ߟ{%c&Ep0 QѪ BZ]8$IW5uBbK9Ι%u}źRD{ģ*,yq|yz.=G<6#gbΥj4jLhƯFBz۾~ei?˩~oZ o/p!Jj8ܳs,O}ώ};7kOO%gəU;iѪԳ1 T&Y:񈋹fpkD@1B~b!תuŁ\-{.t8v.@s jJAFt\fǁG-ID*a_/mCpA BeٺslE}%F5(<4Q ytǢצ(DFӰuJ(V9x2P{ ^% ͲzEkڼm_IEB:-!F+H>&Jz//d'Kx[7r?Ơ1rXK^Cwt-7Bq؅ rX'*ktQYӦe (ksRE#E2DoTO\_oLG+CyGFw0OaLk~ffi,jf$"xd;=9ۥ lsP7et${={u}(.\}7Ex'H OQ-Zߗ=g(7u OW. \?tE#R DᜰX~ڶj 9,?"dlIrjoTu#<[jl~ڨX#u1Xa _ VN5w{5M^o`P$Kg#/*ݕhוfQ"SkTT4)ʲtMkn*"w=ɏj?G{a :6νkLJ 6Mb<"+)u" 㚿#uN`.ٔfRw< a<C!LғaV3IR< Ij0IM!K!Ls Ei4]ɐoVڧ-VJO}PH&Y >rŠ>^:׼/ݯe:\菊U sW:'#Z4l 솭ۻy#B=_<":xl|ú&"One\lWḬ[̘ ?}A떥CȠA~<V:'5f:=ޔuԚA= _Y?=,s6/O׫SK/)al w˰/_1Ȗg VX,29 :-uQXti%̗Z`V& sM Vm椣v$srcs®*ģiɇ @̖Zw%UF`HXJF1kHj鯃FT >2DVJ3C~0#5Ka6@!< h xWb@C¾|%LN~& y4l0G62flSc`fR?n`W6gDDt}uL0[zGmz|=!~`KOPlwBEUnV995k{ C:K,K[Dg' V=UVA-""ȳaR*#L9<@ L0l^}!=*T+޶54ޖxup;lGtJPDxbݗpUb[ } wĺOp{FtJ0jrOiP jђ$&|} f$zbBf_U#-k}P:,0pk-6~zje#SpPGFTrL1S.)'tML $lZY wx5EDk-;$|n%K/){VqV}xҦ{Va2Ą6Kj %F^ۀY#!U%FN/i#wZf.16ߣE6Jl!\H1E6Oc#Uv ˧漵ji-FEh_ I*ɯc Ѻ:֜2.qCn߁œ[㮘- q'Diwa~$-G*~\A_g+SOadz# ~tE_,9WC<n",xGVeh[8^)D`Y m]]^G&6(l"Hx JɄg3gT~&Y9en6iֈӞ8]%Mߊ[eIg+=EmWC:"ɵ]3o8.b7`ʋ.|Hnʋ~ q|P, xYu=Yq=hOo`x(k6r11?WQGڟHʑIw-sV2;Ge8~9BfpT3sxee~~5p ~$IxЀD}36a'luX^AgTwMN {`(-?B= l.pӰOg78(R&DIeדwzNxoEw-(0Ů[P$a]O"LIeדwznܲ<y'-(Uz $*7YR"aɫيFN|Qr iF ĨhVevxH;[5WvWEƏ4kZ҄K]d]%C~}s~fT24"xb ԟ3#{su=n)TIZhI%P:R]_xQ>2^_xв]_ ]DB E6Ih6I[AV'&L<&=*jBI5)BY7GKj%3KNށ,߁VE'w wFMEi D߁,߁,iJ%Ik/"O]H0!һ$aC$"]H0!LnuY"LGZCA4Ƀ!%]@aFA=ZW9(5ɖ6 JA@'0a{%axLt/M1I01I0S?" ƓN`r-6Yn'z|_K||_˸|l }0w>#];fYO'ZLO'ZLO'ZLO'ZLOL-y&(4 ǫЧPt|BBOUSi } U>MThÙz^~QQ~ej#Dm# Zy}"Հ2 -*ihV!=@]KefŞb9?CM" 3$a;l's$ [a~}ԑa>}@n ' ZL[S} 6kjbuD0sHFđ)JuD0 uz"%{-M΂%a7lE[kIDiB Yӕh,g-2dYNWeȲDːe9QĜX( S/@@'0šDe;']1'HcN,BmZ1'@;0ŘP$al[\̉ek99>,k!Z-< LYf“%7CSkٳJ盖%-%%-%rIS9Ľd $nтRǞiEϩ*^c , qT*GV̶ڷqr$x={fRα)l:l=L"ģ(ZLn͠!SV7LX+>L!T7R r T)O=>L|ydJT[ >~i5<}ь_iG}vlTͳRP9`7]o8ܳs,O}ώ};7kOO%gəU;i0|/*@;aL?!Tҩ;Y#dٷ\辶݋70 CCC<e56}H˦de1 &Y:XUNd4WO|-[+SVS'io.Xu' ;=^Zet'VGcǤN"^)z7kJ~ebz4Z-@ئ_nWQwcs!*T !;u :$~ð6>Mc R FZm&Op'h3JV[jZ3\#nף%X=h}òɜWӄO$x$鋉xҦт1M81 "TCQR y3Pt$[=9'p<Xފ|#<xR"'ģl8Z MZRI e FA\,fLr_gme ^h*FmyvݹVh$8~ڪEc)xs <[Y{[x5<[z dCӰOKgS〾hsH&s,6-E.zX6yO_4]S/Сߠ92켎/f6F4h탹|ȸ^PF+RAcc3};AW4:h.nXvM/M}(M^@oRW RԱ !3X$tPClSQqsu;[˴@@."+h OcJSz0tjvP'puavua) 6cfI:WtyDq',T-Y9ݛsż"3Fi@b\H5' B-4#٪Y-An3 ;y.<lTq-fpqcbq#թ QGvbi.hvX: 2ރ}/އ}_Ztd0U. iVUhl^ph''(T΍TRT]ĈytX˨L?",lB_> f߂;6<_nY,\+pɘ Wy,Nq)uR4"XkA#DwBfgCԵ̰4Dv^{Ei NE@a>3@mAY\hw:_8F4z,^o C<4#/h =5hΠ~P回 (ѻ|I:thyojjiSO/(dZ8{FTa/JMj&PYӦqWģH<[M/ZW)$}|ֈdPA<1=-4ޣ''CHtB՚!o_W7՛g&2=Wn'PKgRK8 LZ*re}!CҜYv8;^0x,rϿ 'E1iB|z"wo>#w[,QGW͡١|napA7\'gˮI㰳>oV)ć_E}>05"9>`ĝ &$[}U.,L12df$G+M;оYKaw&WV}#LXXqk x'Ln^hs~fM߰NIoh$o``]@X:&o@Z4IEKiC.ሆ MLg£[Iq1#^}&ߣ)s0;N;u:KTA F%ߚ>6N!-VY}ᱱV鍼Vz# R4djUm5_*o.o}EXM6Bz_H.ňFxθsȬ3\(qzփZ2UkECjy^T+σym6;^X t'%Gi DX=Arqr[ zi*żɎ ]U iorRZ>g;cV.AB]{}H:6!zw?"C8 {XND$N2 B&r"y%B$w̔3^Rf='=fU1AQҁoh]I r - }J$`˰cēFΌ[2gv.X^93<|A+QVP=> oWe=%o`05@ wGlUyiAGڄ- G4tבg1fp}C)q_pEg1c ׽F;1#'7eY& Eo K bfWRD2%t`{8 Ur -?_oA!e1/k@o.0r iC Ĩ&5LӦ2S3UaR,<={ NıNLfasqS{ߦ0Pl |ϙq$^])1qxζ4NƘQi|1a+DIm- ldM1 3!2+ƌd\-w]4Qh4"V[]g)?BA"-4> {`H~ڜ8zxBGn"J~Q__y jΈH9TⱙAx;2Kꙕ-OOecN,[e*7Zv$Cj/-۟o}^+tiv=9o~+x5z?9$~NZ짍RI&{zV0>g2Hd6AcҴl'VixIZ6kGýY17$Ve3p+Wn=pmҙ2A1h#W?H4a"x %3W,;sX=>8#gƷ'Ea/~"v&.OEka+Rz[z>,侁A@$ i 4%_fKx ndbv6B3j|e5aGS:ϛkH:89NP.S YnM3WgJ3왶gV8q+182Es~wEWa5>֢F.F5ϡ Řr< sA "WµlלY:_ }/z?w`EN:ބa 'TǘyJV!EM`" lR >@ *Z =t`lťʔFdB&;`ϯ̘9nB #w`ŐS4H^[Sݖ vB |j IAnlmhOr܇TppzV_W$2+/d<\M" n'lp5kxL [-. Eoش[Zj䇀DkpIx@m9+8# 㑯A)B-|5}Z:d&yW3jlQ-ƘpP~Li:rFљc6GQ3:?lYiU:'Bj$A:}SHvaͦ* RGa_NOkb})boNj/ eg1!|GUJlf`k:. ,Vؖ6 mgȸr*{*Ag mطE1;IG~7?bOZE1jfL30j5UuxKvaԧYHL侁A>@(^M_kǘf|l1lhR FԨuExlᗑ1f)xjѩ|-:ppȚmU(w(jș}So]ށLɤhE߬OY@P}Qp=Vkپn9}TE' +xqOaplzwlߛs^ gr$"x$y9~aP\}C֏D?̛4[w.$#< hJ@~4 2Hy?g^Pt"?}@js`Dtji~}m_E>B+c 9@1e~'GA =-pU9Swr./◔fz\0F5n5윯V& 莝FnN[q! K~g~,א>] GH^ sg(.bͱu`Mx|C7p+ҬR) ;G~ڨdݵȺl~ 9+ջLgkGznԑzY6$wQqVEWplaKwv㖺<~cTӒgY^_ a+Ve#Z ';aw3=$gfC2GYęSgtK{O{ N}-#Titʥ7= !l,UkLv~*½"G`_P&5W䶍V /J}/U(uV@] "*^HKyh5FH؅tt4Z-@]*SM,t{ 8{NOL[a~HT8 \2)G 5kڦkvAvc\-D#Zr6}a_֓/J {|QL{aGCy4gJ'9)~b ݑ01v̡M_ [BUv@[ sxD< i~5!7<#)S"dMHvo2%`J"^~)R!TIbEP%a)L"C0ˊwHTijEGiWD@XIeEJH3 ߘ^*֢ InK^ IJ' 쀭#?$ ;a+hEI5幅]Vd-[ȜfM0@Q~ hՅ@| ө . [ u(vj>&I?" wZS@mjmYuvn*Kgu I[AV'J Ɵ[ U~[KumZäo#kS&}$rD=ZRäpYZ>vY~Zi DY~hTlw @+{E'@߁,iMDi$@vP$aMB6DbP$aM<&o]*2g埁d(I>tIAF@Pj?. {`5r%:PjE o4w'?( S9DI(tS9DI(wOxoE7Nƿ" Sl5IiOځ)6$̲' [f1ϻ/ ʿR> -/+!C| 0w>#ޝ[x]ZL߅*e<](ZL߅*e;](GKj [*{PUeAKW߃*BU~/Q'y%a_Be%J_j6 Qm#( %o/;97m*XI@5uToiNIIV@Y'voDz翅& 翅& wÖJ@D [bZ}[hPf~}@5ѧ|06kjbuD iNInTgO$aMb4i; B=TIhC`Uf9Z"@fЇ˞4Ib3ILy"Lвm^`|E"0j3!en`0 u-f&o DW%a[G +-#BWZ[G +-ۭ#2WZ[GvgI;5ZkM2ND(UM{tJ>\[ DI( ; @'0Qf9}ON/ TK:}e<}Oz2 Msx" I$ = 56vMs(JĚdk B7{?ZTt [5)#bLvwVcN1 6m46(aYFm8)CKm@N =' TI2hIM 7g~n w_GwfM" [ a+MءIxX2ԦH/AMKu, e<$ǒ $r,I%zuKiw(k%;ߵǒDk%;IV0 Ln+]?KL7@0]- [hϼixW7yYo ˿27(#o ˿Ѳ 7("%Bb& Sj?IL`[m'4IVn_Rj eՆt{Զ/PK? EoOiFsjx} ToT*GVζwprZtDJtc QJ7JkfR{/N9VMiŝK9LH}/x`շ&5|ښ&P7Z^~tԵ5x9oS.ւ ;\py/=;>{~̢tG= ?_rf.L)[s N8jyf.sDZåB5J*) oP %u/wtu3oQwA۷|7cY]wW5~ ߯~ظTAnٳ˙ 0a\%ݝx'NJ /PS֪ J^lRUcP mŵe x%A^4<3fɅ7a3nmh}\:w  !3 ^Ӣ.ػD|kr W#kZl-F5nxl-ëwjhZyCw3GQf1 י #.t\ӝ0'03(< zdYg44Sy#C SZډڊ>_xjg,l xĥժ^'p2kFVBFt>-js=`)+R[Yة}o.X2 Pk~ٵ1l΃㾕zm_YVBmF lV_Gz/7>09̨o25ăJxݐ@bN!0鷍侏AkzC6%ӵVg^i>l^J,!oaVc`vYِ /+F~?zq>"_TV4>.XeV5Cv/t˰YZR֬<|ױg8`M|zbX:쯧?`O4S [n1=9Ɩ sXrz%Q4s!QtP(`0X7p0db,aߜU QW^✕ӽ9\닎,=x>c䞙viz(=^Hneʫ>K=YcU{T}TqnviNKX, Es\@('`md?m R$pr60;zG%)Sʔ;Χ@)mi{pbJeB&kFg89Qi4+q3YJ8{"r2*;< [hwi_> fMז`%-5 |Ѻr.h=itZ3MI/2_ ;<[hgCA][][qQ/n}:NhmeS\h؜ހ}C9jS{U-!ywMcսhW-wD^DPTuG4h #zpv@;%aÌ-sܵ1;Ue¾_<=|}AS]? |49KfWS7gB!-ڎ#E8oz9*-IXFߨ>>/0DA<.Y:A<1= )=4X?,"^zD'*uLj &I;x>!iNG,;Wҝps[ˇh;ƿ4td1i)t3[,S밯Kj s3W+sf^/N̗]SwpMļa[`<~ŃEހꑭ-'͞PV$;SĝtV~0yg }uK->N `3uدU6z9%M;оYKaw&TV͒Pl+=n;arU3Qr7X0lmM:^ ;aw^˛QBr[n#m~#0JJjSμYِͣBتUcFr~EuʳsV5qi짃o:fв ;6n,:R;zPR>LT4!|XJdm]Jә  *E2SSgV>$K|7侁A<usbN9Y1GiѮ [hKTuل#:xοӐNjd41U l$t&ŵ&⅓D8DCGG-S}3x үY2ݠ*\0/ּ!ƄbQ+/<6*aE/70(^_H`KV|=iL<4sm$jjCj)F4:ēv]@fŘGzT)cԒA'%"]#g/Tʴx4C_~| _{;*=s <3RЃxN(--/M2 $E)YŐҌ 'EfU wu-O|# r <tVmB ~C8 {X .!Dg`@'W`2G ` -IVgzΰuC1x=+("uxJZ+lv ʵ{Zh  -h>Pa~1꾏4a ɤ/7߁Ngh 4@i1W*)ϫ{"X]&w!lkTx1|אLV XOBOj!P8Xݳ>6~׊YAd欂&|$ 7:FA<)Y.} ;y(UA^)iIM83'{ ycFj׷jb80#TNƷP~x[wuxA5p8e׾;4`RRЦXE_ҍx}^w %Buᙲ+z ;#d ܜ fJ1&:Z] z)@(YoE*蜩p (6!뵽ukQتU"7']FbO7}*2"9;ݰewܺ%5}SطEz%Gr*(C̰ҘB&k~[F6uI|`f8]# zzޗmATo*8Y -Ϛ !&7q`x2!o`O41I#ӴKfLaxL,.f/%#9&Ӊ) ;Sl7 6EVa[x]izx뼍W dVCQ ^x [`>~Ve3p+Wn=pmҙ2\)|A3;^H-"qv%ؗV>n\<z| œ\cq4,p(U|>QeOUVܵ0qy ,._ )-܄G70Q=@je^նW`j&`W`I|`׭]ȝ=,M6S w \*hy]G1 \?ɖS~Hx'TKfB|u [ {tƜX-ze˛/-7h{yEwov: \3!^}D0-L7ڹޗD'f !btGxiiaf ߶R"Q}z8o Z[ݰC -`?=M#p.+#^9Ex z mpc M!RB\̣RB߈Vl|-aFd BwՉ`l2AMF'6F'ssTt$+*"xPqgft%HxgڞYĭ@8Je5a(&G.Е(et)XnB },(幜yr&0 { +1 )|טE<;kzt kq.}Y&= t$h-p&qA7_0$+IlGо풎HJN #quƜ3,GYH+}WmG}E\xhuUTg3>YA7 q3a E*O&_]lKoQ\ILN` Sl* ŘrGAWZh@Q9eފY>3ubzg#lw`EN:ބ/P-wSV} yURoܻJUGQ!Ֆ4[ԶڒFcւi]:h旧WK) xLtw_1sżFm^60bH'KW k>vkB )^-")]-ٮx-?0*OAaU+Qyf`AsU7M/,&OBu ބ-4ȟy'o KFo1G7=6V&VuDEv9$(cNeoN ,0~G#^`N Fza5Ibrx$[hc(Iϕ/7ÛVdngLY1Ҭۧ{a<(}!؇KO2(M zox("rnNxGAs]fHD ?ap ج4i琚4ɬj`~b짊eؗS.A"2ŒSޜ^61W?4߸g~ _-" lR"w@u3[eE pr8[n2]?buvJ;۰o2^cw`ܝ GrA(M-?LUHT8 C\2qr j|QH.e#ݣhXAw0?֢h(Un:l=`/J;/p?h#X4h?;`w$/1v!;^uOJ.](w{`W`ںB4'_45QW _A4 'L[F@{3)<[ljSB)V$̴"%{)V$̲"%D+RF"BZ*Z)Ё)V ifY*Ҧ57J?$ `%/IJ' 쀭#IvVЊp˓J5"ks _C4kQ"kAA!kA넅!'P-|)M$ܥ:9IئN@DYG$쀭trw 狆I-DIU0ס_2&:0aүCY7GKj3K[J_ /A+͢Z /A %heV$%K:Mi MBDHt.8~$L (0&Sl$̲'M I~YKueHZ/C_Rː%a o4w"@M-oBe --+%C|-0w>#ޝݼ mTg~m-߆2[Ku鷡ֲam(GKj oUWʯЯ@_Z_*BU~%c~J E# w J߁(G˸Rm-FwP@~GKߞ_v|s"oھULB ͚y:*](w:©#R"5j>.Iz Lns M4,uKhPzT>}Khp7l{LI:U翄& l' ZF[S}=YS#߃0(8"%@H$aMb4i; BTIh_A`Uf9Z"@fϋx>4Ib3$a<>4Z< LS*U-fWy" L*Ik50f~\ A{`uѯA_Ch- 4i>~ 2F25Md֚ݑy`$5uhZm~] ӯ#*>~$[lGN up J$2'$rw_HP7Te~Cxu-o@;^M[~$iQ0#6aPFU7]GZTt [5W) bLvwVcN1#Ȁ v[ oJm|adi~N U8P%aD`0 ?* @&- uqHP5ƧoA;aBD` P5ƧoA& $N h,jS'h%-$80˱$&:\չr,m(ZcoC2K66IV0 Ln+@mZjbIfz(J5s|$IXܡ̛ؖwա.|wjSO^)PjO YvVЂpKu-l $Lq͟A!w4I.sϵTw9Zƻl@7GKm͟C:l]>(z{ 4S/5P*whU`!.m/Zt_@MJ%1MQx^Pe(Қ^g͋w3EZ5w.}9]-Qr X| kk@-Bho4WZk{=m?RP2״TG%Z0|sxp N1op᥹ggϝY.=ȷ;|!w4oKÅÓ3e?v8yXGsA5*쇍4=CY0_U:l_ݩwr~,5U;Ťx)~%'6WQrX)UE1(Z6⊇zAosN?G1iAoA-6R? EoWuIzx/C3@rY:4 AflU 5.B:Vȃ tʮ匢c>Y̅E D8{\~EC!^ې5 m+ ]<(PԙQ- kQ}JaYX^*[F7=C^˻aNr؎2Fxio!g`汏{Pغ`h%cuK{+JaGAۢn坺cP:CܦU#}suab~uO()&_wl-eަ/ZEkK=9=&R?oP@ԑ1ܵXVZ4Vo(Xj(YJƼA2`^ ~{bdo؊}ZAcc=Z_7*Ǜ(&0^S؟*+\~df|A<<[0 UtпY?2a_;2o;H/iHZ*`&Vrؐ}AZ5 Nd'q#<[h*q>׋2zyWwji~}m`zbeI=Owj2t@Vحv,hcG%Bvd(MA_n΂ ȜS5;H7鍀҈R;Feu;`ɿ sAiĮY^ }Ę: >n|T7o|DfVض$M2GYęSgB}IiiǑ;sYf^c#*{_ӛW!Ƥ,^ sI^Ѣ +Z͛ rqSaR3eW >I!mUtAn jnIJWB.N`[pUȑ Т4;-8)u 5C[u NR UvjnIOD`Fz $̲$*-4sW,vd8Qk5oIJV:2ռi$)CZ͛FR8 ȸVE:HC[uMSRڼ=V]Ӕ6.`ꚦyz$qMSj$ڪ+isS8&Psހ"o g5:Eހ(EE! MŧP m1I;R Njh恽B0&Iإ)) evkhJODkHJoB`@_[uG"*=\5YNh 69D' K'Q"إe#)N@ݰQnIi YLW7!˛YK&dy3]ބ,of,ћD% 'IߵK ߂( SƿQf:'oAoi0a&F>oA)nA@;0š-(0ˡ&7T Ze7iǢk99ކ,ok!Z-< L Yf“%7CS^ETIءtetE䎖Rr){ E JMk]sw/}іQ Z]2[WwO܃44=е.OLrg=D Jo}y}&MӜ4.O[uaךWUj _sj?\g xK_dv@9"I^ S !רnWר8V*Ck|nBT]Vc#! Q;{j\f-UO/sZxi? |jxY: &UYEj5ҊH--ż"5NlCqSHe{dMEjL"5Ѳ6$Z݋Ԥ{xbUӐKZ݋ҢT0/Ra eqZR~Eji)IEji%A3@rY:4%Ejߎ~Vm2mvup iң54=ku+lCZjWnbnR9m B("ܤ@M ۵[?`R_H` uc*r -/b"l0M>q:cJ[nP'p᜗t+0aiҽtB1pe)7gس܅ el{ RӖ:r+@2aiا+$_fPkqRReS^a-ը)ar W$1S3kv"[`)& xt[3"!Fq|Pb ixf;]33٫ wwIPn uSbvx P߉}TIJ rH&WWa˷n%cT'mV7/p]{$S5q7.AB ?|f{*ڊ7S>b mli3ƛ^8٨ EG$I &F^D5x3rr An)#T5MYEKJ=TEzfxryRv{'s8LvE9g!9"%nQMf!O:ke)$ܓd<(Wkoqrf=$53DQ\w҉M~pI qa_O߆vcBr7 |^ ߅4֠pYzPՏCتUcxn<[9/HM{}샠_}:bD3囵}q eo)iTʅi{c;`p`\oAAʉU={6q+㦿L#,l' :k3E˛+ ,6/+x "v  } xm%uE{Kx1M.wY#~"cӔI sr]rvVٽ`XF~Mo"Tw~_$< ; [~N\hsS1^-v Ġm^QV7?`[O|Z?)1`&͑v!hs4Jyr;Pj/oI!wUaO-RzyA]F<ӏ5:=<[ԉ`vNY!|qXV`)˻g^%ֻ ڪ DWh[̛YKNY͠hέ<"{a*6k~[pƣWn?lJYRExX$Ԛ յdQ,. 3 r1JLq{1.^HG2 D1p2Ѿ \h~AKDXǹpf2KҡRm?jr饢3XvG#s1'`@Qw{ݥztD"[ģL ;S&62v`|@ih8pL CkD;N2Cv`wIgAڽX2|o%Ia= >⮎b7V8(CT1޾c\:`l `k=RouTV5" 'QvRv[;ƻiJ5}2Lf3oQ'V9b\=\T:NrV>: ~}2܌Kc=,y͜y@jfO+)0"sD0ش\Nہ`PRS/n}:m2r A*zUE؝[hsA"@4hMcĠih;Qn21,БA2gR`h t jQ'+4͗^0Ǟ;0S |qhg4mʙ$>HE\3c-h2vuQ*{ZrZe!USˑ cL QeؗV;ܑY0]!>Sx[mCBk tD;`[ҢC?d$7m!m⢱g{ kzlq V.3:OFģ( 肯\ң&(^:Fq)xjuHa,U oKr6Bs|!F# I;.#bHcp=ƕ17K"5WNVfF:ax _YiZ liOKf`Yb#pUHPZh ;Dgx+kH+zKr`Fu@r{ҩ&#QɲZ zU1Md̾ɩtGv|bRhcfG"h\&L ׯ_{O [\uOAߠcD7ċ~ Secc\hu`,L/2GќcrޑysqFzo@}4 1gA*MS -ĚsE'2-#dpHR=zQF<q6~k|z\>y6h d5.J"m5*H D[h@rfӮIьͰ3(w;F5eue]$ a+VĮY4S'vdK9|Tk9E-$a'l_k9 [4 eIgNݏ% wIdP0&HʞR!4}nrވKꁴrל̨PdΦ4ɷx$EIp2cF^rgo#`4C={PG< [a D|xbP6k6]w%/͇#$4;$X2@TI [$P"6: }$̲$*-4Q,vd.D.Ph廚M}%]SS۩#w!w5{%. ȻgW(v#plvOGZNIv` ||=*MءćXK)6=(=LUGAAU{{dOAi+H](pM_uCT;ZƝ;J,;\%Th|!5<^^CCZi D߇,V⑺D߇4 uz}I't%|D@OҕI}Y>IT~›4])DI)DItS?(j0!&F>?" S&}Ef:L"I@Y'0aR/;I\р, -ހ, -%a-<ZR-|3$:fN3P%a#rFx$?"2:*g4#y#3( 1v+)(4rHbY}!n<2).b[UKmkfee `+r5nY(@)50Ӷ~j0ŶUf9kL ђ5$z/,Ipr$t8Iځ)'gH,prܥs圖F9PjF@PjFOs%alLu(z{:jY5C$wΨgBu3dXVd"^[*F3}!n яn>lT7\r^0BQ8ܳs,O}ώ};7kOO%gəU;iv|[>}0gԝhz;4"勱.qцWqg?l\U8'J'.SO):Jrv֑3 ̺Swb F<ұtjЇ(4"ozJMZ.eϘ%qoU%HK.L`,\6ҡ϶0Xu)4zk|f4\cBBU]˞ ał<>( D%:'aWV^t.y=|YHQ(չD)/¾~MO46#bw׬aFma wl8+[ )P9yOr]ƤFȒgPxdYkJ^i'㉽z(16i~}ZEh[UUJ5akRgAn+AX Vҍien`B-SbټHw/oM+8lCZmV$Tg-rߧd,MR}\!.@{'v(U=|/m}TZt o }RhWvvS|ZCF嶕f^{~xĻ=u/&ǵk+.Y0Z߂wn2KRMt9x$SӿU=FeT I8Dkv xW&cǔwGaO#wG'/~A<4^:Yd_.}GaGأU b0_Uf-B.^= [~e agƬ*AhkM7ģH<[M/Z:W‰Fߨ&0DAXjZT;qK_QI vB1fԕgbw+qyjD~ҫ՘eؗ $Vc6N׺Z-^jDX#ځD~Xj]!cQRW!EmjiU H^׺Zzd=%o`PM#b[m~Y:uׄiRtUWI.Y=Z/Nj5±e1g?KNk&ZMGW1qj]Z1Vr\vj55 RfV'#SƯNG$/V;ðY)0S@} *uQ81̎ibI`FNm fI6Jo 1k^n0N5n0ۇ׎ϻek% ZwDi'GUM L7 ! f~5kP8gm#F`Lk]+\=w߭-oAv* lVKJG&ZDg"WckKJGʈAi7~iv`h>)TIء BA5P"X#XR eCeZyn`r f!ZI 8Dy\<=G 9 @CǵlRqZ`S*x 葰 fIiH(u_VD !Ҧ,)m <& V`H7"Oj5c)&ΓPIM4:OB'5:OB'5Ƀߒ$@#NAT;SZƝS;J,;\s`\4OC+Vi(4RQH4PV]JOC TJ{aWRK@қ~^^g KW'Q"إ$), a+(%=@](]bv$Lq$tO:)BglG (^sP$a#sP$a#%"Lqt$rD;ɍ.1,GT[rD˸'{)#%a-<ZR-%fJZƃ("T<( 1v^׺a/}ю Q Z]2EՖոA:GEj*;4chA_kk"ڤo_J#k?X%P&>;dO&VLy&dvH2Wj̫XV'j?yALs5BKpܯj_2k#Wce(M7 seטsJ+w}'xseFL8hr\^MS.dgkDWoJ_X%+礢K2hemH թ"kS"G*rS$֕ecEr0 o3sf3bqAg Ns2iP aE*y«񊄨lnI^$n=p+yU7 ~0f :5EȞmnʻ p@NGaX˰qTP,Q}xk/^-4E¯%ؗu-.8e_/Z'6wa}uLĴG߄f:K6?Q><rF'`O$_]'&ҊkKނ}|3 |%DumQ\4<>8 < p+2<[x̗?}㰅]ɫ3$^ŷmŻa2k% &Y:mHH9rDZD(i_Ȝ3^LÆT#F$cTV00uH!NaG^Ӗ_TNMF.`@΢igL 4n|V%> *Fe7TtiF>hKufޤ]A,i9 V]D$a틈ڐPDo(50(JѿUOAXB6µ̠ 82K M@.B6$[6~]$3uRojT` ad%seGu+(\92BҨǤLhQ J!\Na_O_ p5 vq ~Zk(m "f3Ke{$`l}NZ]✕ӽ9\ l^PrV h2FFo~[^KNY_4lv uoM551K4KGhGĎ:~8`otWsͲgr!mEIg㎮K‹*`8F Ձ WL(;uKx@"vt m׀a ukE{K$wga?Jp5> '<6MAQ˶ &~k5kogA#`93[y}6aB+|!wM@Ɩ̬z(>\<;-#b[)rAZ|sJKȜ̧-PGlݔV|?Q;<[~B;n;v&~q;8.n3le>{u zxv˓` jO O@Q޽/{D ء# u~@xS yi`p*ZtX]ބ-v+'#˰/+O߂rݠNL`\|s6{I&ʉ3"zsD}9e}|[\ASD?~i$ˋ(@q)ޮ5 9 RșsQ8>^Qlҍ^97GlJu]GN42A<ʤ`3unn-lזFȍ2dF$3d vtf)[ dv9cqWGDxzQ6g}Eϸ?K1`lQӚTq;R:Q^oۂ,Q/þ|ςܵ` YƃzU ˺_vhL^zzhö)W;6SF(wt4*3!cpI15>LaS`&𚿼̜&] 7` Xǩ5hC 6 vPBҼ۱?5!UDtȄ:_K>6]':#x5S4kI8^n1d?n ܩ͜cHꋶfI6m¡my>H=DImf/Xe%^{htpTH&Ŀ\*9o --d@ %7hlF!i' +Ƃ5K.4ROq&FfCwZgL?b<;͍[GZ%B@Nw@6C7E}qδcDl8 {ZZg91l|ҫ@ [""w={ tvy2X0A! T@[VDUނ-Cm2ݢ #dx"* Ҩ]&m6wr08U J.[ &n\-mn`a)сؖ>}_< tU# <[>ၰKUc>W.,=bO-5`Kz0xQ׎K?i% Fa6E5qrK+2]&ujiFAP]=aY'ߔ\:; <.{9Cs#Zǁ#auGAZrpPkZ{aãn-G/Cd"Jeؗ4ܑY0]!>žMG#!oַa?T&9[D;`[Ң>@?d)MۣY6LŨKt)*!2~eXc.χx5r EI@7^Kecx@@⩱V,U4T%'E:onRkM1 32+ƌd<Ji\}"8mUf83t!,}`}eZԴw߀&&p3vb#p |T^0`Z!m?8erޛH=^h,侁HjާJf*X9c9S^"i7;eSht0Q~ cF2 ׷ҸB-5pAٲL9q .D~K춡ZXn9.^eR2K/"cE-k8}nxՊ-oܭqoބ-tVq; d| -g=EcҴ)=qS3Nl{Ql2;*twϔ}vɥB$2aiD 7M:uQ}wiEiep\x&lc䚵)%ƌZiVJ5o 謮Vtiҽܕ%< [h=xe쮨b[AW?ɿ „rOUlوJ0ŚuShmH%4Cnw.\ǘ[Hֳ\3x)@ҩ[P QT-XP43z'߲|w h - NaGb'L ׯ_{O ͱ\u&sf'~|n ֛(&xqOaplzwlߛSrϒIEH8sl 7Y?2a_;2oHo?7'H2£f|O;F5܁C7Hi"eX~pD}z` J\Au^Hnҏ'i6pp=1UgPD56 eAXѩYЏ姗%B~3Tp;;2@PTDY_;F5u°HY C UkTd>&VsIR]1  [xi+ A(5XN/x%A9uFE{DD/ҙעHʞꕐiFt^6ʖVe*TH/MѢ!$EI֙Z-m#p/lL9xcf/!=h# B!CKPa+lO%t]?';`J^%ȑ Iivn3,Q#vG $- U(L"`~UfYyn`r0s.D 5!>r(Z.dꢄgSQG.Djw" I( .٥ HXSb.@ HFM#d[O^ P&>2P)-J[BN^q$>], _O( 삭֑"dI [A(D }(~›4<6d$Lq$tO:)CϵlG (~ mhKP$a#%(0ӑh8RZ" )N`r#_v|6FǐZ-ǐZ-< L$̲'=@]KoD|I0'P'ZƃOPD>RU~s $n%1ޣWmd /by0#a¥n+ mi-*?͢L 5k-4+K? ݛAmO~KV---_ 3BvSȑ 4;P%a* 3=;"?Uf@=Z[Z"w2 Q~:)Ddا(!jN} Q~e;) ȧZaY^+ǒxiAi.{}e~eEzڲgP&a^ܲHlEf:eKځ)N~$T7e=' I!bT:^xl[EF?EEUKm4I&N` Mv+:Q0B&`* Mn`hRpA)?10D`MKmAY?'ZRef:~q-ՙ(\xtSq0˙|g:~ -ՙ2Bxu-2 f: a(N~? IVՑOBr$R<$섭-O(_S[)tSZ/~ )M2F@POA=F'r%:pl|-nfbqihPeƧϟ& wÖ 'O"섭rh}44I.>^`&{tM}nc)R 3`جj#ҟ0(8"%MbO?au^L ģ)~i=y,cp'FEx iul]?Ңh{`l i̒_:\ygK?Q8j~a2_g/5Mo47+ߵ߽)kkrߦ4\r7 w ?^{v}ܙEҳ|{ٱrGfI<\9<9Sc'N>q47T_=2P%B<.m%'QAe^Y]RPҎyG_7Ou޽}{N-1|x)0BE~UWч_ŝqU^Xx(Π,L/ *6/t;9?VeGme,W2bs%'R\UU_Q\PN2'_ᙑ.NLA 9u'Wbp4o#G#@CWj0{Mn[E;|k ArA<@PUPQZq_GfՌVƐ] Q1Y~)ݙAȇwk]CxAY[~Vb>~V ̪Sw6h F<ݙ![U\UmK3fk%n7j+:riec#( tzAd:~m>;.C.X&x|c~u 8{.rEŗrwxކ}[`;*oNS:9箇-{@'aI: < db:9)ا"ЉL G؎hv3կ6 z4 F o¾^t9a<Yj=9 L wqTCҦcB /a+BEG8ē4 |w^/HD}pany3.z%o-5q2 }GϖC*܏s'\PH^WYJI 6>ۯJ0r#@Zv5V?>IujP:5(RKVN bU|i;1P&![YVG$R"0]qjsWRaZrO42H Zó1BGJi0aM]4kj] +DZ3p|vZ5=[ 5َBY D$Pi-гP%a 8HkR" s)LAX/y tKj414 9q1`P"ocTJ+P%a)8 L"Z`)PtgV8K"%0t$L"%c*R H0 H0ՙ/"p8$ Ӝ"'|u4ʁ 躖  P躖 ? a1kYdjhIP$a D`P$ J:0nRi;0id&I0iYC0;(+aI=ꁅOtVߋEִ9n^,/eK"y!i~f)!i~f!K}@3,=K3 SܳQ"0 TĊit$-S(׀J!x^" l/A6D`` $L'C.C(E](/DC!,eee0('+Ph Tyde^a@WXA+P&(+**Ty5Y^*ЫPdzBBWcU(y/L/*k%a5Kr%_(tk( X|UySx/P,ѝ*_B_wQ۩%IzƷP>K?v~M3.}~M39}Afa1}~MO 4; ^07w%uDJFJ11^0 5Z "%Vhi(U6߀* -݀* S-GK7J4GK5N>gpA,4I`3? MA`,49m)`ͼ7!̛,f&y`H?i2S4tKP% KlZTI8 LpZTIfIGUtJX+%-@ ,QDR-,DGq Kwŵ '.H!HxT;+͇#1RjÖjgŴz$FGamA1]ҏG,MTG,MT G,MTG,MTA(:*WjS]_C_D;_C_;_#k|~ U$#:G󅂑s A".B,"PcEhL4X 0q=kC $L"p HL!KQaQ:Ǖ׺}BW,עO 'J d$m>,$+'哔%|Dx E&8Vz E:V"JOH4JX[aEA g, d\S+g%a(j, ]v,&H9TIp9T<"%:U>gQאԂW/įXev(S(CBNjjzaqR9Y Ka]e"0LEU&CX_=e\f I._],Y.C,W!K_=EkQ[k ݇a!(Kl IZx.*?!mzѮ|/E9N~Ѫ#/7 r|>QI+2]y0E2ViL:r(%H-pvt--rpDԤ6|`t}L!< ;ŋe7/ gOmk o)&A"SM7E(A-նo3;6c0}э_C?QH!^oSuӛ5]eOOooܰ6>c\ڸtfng<2䔪͕KٚY__qp+3iLL4Mҙ`/ŭ ĢXz> R lY+c^niVӖ[.jV87`]~ųg [IwS22;W^x۸( e9H̼0&¶^X^&iPvg]9z.B wvLL[k U|V_ 6|Q+#ҽ.Y֖lj֪$ikCz(vr,,kAk/҄{eh gzpv/2bo?0L!G8ēvPyxTz`ե!~K\!}(WE[sM[{pٲVn(l,Mʫ;l#>af9SlU#ɓ,r?!jtBsQLzQg_dOjSSSڑObv*kfk4YS-isx$r@tYf'Aj !؇dy:Q/Y^wߎۡ VI-Un@Nk9s.ob*.aqmطK 21%C~z5\ďI: < db:9)ا"ЉL G؎ʊ4!AmxD3hx 2ބ}S W,MJS!:G. r tRHEՓIx֛QC/N*ӭ5/jm+Zp+y[hs˸g!C9ws(d$Bݫ]$T}JsC|ȅ~"Lax Fvd%%dbܙLNjԬ535? r[Yz U}BnTwVq~f4-FuÎnkc̚^}9^}E9i퇔 [.2o?].Hij!) {*MVnG6D3;.ձnyM1al:a1|D׽aSe1bqK| VIE6FR2GM ;<țvY^>κڎCa3~P/ۍ" 7VQ]^\xgY@Yx_i)7Q"j-;)x"gz5Vl7֦&=-Z Nͽ7ї& _[ۅt*iT8 ؆2}+(XƦێtE˪|uu;:%?藎{|T$_)COӑ)p{h9~Iµ=Lm3r>_ރ}/ ['|$ ^y\B2+:&+"{q"oI׈;i 1OQM7 WDG`v9 ڵD98{GR%/>V`W]`v5.`[ݭh׻^s*%ݡL-jvg`D@V:*#UNSZ H8#t2_ TyǏx놿4.Qmvu|^x2o yK%F^P1wTp!8b\[uє ; uߓOd!a,X`%|7Ԣ0DCʥ m i!D@om2>Lx +:L?3|MqǓsopX3%Z3v{N\FnVuf Pr1'bA4&ℿڱ1]O8ģcэF8>!҇0=?<gvKuQ3&l(Uٌxqxݺ=L[=d⬸t- )d*70S,ܽJn>./<]]i#RL{h8AK`4HI C=ts \I9׮wVv2"5:K0!T3[F3ԛ5Cd؉ qz&8Yҡ׾iQ69tn0\xSdzm-3UVbuRrnIѝ4z=k!ۛ38v/(it],w-hPiW.nA 3H|Ƈ [\@IVg1'&[( Xg T9(Gqs$g;n>JND`棸9EŽt  gL7݆$o7%ېmyZ|Ӳ?2r"H.y%ڲ߅"ﲔ[2.y۲߅* kٻ)C,с!iG MztՂQ . -J{T֕W@[X&w@՗] $~Ňp n}w>;_-FB m!@8;Ѷx]OmJm1>* ӜK #Q\B_B-+<AI d|iNE xT&&Sh"ZL 3qT-Cw k0k0Պ&X~ UY`)Pt\dV"K"%0t$L"%c*Rɯǐ$a_!IT' Kl1$I? oKx'h D}cAXägIϠJ4I8&x >匪ā!JV$|U(*HH9Z9%1>,hsHPc qyE&Ŀ" Sm0&IfO^u)sDKH%Kt|R,_D/!ɗ,KȒ0|oC21W+趥W+mIUD`4+p\OM_*c[&Q&dZ( S 2!`A%0 d >4b^t92D@! Q.'+er9e.C˱  9Q@+,8 TR3@+,8 Tҍ3@,8#Pd|B_CUku } UUhH@@ 6o 7,F Jh#|mߠa1oVyU8b(;t}%H-%Y-Y5fP&aKC, e&<& `Gc8D@'`GcX\D`eXL@ѝ%O 4>s~ a~ ,ھXH0EK'HP3&&o!LB Hi`v&ҒQlJ-$LpTIh&8Z$LsDGJsͼմC 6C6D``3=4=K'6u}4*K_0WY<&̯BK'5jX]&89tKyrX?@?t'@994}]w%zLDU "TLt#Ie:%gga\][˔ې$L0|$d)0;0=oTKK4|K9|OFK,|IYS>!iH9kq@@ᜩ,H{OUꌩo%s'wo!ӌ(+2v gPa >FNÎrN4#a?IJ[u>{jO..ATI8V0JTI` TIfIGUtJX+% KtW( ,Q\% KwW@)8GqCɭ [ –jgŴ=-u6q`?lvVLk#: k2l^"YסuFuc%Qz\gn&CXBqչTxR2J%4J45 v>M0'<(Ԟ/cCYP{r=PcEhCi.&`| {d l@ سYzb8TZ}$& ȒpvETXNq%n߯Eh,&+"dYL[EȲDe1e!bU9sQ&h*A0@S ,tM_aEAeȲCːe\2K-CenJGD, R@ +Pex[_/q}:̤\L7݄x`kg?!2ͤiX+d Iuvˠ_!S gOm _#S~xt3Ȕ͠ ?BjDr鏐3)ng%%o-[ ^1vMƯ롿(?yWelLW@wMݚ.Tyò立7nXn|nkS.m\i37V^^rJJl,/]կ޸T啙ܴ[0KzyVыf~*Ȅ*Q! w .<#۔4yV{De%ײ[U˳Z+fM>XC_<{l` ?ۿz;aBPv;Di70ˋ@޿:Ьe-SNJ5E9U|gEC _JF2ulWl8NÞV-|~C<4oXytSa2-Vڽ B?ŔTc UGaK%PKV6FC-"JCs'PhjkkQ8HYD8{"rLتG^}!"_pG2~.`dAxe/(=MP j#+R]$Unq R@S*dnMSNTpRm b #xsc"<~kسsN[t7X_n}&p:ggaU)t=!tRH! <ɷ~C&Qͩ^E%GÄ3qXqÄX >*VSڋ*ulMY kl{磤O$&XCn E_i[-=f{ۃ9nTk=[(Ѵ[SkS H2 RR&,. aO>9 ;!㶕 H0XhˏpQmżpM2޹Eńr8 {4֚~qxv㆐{{7PQWz?W)U+ecdd(Ԋ-CM/R_)qO˂ѷSnsFILi/IG+-ހ}#~q8 {6"! n P0ؿpKA?4<[o)͹%5Z$MpvtK'`GgC r~vB oaiMYd nڛ'â+2vk/fp;A,OgaKUb#w*hSvODok_J2bb-S7 v[Nr'iH (nCXKB3-aeo땼-v .þD-Fl5ہ>,c$82 ԩJC9_t{[|#r:=fw T(e "j)`i䜊%JlSuь[iIKylQܞ e/eUaM91R(_Y7)bmZbinPX5ٵ7l?mއ}_E.n}S g.GAlVYu7*$fׁa?*$wO`?Q6a]gEV7bB K@8T4l_M(LvpG1U2yyӢ͗2PyrR#۝:mZ޶!djްsYm,(!ArO4 s/uT+aY`ɭE7$['Tң֫bDcCNs2 6D$zET+ħ[JbZ!wQ5ӥ\(4.V ! UW)v0s;q[؊D *j"zwGy" ~}\7<< CswŊ-wo۰o+G+obNif-o^L0F;eF~BXOD8~+Ѹ0Y媑3 fNxG/@Q@jAS\Efti| _FJcߊx+x' Fw%q^rJY$lq 3Cç`p+pV̽*T,1#7`G7 ^?"}xuY;~49$7%x*7}{]s98JI&wrkw;n(@\FؙJN`/.8펕RC۪aQ!3D^ KHa•Up\u !$x~8 {2~U3C.v \Yµ ^-l86wUk'}RqlܔcȘװx8tyA&S^a/')+WkDm& Q!mI?05znS ; B 7zԪ|v5EG`_dGhQ2憡-v3Oxj{%黐L}\yUj @8LnPmϥZ|RG<U+fA52SRsxfidO i+K&&q/ giӰlWP9-sejf[<_s*U,;Q9cbژf|*({ ℿ GjRvி']O8ģc&W)k.jC>OLjْQX[3gd3gRH`4ܙ| T^7JNNlx==3alzjY -$`4ڗ>0m,O C/Z7J)8-PN 1$'PndA愴O#pGܷq("ΩҡINզ;_č,Kr%1rg._"plZG%pp %#QXB]j)s\nm88Dː2]:yeJ4iR5L!M L 2%c3 H{Azt$L"]* SHI` TIfEJGVBe*אkhE|RHL"} iY1`|ig>@ww0* $I |Irg%/O"p8;V$Do IB,IO]G("sb} Q.eu*зP[ -DE9u#.P? -|*Ў|vᓑ97P$qR艩(TN"0<;oHANau!R0i0eIB߲DIB߲I"k&} U9L"#Q0'}d8 rFUbww,?_AA,9f ~i~ՊD,c<+J;HPĻ$L$L'H4x?fX[VYf*Ky YD*Kw Y7mS&k\Szvc]iNEa VL?@~j%P) Ӣdh%#k\h`G0 &d$L3D7t wqq=wP$a=P"0L$LJU 2UR2!L0TIfGY\A&(tɰkEaPBuRO[:T'PSVU*Wh$L (,.h%$f!,K Eɲ8GT8A9PfцCT2sHvQT)jL!V-IzƷP>Kx<4I8[*,)<4IxT孪O"0TZ>$at5IOfvaN2P4E aHvQ)*uDj@l- L%TٔZ[_* -JTGKS' P%a%R\3l2k$a4Ij3O 6kK'6u}4:K_0Y<&̯CK'5H1bA&tI̼ ],yd̛Хҝ7QFL|uR=%z{h=Sg8ݏ3t '(ex$K+AejW<;Y=D˴K'Ƣ8 gR$Ӳږ-|TLFnF7~[m~$פU6enMݚ.Tyò立7nXn|nkS.m\i37V^^rJJl,/]կ޸T啙ܴ[.Kzy?Zv*ȇ*!w.ýB#4yV{D;=YO[n9<+Myӡr*/=[xJz\_r Dh^<awrfy=0Dˋ@޿:pRzNCwv\Lꄇ~%Z"xU~3gEC _Jλ}һV3lHQ&.~x$h/N}tq}TZHq{`K>cq2ӃcRz[ɱG:Irs'9JYFZEjU~ 1byBb)!8v`\:Ȃ(&xmtHϤ_Ŧi_?}:MMMmߎ#=zjJ=Ak~k&~qXSP=t&xZU:H>:f[h Ѽ&')H ApvtE -_去8{B`@46Wv'V畲-dJpNX1 ݞ1=Yz+@\n`?q<L=ggaU)t=!>*N>|H9ē4.@=kƭEڙd{ y8}5j [VugBtE^wnmKﶷIbi/ \YS:R§__>RYmwb^ʺikEfe wQ튋.OJ$ZM[~ᦝ(~ \L~lN}q Ѿ \-UL[$?_9Lw`bA[37 .z%9鮉٢~۪]t (v[zQ +tsnО&_ 8ē4H읚US;`wHY:$U-Kak\*e/ .%Rb>|# rR"W8w]Vve @<*yCVް~NhfiځaK͜dgJpGqvjoܥ~McE8s}(%. xwdJH7TI|*n br^nWwQt]Lp[K&gaVΙ>m܋V5!dW`K5M.TuxEuP?P /Bër"8^"&'r2ln]D0\ ȇ[|NA&!"ր2{ < r k#{n_OX3Dp2[ znQ ?$~׮^jlD˂o~wqpܐD(]}sGAEw%Kr7ţڰT*mnU |g`M1+:[׊53EC/&vRjMX)UW۹uOj^.>v]6Mc"0>@̝KMj JɋcݸY@\s&\+Yؘ}'|̩Q2e.Q0"0 NM% 5p!yO)܉ nSo&ӉS1Ko4cA-R?S~',\ډm=K{Uop5"~ \O$FWڧ݁DRvQ0aM׫`ep@&=>LoCf[sEy<NuQp \ʹڔTzZ4JߩhQV,ڪφ]A^ -JINsp`4 zvPE-ڡz=#) 6H*pG1U-a*BMM%D6їf#؏_<*/@[HkCZ1\7v6MZx[iV |v{K0ٕ4E@3W+ˁ/a/ȪKtܓ`ux 6^Wk!^aG1X& # Ldr`uڻqgȔ1lNበ՛ކ}[UJ-n) 2@>iܦ"ja3a{` ,le-(K_ߟ%w`,I(J0 +~2gnKo1o 0FA%|[}X|5SjM~dSOޛ͢7,}[י+.^T~5۰&M.tn>e DX37o^>7f:"3B vɤ`W:hƁlw괯2wWx"eV󆝳jca"%5Dol?L=aRjj[V/5Jnk$R /Cѣv@5ň x._A#qcUv+e/jˠno4ۊxy.1U,rptJB/햪g mבJ4ʧƮUrȹܜ.q ;U-#TUAfHiȬ`wW~C9< pd\@n;.(,#U}qxOr qr x vA]r "5rʛroqUzD+ /u{+ɍ,0t+S:Q Û VtD [T(DeNƀӰ9Qδ2q"0_–+r>e8{>l x;[?4xuGMap+}'[ &^?]^U ;=j]P?r{eJ9ؾ@VS_"-)h)y'WoB<= <[꨻|x w@eQį:"֛5Q^Loɭ`a)u .,n?0jk`se o٩"v,tP"#vշE؋Խ􋗁`KFד`^ sɿ*8iT[)Wu-UB_%Cfc?(>;D*l-y v܍FyeH8ŕh%[U7Iŭ-<,-2՝J[b^5"+-[;N李M("z<(6xqP3-#~]GP a/lZ;T4^}?#~wڨ8#w~%bG93-w|,:[Yz-#^;$]*gA E5~ ke6=LC-(-a"s8{(~^IWn 7Nq24Q;[*ɨk ;||y eKecO޶9஋蹟r;#RQ"q 8b!""wga˕,E7aKW.랹&į¾+K|/_.^JF˰#K}\7s~QȬU7d"v`'SU,{^=noxw]l],pu It6܆eUj @8ē4@qϣZ:_xxH06͂66򫧦cd&5)ni~ub;u|p6 v5>ݞ2Wf&|ͩT-E;,gLZӌOzZ4łh""+Jٱ+C\1?O&pGLRn]w)#gg}2%Tf3WϿEI!6*Oo08pM&fguXrre7ĩ~zᑿDl4e F#|icS\2}"kFz3T:pvtS-?"1CW?!Ȓ Ȝ.HE+"mwIt~bp(@<2_ښQ6,3gj$ud(Qbrm݋޺A4–"ٰ@ 6 < Vx`Oȣ;Vr^&씃a/@8[i!F"px vt~BsP%0JG+05)t޲晇4c2Cy$Ot(ʔhӰj41!M L 2%c3F>H[.wU&XP%a)8 L"5J4+R?"*S K"-@rEJ?H &a)03};VU]$ a/5H;yyAQ"!\$ `GЊ˓*5"ʳ 2\(ב9L&1CE.T#wdNL:S=3HM8[Uӄ" ÎrCL:M(TN"0<;N$AV'* 9*߳DI,a{d aäP%a$?eq zG)gT%T݀,7nYIt܀*Y3a݀47SZdM\&7FĻ],*P$aM|$L'"IfO5:_ kK_ ,D%HR Kt_$K,| $oېL ]A[ i ]6iQ"0 TĊi ]–ik@L_h$L0T( S 2!`A DIfc 2-oAzU(0h$LJ @P$a=P?J~hżbhR>? W>搘@?@iV_ t;,RTTiDTiiDTitI8⊂v)nC V6DiP%fV6DitPfqVGTOWvLY:PiNEQBb*uL4ד 0YLv֠IRQI1}֠I*oU}AA)'?THU9}DC7!M0fBD an"qڥGQD`&IR)? 1ZZ2JMJGKJTGKD$0G0*5F9/3 $LMA`'hK'6u}4[K߂0X<&oAK'5H18UA. t+PH~t+PF~✘?~Я_DOS5kxN "TLtkhPr53F.)AQ&#p'CQ'X tIe% r5X7P&at{}C<=jEOxҁ[_Gn/ϸ[柼[ȳE9JLtB<j,p&$Ӳږ-|xm&OF7}?pklt27݁nM*ża[7O7X~)6.]qY+OL/9j%vsRfWo\*\Ln-%=4+qGjwUNxW"u(/r'C>,mWrޝ7@emi9'΄Ӱy ' uUo`M>}2B|eԪ˷yA|ޤ/ _*=< [*Zz=Mٯ{SD)cqD1}-e*92#KaF=[rC3yMO7vOdpwS@@)8ȊT[ʝl{/pz}U$ݚ\L5%*pbu8{^)B֧wq1ceޮwuiKfշ$ Fz/J?oꦝ5!aW-ohk5m$x"{{1J!$x'6q$MQ[= Fy !$n'tο}Վa>Jo땼-ƱK/ů JxDxC<}jp3rvݣ,c$AP{TNr(?: 9ی%uBFv1R0Ax\A)k;Qqպnݖs6mT,QG6-ִtuG3nA ۻĈH v弶ipzCj ׼tuCn*!|)TV_5=wMQŕVE4ViNtBܦ7aLf=E$#A-ط⯴\S~M Dn^ܞU ^Y/p9GW.OSfW*tWWKk7R_*IxuxlQ5!f'WJ[J3梹kw#:hWܔݑWEӭ1;V,BifAkUoXsLqs>ɧ'ב0=/Qzz43jS&闪Bh!Y^jL%sxSv:xo]>8]>D9?'O`?nZ#ճp"m]atF?Db;#t ,4\TdbM^Ԋy,犵45&"ŞԲ5[FzcsF9/d ww3sni2 yodgeI:< ^Wk!^a+g~O\ 0+aG-m-z*ix*>L NÙ޽?<t;S"6۰o'$r"l,i4x"RRjްs]l|7GWOơZK'fJnWtMvaKŜY$q x.p]qƍfX;nu~6 t7 յ\~K(ހ}C/oКBr1 P:[z}fzMzVKrơ|DϠgFCc#7:!zfA52`̒ۋ4#3NqKV^/LLh_Ҧaٮ'sZ̄9e(^*gLZӌOzo 0'EV8:V?c,wM?"n]>OLjْQX[E3Hf;Vr}ׂ'e!c>"3MS.17KNNlL8+GxԊĨ*\4 ED+=r %|@-S̈́Rkt!RWkѭW?!Ȓ ȜHE+"m gU0C<2,m}&JrE8 {TXk{n(qUkevmjlITq+DVr?_g-؏rf|j1˅Y;&Cq b lqfl|gƥ[P%a0>#"P?e;NH}M 9jҜntS\24<ɣ(S"OG%9H0;L lg*˭ U&Xކ* SHI`m0͊cH9Tw ;,ъy\ `Ez$L"%c*|+[UZ.$Iw|yޅ$ [\ < q-x\ IFw~KytYC0۴0GY\ä|,|#0zY>Ve"&E1&!򞢸$m$kZ$56lhli5D˅ (0&~$L'(0&k;=uq|?$!ˇ,CH!Kw$oېL t>,.>.ׇ%Q"0 TĊitI8 [罹QB 2-trQ$L05DIj  2} Qd"XLڼ!Ho$LE%{P$a=P?CF1/1D%Z}>(ȕǪ9$&%a'W}v7 $H T%}U>a)GA@OXQ'Pn I8⊂BK]+ +)T4Y>*ЧPep,PB } U>MYOʧ*Ȏi>27ƥgP3fT C1XJAi'`|4|M K94Ix/I^D`8;ʩ}>& T&O 4>s 0_a7  ]:qEJFJmH_@l- L%Wj%TI`g%TIjg&} U%#:n3l2IW$a<&̿&_ty k3_קL3a.D%s`Iy_3tn$ ]&83 ].gQHY32Kwf~ed934},wZ6WX)@+L8U *1@ -wEg@y Q&8$d)N!`S!J4@0P\!P.( K4||RQ ߿2 D3Unj^-O /[u#YJև\ rGo}yv({:]iN=@E5pΤoPH<-[XZ~m)gϷxm&Oo=}\~We۔$7ukP) ˞οZ߸am|򻭍Nq܌Zyzez)U+ٷ+5tUzRڗWfrn.i˩ ĢXz> R lY+wlYO[n9<+&FtuʲgW5φl Dh^ ]ov*1!dU'`KRKV:vrdk;!C*wzvL#Gǔ;[ȑ~Hjse vdh;ﶤc{&OԔ91DN*USV 3)FPE99#/▷2#2F:mqfCEn`*PSq./|;z^ u7UNjݸ8%*pbu8{^)BV I1ce>휫Ӗ g;#ہg`09BL0<גּLI9DcB IuoI~C" r2p+O8ģHc[8> Oܲ w`J^例C.3A8fr3n]׌p-iuŴ$ ϫٽQY S}(G$4`v&n vڎifWjżF릡&jJ V$\.OVmM/[ԯ/Ul_)oe: N=ysCFDno¾-ط# DD4X 9E{͕[7M-gu}ӤYlZƇi!tIun:Q}Dx`uS/ZG+ؐR<ܷqG@uҡ)(zŏ[R5v,H{ ]3Z* + _nͦK4@]ݭORf|4:b;8YF[[9]wq=7cͭmq6`6w[dtq{J[eQߧRh 8?ߢВjюU-(}۱؜p=[j~_>\- ]!jnDa|A 0B6 s'"t ;gU[;Z"}3z6պ$_\]P7FB&̝uaPd%I LK˭VK8\GJcbv(4#oywP7J;vD#a\XlH/k\eؗW3xa8ӀMhuaR PJ'B`Ug m7J4."gTrȹÀ.+bm5z=bDcÔidV)xg"qb?d-S[rTpg𰜘eaKkņ椯$ǁGeY^; 8 {ZY'>,pT%Ö ~<[ry65d;7z|]iXO?)*Q񠱘(;VhGY @ڤVckyoKG ^+=/y~CzTF#Zž)ѷ)XNad*>a a/*ΈI,ՊEO+hhu5wHeYrMFt&8?\ 7HNA$K/if&$C ϱ~ǸCVߘ%L' rӯi sP**K- 1R}VYsV--o ֽo%F]6 Va;_k3Iͮot}{(/naVP Buo1ˊY ]G\gMaϤk(:NDR.;V壷cW3rn<.\o ~T7 F3>@uwE6%RQڊO"zdҋU*$/zRKJ2nwG ?}GL-J)ta:Av2Qzr[cm-(; F8 {TaQ᤻ &wP5P1Kڵjb9JHb٭j6&ݢj6#өGN),Jk6Q%@jXvֺ]Idj^aY`B&H 'Dԓb 1->?$w]ՏsS8e0ټ)x{Y-}xmTL *G~.ICQQi04ʴdƘʚFU ^^k^+"\8QqHu[R%kXڃ/{OeF5}Ō0cn,?ٮȸ)ϗ'&a)=l-%{8^[̏OPGwHV)0 J <iBnP@[ܴ9-[gI?{Wq-<mBn  t^d2Xx Q{ v-.sJ)DScެŏVpּdwp0MH@7ԭzqgl辁D௔T0p n&\LœD*- |M:ۣxT-cvm+5 ;W0bBnRLC\7JZX5>j1XK4߅侍C fU|E|J`>k}UӬ&J{d(QGH݋?*rhFlvv\WeYAxipgc\] ؝WF9/sq @8["q% 8 <T $nBp;"5)T!Yݑe##]:yeJ4id#IIA x\3}n~U&X* SHI`;0͊cH9T?A?D+ҟ ͟X)Ѐ V?AiV _Eڙ>}e*Z$a?SjS$ T'8e+"O$.z(.OԈ*.W ' Qf9,kB(LhUf,rgǸ(q0J#]ڑ.xDIxՙ" aKڪ$,!A#($C@a'vlaR̳DIy2R&5 P%a$?eq z= rFU(4nYIԀ, ^EՊD `$j@l-&ޕbPW" l P$aM<0&E/ k;X$X5Hr<_,X5Hr;_, 6)].A[ it\GڴKF0Pi+up\OM_*?dZ =\DM0 Qd"CL&DIfc 2-oh7 P$a=P$a=P"0L$LJ@i;M]QnD r\}n W6TsHL%a'W}v}_"HUYQ"TYd)GAPf%-BEnePa׊ -AdZ*Ki+UUh ,TYUhy$Q!J2DYf)7e2K/Cen#_F)8C, e&:+$l>+dŢ]X곂RaE g g'vaN2*Ynm+"*YEK'HPi$`k)f`g.ʦԲP%aP%aP"p`?TIf?뇺QwZ$aͼMA`ͼMZ,f)mmf)7D``3oCK'5H1JFYta]&8)@KyRA!qXtt'9)TYcP6kL$U֐AJNk&atW-wgo-Sn#&DI``t$L50J F7!J4_`/P.G(#(vh#.:*%@)2SG(0qw"DtJ ?$UGGH@ I?īmenMݚ.Tyò立7nXn|nkS.m\i37V^^rJJl,/]կ޸T啙ܴ[.KzyzSAfTJQpid٦ɳ#*[:dҬʧ-] n1w^[e~ųg [鏫Z+$GowW^x۸( e1k<:H̼0ߦĶ^X^&iPvgGOYqhOzQU0+ #W^:,t뇧|%WPw2|4=/Uք`_Rf.2x$h0)[e^{$< v8 /"gJ=<[*Zz=M{D)kx"ʚc^hE?g&“OFA[2sG2~.adAxe Q=ڧIDa-h沕%SV ZmCͤ$s:nj JCYfIFY'4l3#$t{`DVw7$HuyѻA;'`O(Z]߳DN.a+e[Ȓ^h1 ݯ4=Y׮ι:m ~\1;~x#$ݔM$aMIÔDOdoॐB}K^j8xхP[ nH6霚m=tw[78h&Q:e j7 £&nϧSzƣ@X/K#2ѭ5/VpR%Ƕe(wg`/^da;rC<}j=B'{0@jt08?d}kx?G:c~&g;Ά} ^2$ե9߳VοK0 \_LRYv5HnNތH3ݶ2styraB\x)V̜^sND>csAֈP%q.r9lŠO˧7;j¡1 RƼ8X戼ERwD؛v({^z}M7=p$/I.¾?}-oS!E{^ Q([JBd [nlTX例C=3 }R3^Ÿ^^3•-ob:_ٚDe[(˯JX}gg!l fAizVk2j #؏^AQVmM/[4/Ul7Iv;䝁/þ҈ M7W$ DD4 \seMcмnX7Mek'^2>L-l¨s{5"b~z5aW $m,PthC<2w_/ʴ`^5,wGMt%eL6i% |W j6ſ\0 5r"[Ucқ7 ,JMn 3W]OM:Ys+_M/絪tn{ m_lo oþ|y{; u4}!jɮռa,hG@ J7-ROơZIu5ouH%DWN`?l9&:J1! "G%w ҥ1 ӑ Tَ(!ݫL`V nYA}ett3ⱛKܡ!wð+g2M ˪X =;ɗ(ntVZz⹐2qyEճZ6[F%WʧƮ rș3K,Jag'P>bDcÔ/Y$HiLsOƧe-;R-{t"!7ֈ\^xpEe)cD3FզaeC^žUBp`bqx=e6GhL JtBDk;ƫ3(3m411~A7D ;8lHohEx zV"sQVf;TjzQbR&Rf,2[$8;qGuWmivN/RD8Ɠ^ lDf9GB0i75_X '<ػ -ܻX9/ae0n0hNF"C)% i{>/#Rks0k,?$ۼEړX=GWti^?ጢ #`%]n>n7.H=^0vx|`Σ,A! 'w]kدQ, 7*nno[7Qo)\s՚QdgD:r 8;OVinW"O`*Od~T*Wƀ㰣;b\NHt8chSV/ 51\zIx|v:E#<`~ l` L(+l=Vנf^}9Lނ-ϸ+9Q(}6;<슿:",A^ 3aȔ2ҋg8҄ko^XZ=1> BADQ g']1Qq$سU)Gf!$D]UJGp`rrݯU=%oO4u\:c懀ģ,40EEF~[YmJ$- ^yDƴa!WqsZ\ab/@P:KW&]Y[\qXVscSv]Qkеd@sJh,^?]^e$V0lӖ_u(ek$lq!$噐̦=eT H"߀* r-|MOy )?[МuR[N1CąD `O)ԭwA?3 v|}Nx}naNTwєc m,شKԕ#:jF;_8Unr t_ #Fac`ώ!{i 4}^iRJ/uhޑ?\F6ԑU-hnN"w&ea8BYdatOP5|Nh=a3C/ 㖃 `K @ P5kL"ǀaGwN4s#a?I'`ͦ&|~-* aƯmm|pʥK?mf+KNZɾ\y< ׾2vtI/O7/N rJ[sE/,*APd-*zw!33wǏ=[*,Z 5QUR Dz#y,Y=a6ɿoQT>ziM:ϩ odHNFDnU7XMq)]ނ}K9:@TNDc{A5%nY&lZƇi!t2<:w^½k[=_{Jr!ծJ֑pG1Un׋E_/~̑*5QuL~`ݏ$Q5DBEd%!w 6_@:k,";Y.[(Qp&=v=7iÖw1]Z1M0rY~kM-ܸiMx YӦCDT!v ;gՐ[TdRFؾ_=aRjU%-W<";v] HݸN`?lkpZ=$]i6\48%uMzqgMU>@C#׬E¤7QER/g59X&Ȇߪģ}KVX5$wGL9Y_U ش oJа%_$bG_Bp<(]1uAHqZճZ6;XJ4fƳV{n.mjcd)~e#ϻ 0%_+ҘX'+OUp;\(KKQ ݫHy"j:q.+B6]E$FU-pz`{)K[]noT6hz9 x吻Y{~C*Qs+D5Ws_ǫ3L#,X411~A47d/QeXn~ !ɢ 7%xi/l .uѨz*js)x ÖOWʑ(qlEifAT!_ȗxr'nqaȷf0 8=. [X7 "iѳ\.\z;6Nba'ZoLN[`AmRdtVІx́!0$*f.c܄cIt|vno=W)eͲ3^pt;RcM,ZF%j`.hF?P]EK/þ3BFW`uOLPt"NW5{]˨tXqkB8;+ktpVNZK[*! ˆ2L`$#'`PΑӓ|k9Ke4m–Lv ozDiOu3$s n3$y%?>D_ | u2*FYm  7}R0тsߗj}Җ' egDk:r[jKL#8[T$쓑ɁOJJx!$r txRinp:MSnwKL  ǃY]G:,ؿxT GL0 xw1ld]TCZs˂F4;a_.q7`K,g$rG6Z8nDọϮ b&R&1=wA{64ۯh^[\vQTt=1>-UC*d.Vy$\1?l(8ꯔqTp߯o8:|| &-zVKr!i6q`?lvVL:Hȝ)6 l:b7mvx %j,Eth;_!BY]VBYSg2`IJ ::*Wjeg̱D;92R|5 v>sP%aO?y$P=_(9<[6T2Hv&QTiCWi$< t *%lcwSieGw :IY$j@'a51%ð,!5 KQaQJ$n߯Ԋx-Z, JYҖh,$+dYHYȲDE{/-Ak%a50@&hZ(X&? /A}C [" ̯C0:I``SP}A&diD[x4Y-<8L7!KZx%$~C<=r7K_Gn/};WsˎgSdPRU'`KwKa%o-[ )ⵙ6nJ>GG:lt27uǘԭB7,{:~zk}ㆵW6>8ƥ6s3?k%Tdn<^bUKk_^Meb'NQ%=D?3¥hl&jpKK^niVӖ[.jț}jٳ筴K1\dmËaws6n4 1^´~ ۂzbyWC۝}A|8['f!(Vn*EcD\PF_OM:,mWrYXgi)#ʄSi Vm!.ˆځG`!ף!nXScdI?[=->-XuzUX[rC<劖=K5wIMzOZr%+'ݏ<"BNU9ڏ<"l/"̯K't{Y d;J(F&iޑvdakel}d<8u(3)3FPCuqiq-dFY'4l3$t{`DV7w}n"GQ;lqbwW5;'`O(w!araӗ U[)t=!tRH! ޞ`1鶑܏s'i=]g3F!6q~_p@,qF7L40z("U Ӱ_UثԿ}s;KHa;c0tyG*wJ{]o1+Z!`|L~g'6{ aE_=YsxrFW?g|%vނ}K~cjmJriwX9[x 1:} 8{ O(gb pPrp$v ] ޖˣ}yƛegaKusk0ph$5( !oR~RVtDIZBX>"*1~tځ>,x};0*;ntmN˔DR. 7^g)If~ QthK5#-UU\tl-~q8;`qh%wGգ3!h'V5n3u,Mj21dGxqky⛉<-Uao–O rm*A}0*zPeLݜ6mɧ;!i#'wKCQ!C%sUV8e7ݿW g#ѻ|[9%%{X%II_ODo߹[kJVx2VJ(,Mt(8tC57!s4Q)BR йk^O0޷D8>XU)>On; giF!pA٪ ^e1b  @\_F2_12Jf?IYh#:Yzڠ[40d]2w,o3)z nUSe'D/9=lȤZ~nhe(U- Ln 2 gd Hބpt&ۂAM + LUVXNl#Gbiv=Gm`H5Q5y%3-BKmطoC ;ʙtH a³ZD.1l>Vi?=6D=n(TP;D<&lJYCzl H?<[z_>;eh"wsE]7ab^F\n~"-C xLxؘ_=nq(g㰃T5H?]^mEcbf : <[n>9S'5)R I l).O"VA 7>W |MUoS|B|~\rvӭ_p}oepr_$ Y$%wcc'i2jIf;C#\iX\^8)집%n7TҤ oO4!T PsB0~8R0zn빶8<̢=#g]}sdÂf:ɴ[8@z 򫜮МG6rEs,lSk*\'{B.hT"-_SԱzktYwr4һR| cP41/p 39*supn-q58+ܷqRK|)`4Ksy,+zARS B 7fH=iRC{<\8fQl$ Kw0^kHvZX wW~Ey oÖhzn';t{ScN֖Dޅ}W-et,}͂t =:;[7rrfĨxNK9OI49DexT]\I&s/ZX_f孰y_3ýV<+b :R>0l@84-ws?JwF F:l=<궫V)89]cE}c|(@<;Z@j|I~mפVi:G]BnFױS5h[*L?zv/q >8\e uN>nfwx ]V^ E_>7n?+_);̳:-,EZAR'( 4bx=l[nlm$۝:mZ)C<ɫk5o9ˬ6 фRBͩ$}c} C8Tll?U5ΝYXVqmcI|mGx`GkNEeˑ%U: ͳTǁ侍C{YP Et=Wфe(j)F49ēt݇fLI?A4fhc[-oKn#xZDK$I>u)#~)y(k!-U#wD|gaGy`HJi֍Ϟ /D1R'D*kM)0ʕcI #_M͢uL{ ׏#M|I&X둻`tu"p;BXaW+e~ w6yL^OS*vY4n(v׍r0o!PrŊ-QAx_$ 5ZHδ%dKX_9a]ZN`76wJ{`ϸL,Qީo9ÖfcELB/[D5Cei*(/WE`|+G"3T?/[dܦNی%Tx2Ѻ[ c{ͮ e"TkТ9RR1qW:93-QYJ`%7aN!w8ģHgQÈVzWDb9Vgj{ FY|Sg"k –:VTLo;"\$} a+~ 1:=L5ؚr޴^[Ɯf`gy׋vY҄7Ǽd2COo:@FKWm[Uj @8ē4ʧny_:m;?g31c'pԒzaj CzbőۆV*b ExEOd|t1R6$M@ Mj\p'[Zff޿?ì>`;Ke𺏙74Ք%~ƹl}M|+r$p`rL(lT#'Խ̏)n0ATM(o'J7j4ȬSq Kط"0*;a4;,"*=Vn?vr5QXOY=˰/+}Tf%{:v~`r;Q$׭Z0̯)L8`)E9:JZjeܕݸt}| rqCP4oþB&w`QξnY,j 5QA@o[Q:DMCѪaU[nޟi Vj>s)->is^9V8ž_&߯tP^ujځ@Oi8qə&ij!ݘO{+8Dz xT}ǁax 7MUehh7/[3X],Yv IǮu+(ERBD`xvW+(pvSXT8?7LZ&Tg,aҟAR&0aҟAip5Lg§QC+ݲZCU(f$$C+d"&?,dV59Ih]. Az$LP$aM<&k(0&k;=u֖ $%: H/X,%: H/X, 6)7n2$]Mt(j b7%(lFɿT .ȴhh%o!JL$L5D -DIfc 2-obAz$LHT{D``Ai@0[}>5miKh_ϿDj /!J4O? ?A_ATW,(_ATW,(_A,((_g#HʿNV Uu kU_CBXFޛG@ 6Q Ka6Q Kaq6GTO1Pn\JJ=:ҩR"0 ԘdJ=IƷ0S&&)Qu!"[oQ6eˆHobc'&ҿ0eclPߢ-Sz3%TٔZ\J{$L7JN0(=.̬& 8ea'h3 Rn0f?AK'5H1d^A]&85w߱XS]KwjPF954}+={hY)=L<U=2P2Ccj:%gga\]R 3DI`x?C,(&%aQ? 5<L@%/Pa)G(PcG I]xT'rODoO'tu "m,KgS9godQt-6{j$IG! lai| ?;^蓾MƯ롿4C*ߦ4]Mw 9[ӅJ1oXt kӍ>mm|pʥK?mf+KNZɾ\y< ׾2vtI/Os&SA6TDlp =ꫯϳ#*U:]Ҭʧ-] %i#o:^[e~ųg [)Z!GowW^x۸( e0k9H̼0ߦ^X^&iPvgGO_3~"d%`R7<+;9-W]9,mWrJ-hY֖w憸r +܅_ i7 KZ'a?۱ 5vp@yCOp7TJ^ESou>d>TQr?!2,eM"4,nr*L~$s1bQWId\:#Ȃ(&Kf{UOTMjSSS's#33ƻ7$ aZ AA?m*U:^ؓC<2ny>R Nhg1ڿ=v4InHP;=YzWcwxNP.X',MR;eN*{c>Q yJ%#,&F,v4sN[t78u@_n}&3ó*xϔDOdor`'aOm$IFR @®m.I1F!6q6Ftv:I{;W6vsD#w#1pj2_~$K~/C0Tzd2&|,.IkjDN"H6~9+b}Eî떞s x{yo~p2_G]/`R&ߘZFVNǖkY2^*Tʄeq]4.l`b HG8(|b^&FYRv{ܢA.r8 {4֚~qxv㆐{{7PQWz?W)U+ecdd(Ԋ-CM/R_)qO˂ѷSnsFILi/IG+-ހ}#~q8 {6"! wL8aWCSᖂ~h xTU%Rs KjH 8š%NV4 .h'V5s(k44qǕQ*cbo& pT-:r [?n'-DUi(C-)2usn`%~/xя0ީ)f{>kIoU:1,9me8#.[2K_ODo߹[kVx`TJ+(N G4uҡA޴*C};7A-NEou|Zn`-v}@r#Bѭxo:=K T_*%e5u;4~)!U HBq&9.u$vd۹£2 pz2sjװ_G2B_ 4aXr7 |x#4G6U*c OhK/ihLs;aȂeԂVG)g CaCP3mJ4Nq0qKR}a$AtInϗ5Tu90hΖ Aʰ*G[8)G6ۑ)^*A<i g!oP;wHAsx$Ѐ\׺S* 2}@nɮ`mܺTvMrEcʺX4SkmZ=m;aOیezB_-2W:|Ul6T<){sM*yY3w%~%쿌i_-k5U5CW"l(׽/t k,YӜ)%Ogyb;Vo б[v/Wm9ē4 R hZ/(`RmjspG/`Lxk 3Nx|E_ǶDmlvq%h}J_OŽn`踖^d=eۡ}N-NuB .[Do $nCu۝:s!յ7er4PB{'!Jm ҡʯ]?= NHXHN #&Xba9PW~(A0ZQSثSDt#*9Oi {暨K-pa/>4ܝ>LU,E _73&/7 gM#h{􋇀 &~`tzDk Rr9[G J)L8Tݲ(?tSfZU)$N`?~:[#I:㦠S4\OGJcfܮ%&2 TW ?iTgtN:.u)e)-Q/phj t-Wসvt7iZ&Fv;δ%v dTȗpNȝЙl˱KJ'klY6q>`lT!Zժ oMșxa˝7Dp=lj3 D$|[K㗧#n`ZIQ'm+ 'CY lI'wǀ7Y}kzҝ(rC-ru02yir֘CDpJ:58Dw`ߑ%ǁaKśeo`QЬۃJ?jgC[3X],Yv;/LqH8ē4H FdBi`J5R @`Tϥ+Yd=@<[ƇiiZsxfiSf&4ۧZYz0;zY/WtV&qrf8Ke ni+SW3,|ͩTA&猉_kcIbA4#Odcխi{=#I"cZƍAXat{gavָjq|bR̖ ܚ͈_XT g`Ϥ;hIJaRUrre74{ifRA<鞃&a %)k.%j5Z 9&%T d`E(fB_b~O8;vUi!8Ya^T8rơ|w$:JFe?Q=ӳ(.Qأч8^䮑Di -E!nہl-dat%ďގ ~aȮj(Km/x 1_o!BsH|GEW*-TI8 {8(l ,L}M 9+Hp1n~i~iNE xT&&o M L 2%c3Q޷ C9AB VBVD$0[0͊cH9TA߱D+ X)Ѐ VAiV _Eڙ>}e*Z~I3kQ<$ #'8e+"!I!"$'JȮy WY< :D*t. UB!ȝ!&*DʚNpM\8[U'#WsDX㰥4SP$a?lZ[UD`xv'EŽt  I ږ&W&8L5mi `VDiOb搘@ 0>}X* ,(h,(K7 Z2 GY\QP(t?LTBנʵU%5r-eAk*7$*u0F~\g)7(!,F~\g6( ,F &ib7v.%D&i"uڥSGQD`11P&a@CK& `K$<[V'r7DI/'?T\Gt(U6o@,юTRne vD7 nG눺5QLxIk"4Ij J ֠EhҭA)`|5aN23%,J$D%iNER-"&IR)? D.^_ˎt 2tI|,g($e|,tg(#e| mVXG)T S݉g8ᭆ^+-<- VHW{nِg'sЕhvxXT'LQH<-[XZ~m)gf2ot7+}zo=# 7&$7ukP) ˞οZ߸am|򻭍Nq܌Zyzez)U+ٷ+5tUzRڗWfrn.`NyQ%&=?eGQVfU>me,]E7`]/lٳUO 2;+/^?l -_厼8[?=D'pjV߉ X]ÞWʶ+aA0t p Xdgsul bwr; 3&GHH}VY{$x"{{ ;?[#q$M )|Oa6q{Øu@Zoa;q/Vս{+e'g׻\]^`.XNi/SlM ߱w>JjjDNHaE_=FYq[z1,G](ז?lDӮ[o)oLMiT#+c+/Q*e²8lN_ʙ#z3l:vb8i;$<-߷nQxT];(zh _! TTUUJJ$Yj bqKPӋWʫt=ia[ܺQҵ9-SzKfk(_hKA7`߈_x}žM~Hor'8o(rxP_~T\ծ-ž9a[_Î.XZbl(Lc^Npb{-oY_37iXY1KLPnUFڋ)8/NSYR]?&l T 8W XX͹mݖ|\6i#'wjJt;^Z:[-p n([mΈGx+ʺ21E /þD-Gl5ہ>,c$82 Ҵ}a0 P~M~^~pՂL rǟ󵟢T:h%phdyoeLƜNgrtOjfyӴlqkJ/_*8kb NH:#mUgUPǼC<2^_yjL3gRyשz7#VpY G+د",D0kyR+Z4p Ru.^Vv[vkeGwGPb5(\MvgN[sH]yY&wڎzJ7oYTOơZ Z6ffZ-l3_FA[Rh r'f \ƥłW[=|Űݢt椦5ò*fښMe^bhcQ_i`˹P+K%:}6%2`K-4S85B)ܘߑuM:$/IxVpkb(}͖aMxynr=Y<B\K >m8$( `D5 /U,aU wߟ&w=ՇCn+SM5U^ث$r8;aK"{RQGK5C< \]d=悭U,: |u1 I ౹$ 83Bw5Pj,K.x'nYq؉%yWYV/rY/WTw-]_?tߩλo.d[c ~{ ba1j3Jo0#TIጲu^6,\PM1gIADؘ㹜IزEfzD J=£=G4X $]~Jj>)1Hgv`/PǾ:J1;r2>5B[-snM)!%ؗqCNWUD2yK9͢]oY`zL:=аr.d 06$|pʥ 斌 ሸJABsTZe])-&|P4rP53N/C< u鰈ܡ¶Qkvh+,?gu?=*R>=ź57K_1Ž;a 5ee.:J8{$9q&,StgZDZ9Eu(|%VW4J\3Uɻ"<[U Q*hR4c=(O({v{ KЍo!i""T'kFŲMVϛ9:gMrpO=Nu9xIG&^tC]ħ񞎒[ D$u@lv[4T^Bi2 HI`04'9#EN¾LA^-`%[)1#Ic+%k[9̶ ½.T1u47r'ꅫSQ{u &l;d8E SI4o?^+y-.g]!kDkTǑtu.!qB)j-EϟQrk]R n`l43Yev)^쁔{4l6 o$SPg7aLRbGߴ7rJg$ar=h8iJ)xq 9ac{NW&9)Rߺءn)cD+x.gQX$ $=ƶq8p@9M8T#Kb 쇝@dž-߱9IA@X*:gګ>#`ū,xxmiby%+?H]LnVy=Ub罉dOķ{a*@G`i|ZVh ZnzN`{x |Pҿ|”e@rKmKnl!Ey3ͲhZҳFfr f}b^aSOb& ?Ώ xٳKcFNe#X*D7 }*dž9{Nkr,@ H8ٹ!VE?:b ˌ8{.WeG`I!^Cqr.?阮@NVQkCK%c?w!͞JWΟH1 aJWҎPMm\1]PFg2ە5˛3 ^ovN#3)+~iw (˂ptg'K7PCM3? /.rireq6 82^&vT9ɳP;MFoh(wYl3f 3pl۫( p/h#xdX9A!.]C[\d$[BTD`p7lu~BB=S)w`ھDug,c&eZ4 Ȟf쑔)`=<L &av&R{`k#W$HP%aUH.`UH)^`CiL"Ԃ4--QGjA#% # M4)8Gڒ{b׋ڐ$aӆ$ c7&/O"[e+RG6$I [A+-OJPYUy Ke ӪQG%]4BV%(X(KZ>4،{UluoB[GoB$&I[AV' 4L?@0Ɂ*-a!Lp@i(^`֨aR[n]}5J!%\҅VZE'QtfMJD]HӅVvjO.djKM\.I`F4D'Iσ" l=(0&tl=(0&6o ylԍ[_,kːdYKy_,Z2$Y!K 7W)2:]k_FyM%=@A,FK>b}?9R (5NLn[^'Q&8ɴQ:D N2-@iN2Q=N2M/ҜA @A@@'0#(0( l\tS.ir!E-QQ.j)Eʢl t$L}R=ƹPø߂*} |KKy-(--YзʷtgA߂2 F͂B]߆*NVoCoзʷUP)+m*tDLwC 6(߭ȿ5Z!wk6FyF~l|@VMZJ|rY8w$UJLXLS{L4P`l񏯂& ;a ͛I>@ʵ:*hPݩG~}RRKsKL"0 ھX|/2Y8s$EJzR1>$dY "33pSYjh0A'$aNtt_ MD):ъ>E i:ARvD}Iȴ(8'9锧{\$~0CR^?*D]_Kwa#0-7s/ ,<-h 6?IFSP@R΄O6 M[:wd5%a_Q:9J N~ DI(lhU"]ү2VKtrk̯R%}@%69P&QO|&x=E5)᥿' nU`-]^;;jǸZy!MeOg/QIy iN܅$,54fokk"o7Z+ok#T&/{#%ǜ#3 9qGro,=<<|t7=G#fIXgO?729S6 'gO:~$;׋n, 9Dh _O)ʢ4]z{ᕡhѯhF骐sUoe7o^UK{1\dt֭hM_:~Wqؼb^ôf峞 ct s{jŬ2OC-klUao89,jWI}_Qtb'*)gw ,sv6+un9zbhIYK >*͜;)c1#@Ctj{J [ao!VWmEkڒ bOBt=PLzk~]Xռ(rrF, 7lnt6kV妻]סO><+ԪR[hKnN(1#XtMKiAx$%ڸˍ0DfavFnʮ>[K7Q^9LJ7Ү'n6 &k4`)խKf WV6yS'bW8{@bͪtSgx;x08:=.Ulu@,f#]*+Uk VD#◛`Suf7~EfX _scK>|HO46!")&np7kVnYa\N+YppC2<ݴȜ{Wӄ㰏7^+ 'IFr h)DI,p+DEj>^;R]4|E\C=sM&Fx D!Eo@wfZ} x-2ʂ- ZeЄgon-4ןk8Y#`i:L 7{̴|gz.;vq̈́Z5 <[hOhxK-6iWBYg%4]u5<%5c2tK,buMйfx9v"zU@Zl~l_>b]vT"qb32OwPxtv~o#J/~Am+kEy;ׯK#*osˎA-Lv~u"Vm͹˔Wa\xd "̀Cvdn_(ZeERǽl!r8h~AsDƁ~Mc{ԠEmȬՋv4մ<s> HsvczhA/,.+d8z/-mYKl"m˰_NEl^ހ-ԏ瀯~;|gA(Wk>TB5ZU}y DOV!~ uL2Hq {jDx ŻՈ[mӗ/=?18|3ucRS tC}v *c$ )2 36e 6g@tIlx %iϺRv`ħer!<79#ebY0=9> [hyی:ږz:!+,LYY賕yz^C(FtD4.I((jrڒaFfGh!£vm,A]\Y{+W7YciwG=K `ߝk^,㻏`Q~ͩzqG;7 T.l5g|6ۡ y&Cv/|fwf 'M[9b %_9ǧ %#k(s ,;gn`eT"sQS,v -wz.P[.MF슬dYJzAfї*_H$ -6|`ބ ?)忎Y(EVJ$9$[)Ƕ9s̕ % m2N:#@egmF#"n7m\ "1 fM#f*˘ $rDSٌq|S ks:]]=ax"dـNټ#{c'"<D#Ji f5((![0,z4#hjHVcnj%y^ 7U>N1o]tߣk`_K^ tj0|\ &ܥ~V $ 쩻i$u.f.1;|Pw<r` pЁ|xPr#oJZdqޅ}WT[b[$j#؏릱qگMئ2Ѿ\h'o~KZ1)ni~;`RgaPaN^gB]yUEa I;T$.`ntEqwt[R=laEg(i>ofiZQ _?tˣY=K<]Yg`d,>ߴVx2[>KgDewV{$W~⟞:>7˦c,?(}3  V%;a'U< [X_6`-=4U{\7t4݀[{Ρ9oZ܌9u+k2ܓEƒ򉆒kk`=}]x2"F-XneLڦʅS(e\BKc;ǰwݾjZ݊޼Lt;%MV1](㰅- C8/A%,;[ʼn ^P6P-@CYٽS  ٫w`w%/ ~v;ذ lƴaO,H1*; hѹrbulYpcLvP\91 N#zsD!pBr ѹr*p2>r`.^L) mig$Ӎxa.+1K<$w9Zds KdE]s:Wg1ģL3S' -⏉Vq}G dp7lV)MUh,gaZyLQzƗbP]x뒞qr ;` VWs\&ݱ nǀ`_Hc:g.{/peThxУItgAua YC+SzVhK@ %M9me/@/+a fH0Yӫ1lܬp|88{ W$***a/^%^~q+CBFab(#/4kxfW13]䐰U{ Uiޝ؟Eܒw^ kI/^e8vn$NwUBx[)JDl3wnU"/on3RtBp>8NJ~%jSd7zJ|yYНU.Ipl18mY_ %olTF!}X?."{>oҢ Ts(>} ~Ka٬hSߒBC͂N! ENQeŖ[ & NDe'4^ή[1=\vFV]B-6 !MON(\i" {~q+SwFi-ENY\Z6G _-O) \Zk6npǜ֢–py~o8o^fv-\HKgS&/G-zI ,41E4RYس(vcH<-&>l5{` o)8ЄmJ%F M+r.Ěa܎f{*l5Smy`X"E0UjcHo'RbGQ'5R>nKG(r4^@D(2jKEߕY;`wP m1C~« z`. 0-2 &#FGK蜏W`Err-O-WąBNa~H‚8C3(b3A0!rk K(7Q3|@^Z^Q_/(ZDd!n k6e9*"2||fl$:A YR6Ţ3+c ivh6 % [^KNan#Z$*ǀ'a\X`wPQ'~`J]pIҘA34GZ6 b҈>1#㹜XށbY,9v-vӳ &dDCAK,#?K $ݩ$VYB[bGVWu<3g;y[8b:|mhsX% 3n tQ"Lzȁg9)p4Hءn葾htO7Š0%/ 4߲قP`e+g8̲^2t2 h.ܧFtr0 DlֈNa g NxeNEQDa* ;E[ݰEf l/_-HPjB,? ="x['FȩFP_Gn1]lOwa[ մ78n_.+\Hl*P'=.;R] }og oKCm vŭ֯4i2 a"%}G>%T(kv 8`uH%:ugV7Rɣ亁#&?< hNEjieAkaUu FFf؛QJnp -҅2Rè ?y6A+ V{sJ@Lo'aO*l/^ dT}פUu`v!y/+ܤg}lr@7O49IϧLzؾoO>}K]s8 ;~%ǀ#u*m@-\4x&x_߈:aJ曐7KHJi{ N/>_Bɭn]`WߕIz~lA[KMvWQDx:OфD%Ȱ;.y /<.bccط@w`8l _\R#9E6{a6bPr}OW'EQWND"M:P0G%UA6o. Z WcBS- n w6(۴%%_fػ[?,70W5 [h☯NPrNN[n4(1g 9m.—Ns&~?4܀rvi~r'j%)TG`7(+Rտ#TS 26 M7tϯ% 6,̗  /$cP ;L龶\#-. WeM(LmGpMp3͍ ߅,?P1[\ݐ]bH?sNq2f9}޴w##,Vفha#a·/rPiXԬ 56LO>OO opxULLNam\+J}H&\V~ "DWłakFq؏1<|r7cSi[{7f `gTaª(-7i? (j2OV`iVJ4 BlVcʔFdB&ہW`ϯYby ƂC8npɐ88ApP\1m!HдYANbd4'9'<"=aa\.8rǕ9 B r-g(Pkx^xL-k[ys٥h }c8[8]#7 a hAEmMhzH^}1^߅Dj/oa½7'|a 6ʖ?6„Jˍ{f/'bfȴ۵f(fe `FRvF-7[Do2^aGJIPf2|",i&f)f:7]wWk;pPB}S->-%C>@O?׎0,O?׎P|d#E!"΍vRO[?0rȁs~ҩ| -<!Em꼙gft[~?-Y?39u ixEL& G+g o`X@0/{v1-Fp3D7%^}ߧrlx-ϝ$~o,W͂$#YbXnrE?:b ˌ,fΜեeG`I!~iGw\g F~f~ ,נG>ic<(%A!ߩ7^fص7AU],@ x~Mkr 㟶/ V&BgAE[*rl/AD g)$^p9WZN uGug\9%<4m++ 76h~ ]PB1|ȅ ?_E~B+QKng\Ut78ԿU._DM;R~@diG1i#l6 ðS\| uJv S)aPNa!{G#yEvɮ__yrWAWfk CugEm T3{>>ݰ(2plCʡw, o*-$%C<[Z2BLʫn2nQ+~y;p PǬNYڀaV @^^-ih5n\ tOF-c_2>=b`;pGMHUPT8s]4qzI.%^ b}WmKe [oL=-h(w+m2جUP{`J( p/h#x7J'ŏA ]/A ݰ>KKB" G]~ $ݓB)^`lqVOK:8шy>ت ][Gi>Y8{$eJpl!'߇4 33)Ȕ [leбIP%aP%a&H?UH)^`CiL"'D' Oh);R" :O@i:RJ/q%7sEHvG$T,Yy.*[:HV[.T#<7ŗ8~$ U u'OB.Eu!+OB!DtkF|$DIc0J{a 5 t觠H)(זU'vQ秠H. j':)nT|aG"äOC&}0(I* &Q>Qäuû(kg @+Zg @͚  heV$3Mig MB5%:amNz" l? EN`MgH4xJظ&%Pgi i?I~NKy9sZA$l~sU"s]!!>!tțfἑ(J b4%alF)}~I ws#0I?( Sd"'$Ls6ti}A/q$LP$a=P" LP$a=PJظ>ow4 9nQO矠TD'%a6}=C$*PDgA?U~^KyPDgA?U~^KwP&a֨YP(4<]ȫ/@_HV_*BU~!Y~B T*|+/B 6_(5Z!/j6_DF~knnayf4N e)(jjRO?E4 玤J@i)|*S(0 ~ظ s34$IN*/M-a>@ʵ:O$wzW疘>E 30l ?C4 gH@/P3'?0 lH)= L#FKFў:JGK$LuDv-g0 F+DC%Fs-e7(?-%>9Iȴ(87Y.ɗK]~IKyiK$_]t%-ݥ/|Ik=Mq_@%O/Ϳ$)/P@R΄Om-6)~:@@ N0Q" Lpz@iNR=NV*%2e-/C_R%}@%6=e(P(w'J>CQt1IC` 1>mwp;l\kvrc|#a'lGIvi'i,hS? %:RKn`cQ9{ KVzyIiO(j%'?ǒDȴƒ$Ls 6nIvh_$acNT3'Iy0|bokok)`o$-6:(π[}k:{zz}ᛞU|x̣ȤW,3租)G'O?HQFb]JDH\r|OQ^:*b,2~Wc,g33=`N|͛WoR^.F*ʐ֣oV ?|+˸?l^Q-Z~oZYÔyo1?LM ݹ=5b֋$Wm[ի_}qX5ٯYybC=C:tK/? TP;c )끝2fO? Iw p'l\*J+x5Wg:{ GgafCeCĺD&֡ o¾H=+ԪoP`JH)1#XMK(Hfn-dט7>Po?rVvi"`n1Uth+@#=& DB'-( v D.<H2nmLl8nS71:bx ɥOLBoEv4ޡb(7镥CCC&j.Zy'3elƖ$f3Vn;:2R0Fvo93l;#_g wf Ju_>z6պ+4< ~,.KevG^r5FՃT w)2ߓ4aB>|f{%bPj)L\ϱ: ?'`„Up3%OJO4b'mki$]_mnS41`m*{2#Rr={KmL&t+E+;WZX HsvczhA/,.+d8%< [lkj^b@B~Mss-crQ%]B{ J0;/vJ8{N{.w66S4+P'bqev>a؇@bho-<7a6PrC KElnO Ga &*MU)/~!nHl2ɞއ}?Ei6gÆ }D%"Ei[u yڿJ +EJĔ>$)tmuD (9:fzo7eLo,]#1D)xzY:E%xdgAL7Z<+׏L'T3 [SWo\<]ϣ[!2>2o#V*YH`4`f)h=s`=KZe%Y\*َ:nr!79#ebY0=Mj5``ی:ږt:,!Kڴ6feV&ygQأ[]Y j#tRJ[5{JG`i9 -67+ko 'b"x 8 [h=fZQ,6RM1FпU{/ Asj БF-chMq2)3"LI[#HzD)AЍµ вl%7$4^G@&;+p~océ63wpNO)P"o*A{a ggZR׈oqr>ǗV,ݟD6^2]ۭ kJ=Qm _rNއ-4?'=K ^]^>(6 HJLlKTgf-췤6ݰ-ͣoLШ g+DrED(pxr^eq-Ԯ.%ؗ_(m˰/P(+Jص0gf碝'3t67_x :ϗz5;ڶ[^TvWuN7ytԃiY6#cO,#BxZ߹KmM"|ɸ5p|Qo¾ġ_-ԛshw]_5i G\A!{Tk9kggr3搞׭ԫBuטa [W4\ _C,L;C,pˈ C_v.NP.V1HƀX=7bkǫ5Gn5"3>ZU:&yq- VV9BՊPrcǤDxqhΰ%Ą^vx+;<4` m@ ]Tpm3wh-=gK]xa1x}uCħƋkvR7H'p= < [ =M8UIoPCa^}/̷ja jRQM1ē4 98û,g f"X{:q c%Qt g=Lx8qtXgeAp X%C&7x@.”j`9av,6'EڸdwH]']1ēt͡"LI&68|f c,N3fNQ/npN߅h.ܧ=G92TN'j( h"]˞A R=*hd}9#u ;E[ݰEf ,@"R%Wc)aiǣ-8,?-ҧzTxiNl,ڪb"wZ F/Fi'yo3ܯ?%?3c^2]%P'=.R]o w}7GՉj,ʉ(2B;PNA6o. Z G<%Aܠn p׍AӪAGBpox?Xn-~qkDe1_ZOgEC(rPl}#0;g۾]?6(/9^Q`?'MrQ#NZ\_\2ƉZAFm ( 0sW@P~/r'țBky˅h_}wK/Ib-r˳Kbdm|+|-hm"Sۑ:-\S' {s}! TLVp7$Dd+pl[O\}E~Ēh@Dyv\#H_"{ }6r&|K7"՝& E @poa/lhcDk?\$l|Np)8l 8t%W )„+Q>RdM7@cxrc߬4-ɽYǛQ&o#LXߊV}0[!EMiV" l;J5՝f=B⑍]jL֢XWDw; l#St;O;€pgU .G^U&^˵Sݖo;a M+ۑ;a.NO}[~r#R]#9@~Γȴt߁Ayq覱b<[]DGy_CF /aRQ7bGۯJ[0hJ)xɂokgYx@m.98]1T?#~I D`.5Ibrx % [[ &<ԤQZ>$o^}O a[/[tߋ0>)-=5i",?p$Kߏ~terz!.v em+o2 D} aJ?m_1?8yM&a;lMcV5Vv(mbOMC/&ԋ^Hoib)&܋9ᓽ,1_([n? l 7?!=C"2v--Jnf`|Y`A7<شQTQGaM}ʫ%tsim%U|E@5*4p=U{WXMuњ/?S!.]ƿa |Ds" G]kvO {}X=/Qh0 g ͟VMm:2Hg=#)S"{` y4> IIA^>bH/;YN$LБ0UGJvt$LӑR:ҘBEB?%HY-eGJ0AG&a l#m\=}zE-$I$TYy.*[:$a7l<)]@FdUyn/+q29P8` >DsE.dsPϡt5e#>Dsaa j>WIEwP$al!-N" [eEvVP;Iw*; >2]&ow4 9n Qe򗵔/T~Y%a6}=Cay!CZ*?< !(CZ*?; !(Ok,(.U臡'CN[*?B? U~8e~pCF>XGG J@Rn?-F#Gt|Dkd#57sl{Dΰ<3o'_2[5k)uT+P wsGRD4> IJ?lhYUhP"d>}*4IE$]n*zWIBuIJ--1}k`تAiI^TgOa2,R{ؙF&=/tסJGKU:Z" ~$LsD*;5HL$L h0ftl -f l\3Y.GˏjGQ8R#Z>~$-4J3`VfYoJ M-P m&JAV"7M½ņr:ޯ\a"9DIoAΌn`3Q93J:3ZȠm(󷵔gF@i͌6Inf;%!ir B<4Xd*Dd'bVO z{ZXu 5WԩƔ\3P ՘lr3\j{aJ(T%sRTIǠJT.`ss* Ӝ{}ZbC` 1>m>H4Iv;` 1>m>H [i!nmR;]awKVs28Dq-ѱ!ʏk)%@70!J4ǒ~cɪ@/ϕ#I<6O@K~XXP&al( ql$Iء%v& IT@fOIy&|b~'Oj)`o. `N4J3`Vr3e.d ީOA ed)-,Bh\OAҍ)TOi"$al> MɆtdih0V+1T{]2k׮?Kf;>֪ eG+;89~V "-)mQ̱:)2,BBꬳIs(!ZD󊻔>(%! X\4!^[}ъ_iF[薯)5x)9#3 9qGro,=<<|t7=G#fIXgO?729S6 'gO:~$;{n,Lu8*1i#&\) SK jp?NUc3̱-u(̲=fL>.6_}[kD;쀑2ۺMkCg2Wͫʛl cdL.bSBwnOM"]UeybVbo8U,׮I[~E!F 5Bil\sb#+ _MMx 1i9H!2_:yp@ru:^I AXcBRECwϓQ4V;` QT~Lݭ`ФʆC< 3=ܗ7f\Cga_! ;8h y+,P *:" 7/PJf hҩ;?4 B 8`)KfWV6S'bH}3pt ]x);V0$8:=.Ulu&QzwTo e½*+weAQk,^})̎:sB p?"^3,bGۛ~]DoFJ?x 9xOa6q+xp3 rZetGzӚqSwojxЬZO$/&“1ē46@SXL,X| (1jݙ Pk57൷HX* D(7kU Ǔlb^:P[wOXcftNbnO7`4G-6u%3-癞]d,lLKaY7a)اnC}Z蚆y%D}V^Bs/j*1Xӛvf2 xr&w!yEɯiӍwQ'-~?/~Iɉ@en`V8wMo?t|e:| + Y:Lb1WX'bk'Ŏl3NeG`IƉ_'QvF ؈YcgJ8l!'P3էrߪUi( κdP7-xd5q2b[#a"ڨU".e[m)uݰwK L.1*,LFdcsl.'F{åFWZĸxiXu+I1<;<ȫ 51~ݹ2>}WrDfxʹ:'`wӚ$lQu2rU2^})29 2ԔUWƉ[SW'ĭ;4!*+yÙ`; vere6=~FZu`KS`J-`>n*# +; k736m#cZE4o%M7t _ӈ~eBWe=P8avFS [h)?wFGa_T2_7^^}>X&~]`e5)dYzΑ U^T5"7[L> Fx"_(!K'3F$^ xsMpmI6eYhN匼NBmUOZ\#==#M{Svt'\'/*$oƊ.w1#KU/Ix&M H$A_9ԍ9FbwyxY;tRcI&`'D qV3MxV@ڄa˯(o_%i~Mלb\m &b'a 5gI|Қa GX]SO5Qrۀ "I 9o 3Cy3kraD pq%cP_hiPŎi5ɋmVo],+-X';k385پMb;aABdo¾W/|`?or*5دI0e N:sLTP7g-`gr3搞-|Wn[=/-,'JEn#F (}lA/<<;-#b4<p LPhS "iu˩NSP.Y%ɱ{.9S1l.흂f>L$G;w&i/om6-?uhVr48hv'y:<*k1cPׯ [J;0u<]P;]ڊ;ydhkhlR k0NgGe"bF$叱{ܧd0f7PR{Jrʒ*G3g!BuAv; A6cZxy1Apjp򔻙'V'i1+8z.TQANt_)!y/d rJ-P7ѫ}=L/`/$#;GQ`%l03iѼ$Αjp(,J=k̅ GVMhјMlٺ]]$5ѩshl!eҮs{K*lnkӾ XF`?rFɰrb+6q# Rrsa1cuIǸ?u.ލ>VKO'`'?VKO{NcLu-1ISK2 Zez+ŦH7֓`%#IBuhMQrcYuu:a%Hq![}Q KKAe_H]ʼn+6/A#m=#t?jЩg y9^Zq:f7El7Wn6v;A0!G 2|ֶig4mO@u<6hV򸊯[?#Gx9 B|^ <[lKŒ c/*kv89 +!ؗ<1$`}xp|8{.юMئhPo$!Vz.ĚaDEAOa0vGQ<0qgpzPW)'bGQ/\\q^jp/pѸP<7V;$zM7 T+q9);kvB;! YV)xIO(1: hL7Khn t8Ts?y cKf;ZzNpz)J5[c2vU3gl4c7vǣIj5^gRoh|>$]\p[#w/h-?0>HR? OF ڴw 9Ʀ|eg%(VE\ K(:n`{a4CIdg%jF(kH "3 B%wxEBȢ UZ-ӌdnCͰ)eCe?*XOCSX(NmXXpDv P֊l&*ǀ'a\X` HnѢO+-gSEwӥ1'eip#t3oaJ#i@op [vc3p -BmG4X $]~/"LI}4)jX.`8)'@z `I&{[a35 imJnxY23˫+qxMi:~Y,9vX=s,"ӳ܃ %BuqΔ@q_4ܒ5f6:Ke$U։~JBu۟0\x ;' ,a7Qr@ĵ&GQݫntwލ"E[8h_` ͞.q;\J0l4^ 1ƫP">w4^\3Ь*AD:{`[DxP/ pX;)ߠð_oʁW +8db'i#"Tbx+Lot`w^$#Jr&  cQ%Qx,g=L "2!8N+ :hKgtMCjtk`.”j`9a6,6'EߍAMvsOlTOGaEgRolAw,ӚaVrEuz6̄S.|$ \O[re F3*+( &ҳy_q /H(pBvVl )" -J|/7a o@"R%c)aiǣ8,?-I /4Buܒpæmܹ[1>}$' gLG7aP1E,K#ǥ_|l[AG,t{\p|,.'w}K5fs8 ;^.%ǀ#{*m@-=PNYagb'T)yx7~R"} uB}oq_B|6pK(uKj2e3]ls1 ədgxEwþ.MMdJQ 32;70aQRs9!b_}J;py/},} Ams?_]˒"^-sz8TMl"TAXy5jgX7WC_ULMR` oxXn-~!lvh ]'(V`'lY-7c[ /ٶl KWTDx'9Ba|\n@Hg1NJ 2jS8F-oyMAUa,J\}*AFQ㿐|0Z0r!ZWxNx %bcZLVP]nyvp=wI䄬/}mBlj;_KaonoZdVjl-2鞫t;Y}(>oڎ}W{`Q@뵰0*9@PCWpb-jV pB,|C {a EU&Z'`h|է'a EyXeg8 *&&Ŷq\FTT߄MJ+Y?h]q̰5rKQ8J}> rJsoߒܫuΨ6Y3aªշ(-7q߲ (j2V`ءZJP Cm^RiK ) xLt_1:k/0 KuV58!q0pP?\ ɚ'⽖k7-)vVS!+w)]$G:>$H#Gsߎ Ly~2|"'i&<5Pd\McebxxB3w)اKMf^}I6֪!n w5黕֪7ÛWA!"LJnsMZO<!gOi.c ^ +]C{YʛvFQÅqbOW0N^ߏ$l-4i̪N % 8[l65"uxńzM-^,%Ä{ oNd/ he0QV?ܸg~p>3[Dخ%6E5l/ ,fЖ63 v(ltg}—8&r^ބ}S_d %/%e.91o~SnfËU rsBYq$k[\øGGCdѢQLݙYFx#8}ϥi}`ygVVw\zAv|?8Ϸ#TonIDl1tĭlmFbn0r1{WXAvԯ1㤽g?wq+'C%O8al.̳{٦8;o']Gn߲ x>l" DC\ "n&v,73;>x1Ag- \$N1]n?`Kso|n/`AWi)g٠(tV+7I9#u__69瞘_a ʿBu ʱoP. ~? ?d\4Ry1NCEh~kx2<5Y7WǤM;scn/vѢ`J8{q?F|Q^(i_@|.Ư=9zj=-0`E |l O~`w= ^@P>_>zDP- Di?bhd~Yhkπ|뇴pvɮ:!d:gJw (˂pj$wV*ZJ)x%,ha(HJ5 MWP8[*q]ZޢD'` RMc1a◷ON@%<z4b!{WS`.S\dDq[Iؓ4{ ֓9 !wl1J? %j in\\lְ)H$ `)ۖt޾zD] _VQXW$ dYү(#_EQ^{T2^*M0al80~b -4YZBy]ݰ <*7J=)(w`ھDEG!͏c6Pv~(Y8{$eJpl!'ӏBؙdJc`I7JoB:R" #M0MGJHc qi#-H󷴔)`oAi:RJ/q%7sEmHvGې$T>Yy.*[:mHV[.T#<78D;(VMp3 @YT(wP:ݚ@c0J{a 5 tCnjxАB;`h:$-eI:;auP$al[~7Pr0#\aA%:L=I!Lp{P%a$Jا5j*]}5JScǠVQIcǠfMV ~ [T+|d1b&ڴIc&!6'߇" l$L'߇" l)n`eCǵD$?;8dIظ)`gk(3t'B? U~ZKtP姵gA? e~ZKtP姵tgA? eiB Td3i+3PgUgϤ@iBH,DI`#YZʍgQC>%n#YTjlfmϘgM9(sت]KAC4 玤J@i)|*IJ?l$섭z:Chp'l!IݰUB Z]U[b#US#?0,9"%@H$dY "33-ME{^C $LuDv-1TIhJUwjE< 4I`3'$a<& 4'Z<fOfDCRn@/0f&!k)=5r37_6%K 4X : ŧ/@{atJ-,靦Fwp2"DI!JTF@70/BiNR=NV*)ZS e(2-?2 Mrw31ē4$a],Rĸ@HSrrjikN^vMuj2% Tw@M&ہ;`W&gȀvG Y9)9TIܟC]$Ls~i>%(0 _" ;7N`jEvV0^V' l܆ڭ+nP&a2 S> IbP^3U0 ]#Ν%[#XKΎi99~Y lTL%jё:)2BCJR8yW^B9(}I%?x2`ŷ&s5ҌxmMp$VF+~6G|HD=UI?^6os^yۅ#7Fu>:{zz}ᛞU|x̣ȤW,3租)G'O?؈_9F]5E _O)ʤezϮS$fc?ZڱQe{ș}0םh|ͫj/֌hU#)nEc}oЙç{U5[-,ȘtНS/fHzjYXGJyl\'\Q 7iW*b^~v`3gg[;0-69R@ꄧ`ϝ!RK5>.mŊeb.S(*J~W <9Cnv=P>LzkeV-'wpٝWafxx{P&T>j՟u(u:IrtN@<"ddjcdd0m{Ek;Mgk&jkKxIf}X\6S tM1#.cYKd,-g|Zm۔9%S<va+RשV8{@bdvpx~.s XhWpT}`WYzZXV`" {31,/-5z x:$z&6R1ē4Mȁ{ kqjEmq ZM穩7m*K䁽Ca{>Nt[U"M„{mfFHq/l&uGק}>=Z 13%TnmȁӟGĜĨ {W_NhTwff>ߏ-٬hxsv x z3(+?C<޾AjEZRYU BF|O64] na UJtn/a?] pW0a1-H%0Vđ h[N|3pP~ɉRRJr Ȫ)j9섂v6DMĭP*(d'TA[~;AR4Ir=.(IA&ԃj05=ΠaL`R633ʈ:x >LRraBJ8[~*QۻngMbjSr` u9J&wCaO9&6/&S6'1 x|X?Mهs鱢f V]emkްLlWLMpXQ@<Ga6e؅D gTqDqxi:'}9Ә7¹cN7in8ƛe1rE֣N>IGfaNA7-=:]ht&V ðE5<(V w9ϥ)7`PO? krS*gZE7B7+X!\Co+SUZc:[dus{~AB[Z= a?l-qۢ@~ -vʩzw5l!bm !DYK_%/mv[$JGߌ!I4 W] @SWhFhFy=Jnpl3^-ѸBcRS MZ=tPvh#}-\ * )jJI"H9G@JiL[pۡG7irMiw4n1ͮs@8[ht8YEeBC#_[ {tlR-Z*Qb^T)ZNz ɦ,|S śP)yGX%*Y haM(ߒaJ-V)(>Ʃp&Fm[ mj91%<Tՠ "xh62mL =-J~/߀FtJ4!Ғo^y "4~_be+YMQQg5ē 4F_G%$[hڂi,t vw'q=H}[%zk\[ Ht0k[7ZY~.s$g -HY*u=n21g+96As7 MX2և0/3 FOV#iqgY09[~YgrrPA\*َtneFfwW${WR86 wns ~#w2TU)o:a}Zߴn Qz2엓)_%wSq)Hk|? # uغ4KC&.O#Yi{t^VOb/^}k^}MeV;5DѤR"HT˟-_ibe,+nx`t-JW}9(%*vp]ZBw(vc}M Dkתz(f &[g5{ J? [ $Τ SJ/p}p "T* t:TI#% :R$LӑR:ҘBE 9%Hg -eGJ0AG:iH)9ҖӧK^4 Ivh><$a'4Iv`lE3 IvVЊp˓jDV&_E3QP8`0j> ʜ&y@sPHӭ%r)Ni*/(-|* luICܪhuP$alJuNTx>uP$al[~7Pr0#\aRkPe^KyG&8LCiz}ZImwQ( D],gVQIt$,9  Dg!YM6|Dg!MB5%:amNzsP$aMIjO: 6sP$aM< l\np9%:7!ISKyoBބ$M- Y6n*O977*ǰu4tY8o$5JzRX>]ig@)wdp' =w*:ч%aL!JT'@70I%aL~L z 0]" HT{D`EzLV(ZQgR-!>!J4'll z;#fgzZ-vuM%Cgҩ;W#-{WxYd4u3Ȇco@{o .X$Z,j]2X[KLuS0?u"~Eꛁ+N\4HwV.Y8:=.Ulu/-P>ruXV`" {쨳׺Iu1ģM(֩$ۧۤc(۔9xOmrF=ӝ.9l`gաA7WD8[USV!؇%8xю1J~ q @xPIw뛮KwUZtO9;p< h cK?C<޾kzviKevԁnOҡp/c(>Rm[9'Rg[wO=CDQ}HF5A `krp6Ƈ΅ %o9]˰/+˥T臲3ZՉ\ҡE̕yo|tqBUMsĨGpn6{aJ {!2r~i.˗ sxuDafyV/-eP 3v=b~S; 49e;50Pqڔ =NjK,Sj8V-z $@_nh|3vG 0"ܶhA떧c3Vala@ց`E#m؜>o`Cvf\-źu2gxq>Sr`.uLCNyΪEs [% < [l0ic>+̓{>j9muEGx6=n1cHXCY<Okg Qj!z|'37J6_4Q]>^-GG&571v}c?H8[haI2je +2w.r2z"Xޅ}WI@lX-oo@ 5:B35S]/O7 7E;n)mĠb(_!p!)S҄:l68`Z(4M[+jgʆlxPr=H  >w8"M77zF=rt%ѓk.1_lf`g/g" P2Չ|e6stӍWT2⸞? di@zwHxؾFm2[4kv17.IԽ17Z%R\A.dG_ؒZI$cY ]1\?k$Slyda;vZm>ħ V(m lc>٨WKю%7^೰{{r,ݪb˹ռAt1dP`##7~_/0yL/Ő~]/:D26;fp88F3 +ՊeV̖a͛mQ'[lAn20ySHlr@7O4b9 ecÃmy\t'ӊYq$sCE?:b ˌ,f>,#<H 7#TNoh~feuwί89Ӈڪ_/e:G gsKu~u=%u;"DyP&-2$H;B5 8Qo.ѕ6%PǤme:W{*l(7 Kx 1i5VdBuXʩ{.`@ .f-cosS ?`9/'o?r]"zf+$p(\J'WiV%0 )_}/3ט\Z%_*WYdjn*H~Z'lQB]/ մ&ght6vc}/[vh;ulߦeBuƪܹ,KH;B5, vNf )/OJ}:"Fe_+⒯ӕ4܊n/}~`wI۽_Է݀JXĔ*ҎP22ZY4Z T{"z awaʽUk;WVO΀aUhMf]MuW[ќ*.};2 d 0LyPWA&RY 1'Lu,b"q4"o m]Vi]0^+]\[x6uO DvOEfBQa{n C]XZ*ixi.2P]R~唠w*NDS#kx7{љo!Xn%iFsښȫ7⠿ֆ?+Gէ5x)9#3 9qGro,=<<|t7=GYsd%{s#3e;zB?qhG#W.Mu(Qi#*\) SM{)jp?Nhm#rGulbRL@o+cҏS֭ a,y\9Ӛzbd{ieJl^^$?,Ols|ͳRibWԭfnMjW{*JmٝAs.sv68.3-69rm]k&H;)1\v:{TY)Pq3][nXz>X|ZlI %=xr!o PLr.*J~G (*b0"e7-x~VNPF`RX^n_2"N(,&(ݨ&-GK׺VZ:Q:e㚤>, .pJg, Tp5JVvzV&֕L5ġئF]GK]Nvk\.YuJuVN`5K5p\[q@*>kiv W[qt!רoD V\Gz/7i+QΎ:'bkZxX _sUoKkLmchlBD(SXMY+*Dɵk1Xpݼ%O Pm5ݲ9̼i89c+ ?(|*W _ )b'iȁ3.XF޿[zPzJz% {2R "!݇n2LZvdMj(̘5+Ą,ig0TrxywN]k"i Y:%h3WƣR>clCjHLso: kQ#w|ǽsExiwշh%?Uv9_3(̖:}BJn,EaFAFw #biɷx [K]o](yhقnyY™ lnu2W쾋xR'lڜW#8{$6q /o}~[< [h"pY/k.ǀ'aT.KJ_%o~#n[_%4l/>0 `%7^k{N;fҠ E6is9Vk"UN\\v},v"F]v{T26q.VX fzmI̾ bpxPډX鋵e`Сvb9WaW& @ mض;v"XP3nm"U~쯓_4d :UjF]0Q vAxDKlAEj 1A-Nʝ4`MuzrʍQ ~xeIFYYivADGMB~{JhnizvȐ '(,""s=N|M#⑼@pPЈ$D2ˍ;%wxl5x 5iSv.3 ËLLmr̛=Yr<.k CV{; ak]!H5]t208K|󣿚VΜ7seP٢G@ x)G+G5>RM1#_׌uυc7x$RCb@mP6LjFW $]pǡS $}B)މ|PÕ`.][E [h+-c!ts(N7Ha_gӓ[!*6mҜЊz7]k 21su4)ݝݸZդ:gtj:gWd"[3 B0 Bt‘@ʲ/QP]* ]5Vbr3 rص3z΁9ma:ن3N"cHP}CZɺQijPȍn(6f8~.(0F6a+mpK"8|P:D$l<|[eUd=|Ҳ>a ,ȧ c{7-Alk;n8·rgB$iNI No9=3Ó@' `IX(c/ D^GN|-Olq/@ 1M0RqE-eFE(b(], lݮXgLlKLpl1[`ppPQ``K`2㰅v.#q8< [lWӏyFd;(R4l(Q ;䟋!Im՞PlUβKF(^17K`D(7殥[ m 2ޝp )(FBF;4- {AM P]\T0*8\ժn EuiNPlK?XR4[zܮaleNh{,&ilMCsLk{f0l ' dn^}>^}Q:؂Y(t} vi*F˶%,V,pC脐G-!Yy+ Gl,ڢG-ہ:U*!ORr!T!w3 SF7=3ݶA1[nA %&y G 0la`k|2`˻QƊSi7-8>,[V̅Tl|S $MDD N~.ve#p3lA_"](}ձc4EW9Dn+p4SAL;θFe8EV)اiM.qNh8@%wl )7`ߐ1Lvr\R9p8EEbJ !abDNǵJlFˉ^})9QW`_I-Bif'΋Y @枴7X6`l5>Rr끝C.(})+"~q8[0~!hs-Q<-4^zR>jQ (v՝\Q\9Ad}sI!>+ml D T6  Jn=p;splu;ф9Q-_8 l=O ӭBronwN w`ߑfzJJxs:V5`nmXW 3 .'(lۗty l@\x[1i&=9Q |BD009%{3/Y;x N¾+kdm+_?>Y]y&#ؚ ><4[v z\UNj>C~b^p\Н`PŁU2of$ P6,;%ؗߣ7`CΉǷv2H+uK,[oJοIGv X\*UpLaI=R [reL2(c3=xX,<ɷ,EnE,وgxcG/HѳXȁd炍B1~йg#~ބ;򕏊%:iU$^ײַgtIT".1iV:gW2Yg1=UR{j׃Zv{H:B5tj`cCw/u%< 4FiP'hբ:ׂa~}<\ωݵNZϪ_eզqڇ'a ~_ j>\/kjnN_> [@RO_#Lxׇ-@u97}Ϙ5nK.79 sG10!rzKŦ<%߈!kky&|7CL`jOw-]@BL)~!Be-u[4F$?}>9MaҷY@70OAw@.C}:I_ fX~Eܮawta݁zvF-"wa.izf<.Wfǩ2#[|ow%^$J+cyZ?^ٱˆ5_{E~݉F -S0&ԞVZ {y{dcwGމ8vį8ݛcIHu}T}U GU?|Ϩ}wÿb#Ub~Hi%5:U[C!!KSK/2{ e[jaa7d1&A?Tmm~"39kGܡlڴ-LLqv*Q ,C9dMkJ%(}ϫƨuQHCuأgFtGq_7 b.S$T4՟`F?J"TzYox척Ob>sr)#ܫOmIIϼ OB>OA?e? <L|-aZ6[[?;foQSO ߁AHs3/%m޶Mlv;! -em*|=3GI'a.tii%,2Y"-tf]^| =,p3 SbY蹯%< Yh0*W?}TS".t)qm,tolAmv@[g?=KDTy*û-WrkXz[S/pϯi$J/CV0fs$ ]-x 6EP]߸ƍ>ŭ-.://IW&M@;|M;<(= AjO!A!;]!~ޘm "D YhWSܷ Um%{#GDYWb􍌊|vdʟ^|)ޯf1hgW'p8{k`< YcqU{G a?ݡU7QDESVn9*^wsN! ]X TD*;8䶔_뢚 \^̢].T(,懿5ۀ! ;_<YhJתIȓF&!@\.9ߥy7h|6ͻ袺ݻM"V[uHbߍ/+fnna6A䬬T)',vRs"!(M/esyegu8 Y xun= w#BJ߃/Cdp* *Vi&c)=|hބ|S%sQ瘕+7)3ʬϰ y#ü5*/A[.he}CCCaCP$>3FoTe,YiPsy90ˠz)"adu{I5!Kk@ Ēga(Yl Lfsγ;IW3XCoaNBqP>>m978Kx1D΢[,q_ys%goe.P3p&YK!hG%vAvL8y\ux](:7|TS32 ŸE@rnޮOBKī 7^E£a8H!o QtC\(JF]T|ur!F (^Zw>)["t}yB:o"'B1swo8}Nb@w>1mtoɴg?C/LC')[uF8nf, O}o{ѣ1EJ(^mߦqlrF1raHo̲f|+x$y87Z%'&<+3>=UJc2#uA>qrS /RX/ƹSNeI#o9M^85_sK#gg`E%neF@'FGek`Mxud$X}κQ/yN*{s$> zn:I7VқQs24PN&@? 4Q.d ӰOC;XR_~FiaÐ3P* xPY@Bh0z$ Ye| X$ad!-kD`p/d3:I YAN*Pq>n4(mٖ43hN>VigIUsDvkQMZR L{Q\-|bY~VgY~VѨ 04? [9 j+|&Yga4ѮUD? $!QtdsIcHºvD`0./a}&::'$?:LsZ'Y~Nu9N?$nZ2O5п]6!>+_nFF@Pjg$,6Q*_J-?niƢc^'0JFIXE&""_( Dw#]dt" c ,#P"o`Rэ@y#mW)2a(?>?Vgyh3( >.`t3^2N_U~Au /hu^, Z_U~A*`ZTY*d-/k_U~EX/*Xg "Z(:yw@$KZ;/|IKZ};/|IoK--ls&efm w̿fM^J-,oQ;µ#iDk)|VLz^.lc.*r;$Tj>;$^B[>@'pd{!wIBu?i;Y{߃av,b{TNpH)80 uz?L@ND1[5WrkB? $qeX%a]gKD`?0җa-QR qMl0n`u@'0n`շ#)-n+0̯huA`W`Vn?ot6l\q*0ƣ#_]~Uё|UWa_{th#_բ<:3Buu6kͯi>dkP3ӯ6 { )xvI?2 :J?2QS:ቊO0GShX^]k[E#J+[gGp+Ny ٤H8&[:!%oꚪq) C%[ 2?xmM>fJ&Gw|ȀJ\~Wmë3N^3ËL[é7 /6믽ngW^=h-9o); 쇍Ur:RI=[[1VLOUaBwnͼ}t.PSeaEmlrkj[NZLpW{R x|P9ɘ5T.f{򦧳؉o|F?w5Rg#@Cn |ozR7% BƀZ7 Ư*AsȤMZY︴Cc"[]]9-%LW lca% 5fLP{bN;nQC XÓ >GZUkϝpâkF&|L,c)~8%~xZ/bŔ~H񈛳6p2k4\F+גt>-\usZ>}ʚvwo$V`?~醵=րnXz޴ ;5pbu 8yJJm!'4Iaka)@'r2K+gMEZU>U< Y)#H!zejļQGߞR} ≛vԀ#}bi̚ ~HOTs V8\V }3PYu}^އ|_a'eo?^|M& 01!Q@en ^@yEؖw'}61GYzEfR.3'<2YCFJrx뮕Kl- TvvHcͿ[Ka*ӗ@Vdw0)N'00k Цmfd2}yfRܝ71J@w'gx.`7n%5`/d: 9hS~? EooeȭeLL w*~#xс1<'5@Oͥҵv9#7iQ4o;^{('䟝Qm׿>w@AS1 ' _,?kT}M5c4n}u0*5z(ԫ};CA[ߖs)Kv(- mJT (zF~=t~g+^ۏPq|#ؚ*{qӡ U[WRђB)J삉tIsي3^Ω. adS{/L(p`<9 <$=]K[}}a9BRx/A.o`PΥmӭyS!ҡt`YW2tZ#e^&3E3̘CLza(_6v5lƒi V|ڽj!\vB٫+ yZ[}X\P6yq&t#cO}e!QyB>P b[?MRE-Jh? 9?P'eB aCy;+c/@*7CA5CWvWWWlʢUEX~ۍ{yː/_Lf!OƠģ5n2d>䠭 x7*_'2ↀNְWy%1vwA.y&dҏ&FWZEJ[7޶FD]O0ܘA8D}s.F 1y>U` WIs_lNBQq[ _1btx3iN/ӟ)Wn{ yU#LZ˲p:"w8 YhPZ&e6A48fHByu`[Uredj\^04$^nsiLй^aM吜{f@70G9ӿtթBW+ YG!Bѥ+[cDA$NM@~nM=}TM>N+̚/J/.yx>yi-\u/ON[ Hs:K /;Oy#msnE杙s䲑]2S`LxX,oSA\`|fֽh9ڻL/}% i=D|?6BAfʣh"Ұ1聛%T \-ӎ2jr*'s݄ !$[mɹ/*qQDRdՒvUd 7kk𮩀)'4vA:2l83'n@g>ɚJi PZ\&{螭*͢U#o9o`I~"J1;<Ѓ^,ZT%Iy-h\ކ|[>;WV5S;t&mF2,}HFWS0&B携$ 5{\!tMR˝&]SrucΏq5@.*nW Uy/ Yh琨F`d6/e.=!=CVS^1} ZS7 Ay*ӥZo\㎧G8TZ!:KdۣL*zz " x*BA\!ǣn1B%8Y|z]׸[{ħY+ފiA5|ZĥpK9ܠRÍRkePio`O4P>c溾RNk's:<82%̙cFrm$t,{4p5ɍlz2࿀W d"㶂{(Ci/ַ5cZKKh.3rN/kޢa&{lNĭ7@Y>Ɍ il \t.+U1Ql l*bJgKg ={cǤ^s:QZNiغAw ,u"x 8y^Gz݇H/B(J/@~!M% ߓ6}M_ES,wY"pjF7*A"<)͉0Ku0'+frG5l1e T YI,gTB˖k4xaeJHT 8~Ce`C;c ~zx[n=Tv#Ή ;LM̯bbt@55Xv+eL&_tzmI7n>?,C޹}yEXW_  υ`s*n )dxNTcSqG礽f3.<,3˲)]0^eWH Jy8_1cҼnܳ8 :6;fCB&$KSN.2F~=:Tt`%YK[i4*pmKqeGB>(odvK~lc:m0,( ~~ En 5sa.43t:7:e頔5E\v]U,w>~;NrepZ5>Ϝcy~H:B$7fYGx;7>R M:[4in൮;u6/y5[&ţUfP&<.M ,;/vJ p!l{+Q;U3Q\ Tgz4,t OA/&9VF mZ }3hvAQ+#%^$jSV'OAR~/NC!wxUikn>N_>Yl @:!럾ENyEu9:c\2#]-QoW\Ygv( i{M9rUC(׵y30Ņ-N~iTN$(tAVaqKD'}cu,mHhf:?^ЊmE-[$om|u@ CimpGEyGQj"Qf` d!5Z*تI$<0Nopq# Y<@8qN١>9D}K;Y -3vL-I!GoT1[=b2s(oעqM7նEv71YwQ}vv'LwQ.o??\N'c]tqL["{Yb;QWߩ3f53i~-KX˸N;)Bޠ5oT.w* [!~BZn݊[^m!l3q%#-e䭷fP5ZJܷ`Q po=J gpr0u,o|ݐ!: }ͬ30pFQV?+_Qalvb߁FvʪJ(vBwx\Ms/Kv!-nߋ"Wi# ՜EG5iY/~MpB|/C⫭C }jcW!Y+`eLnab>(QӚW[]҂G \{cu ⑤ݗ^dv5pX'οEkP}p}mӋ9^?Ji}ng; NF?!oW7]1;Bnok,?T?f${ !QHy/Fό8:>7b9=W\7!IiK?S~Dae3|nE#G WڒJ/.y}|2z_E,h?x9xZյmnlce>~w W`!xL} g`>ɐjGڠ϶':YWG(g1r_|Λ.]KݽxĀ|bNŋ{{glΠ`_axߒiϮy:ׯ_'N&݋5S;tY[73]'=35[k5EKIYkz?raH U+ 1ezjw21a_X1WrDhJ?G ԡ3QWW?PV중SlK_o?iy~etԀj?%=_n?{X,?7G>1•+TU C(7 Z/Q|.>Bq~_Pģ |儌IrGtJRgĠZ+f.,Y:jM$"-լ34Lf $ ,J4U1/muņ,/*TAx!ii^=bͩ)7r_1vBVbc Y~?<Y_UvARݐXY;.Ygi (\=fJt!BL$L@NLa'ck8n0KGnX%aݰJº:R"#}7?ԑ2*H|#}L=Z)Ё1:4 H`t)pŰU^/0Iћ$ @?)`D`/^$<&I^<@Nyng8F^(YPgQv(j^X{}Z,i |/ ca(<Yi[S ӏd!\y߀E,B:IYkZ' Ye ߀EvBV:j&MScKd>XXIUO4}P aӤ* 9MI-k=(iN<1,߯IN3,hT a>}?&~&YwLt&H߄Eֵ'{1v $gOF7y` X'I~@0hN?V `M[K)AAY aD4 ׍.$F?$,6Q*_J-?niƢv^'[0J~ FIXE&""o( Dw#]dto" c6,#P"aRэ@y#mW)v(a(?>?Vg!hC3( >.`t3^NU~Xuðku^0,ZU~X*aZTY72~Vx-#ʏB?HXGlU~$R E'#Ga1vQ~Ts'QjvQ~To'Q4jQvm7%L1"'͏2?͚ڽ+,cFڑR" 5>+,@0 ēlP* }lp/d$I: ߁MoTVoMاzafMX,H?8*Qr$J 0LB^#Q̖f͕ܚ߅U8[]X%a]gKD`?0* 9[93ٕ=$a& N`&Oo7OFS Z'`O0 u~<]7m3$I%aGG> V#D#ёO.?'F>EytdgjRNm~J5ǧ`$}駠 B)ggm@[S*0d5[/Gd0JFIةqƸ|0JBu.(z{ jR耒S-*A< avǷ_5/a7du}DtA' @]S5$VA44j} 4IIVCylE>V4'5^{5:)60$:,U$&7unBL\u6Md!KۡS#UbV+$~6 Taf>Kf&m%*e\kT[ MvbZW!͕r5){CH>9QU< |#7*-f*8c!ҍ97¶KAфFt4ޢk.2KW*:zrIʻlyK)#DSJrx뮓Kl- TH[x&(m,Z1dS n#ay16mLF/8)UܗoIqw(<BCyo}D,ݐ{{oT\(ҖzI0:#LzB&^024VJĸ W0'"Ve%yVx9(_hOA!Gox<T? :.XK尟Jt] Т(6ݽSQB4?z tK{}oT\r T~c!,zRzkf~+HF;ɍvC&_|үI; /ܝ v՟5o=;o@!+VXuػ' (dSR+V5Q<Ϩe)SJOC9sdT\p+ݡ_`O!܃|/~GNſ i0C#OpңVȭ]ʁ Zӎu|v^bkˁk/L󎉉J709':RNM6{ÀF'F6_1'xT ,XL%cO(SIí)}LA$6i*zt&AV5)lpp=,"rxx5< Yx41^|EѠc- e3zz׏ͲCB LAȃ(G5})XU 5#cfmmcDȜbgKTC>}hs(:4/l\tsf>2y B*?MF!cΛ@p5&4¶v3_0=4)$aҙ=)cQP%vaӡ{!Fڨ.Q/viH|.cxYB/&Ӑ[525A<>dVj _ߧQ1'nCY84k4OhnT_;~]6KnxK/X^t6^K FF_1\!xz#<YhJ#gOTYMc5cD fNnQMn~%; ұn}fk <Y9ĮGQ-`~A605@7&F-44LYT,44A64O"d?e[}׍캽Lkf2'Eʜ.tb :d]:|R+/|9!A΁6/Ngޅy*|l5Y:ޏ"""^?C4ZZD&ϡ}ya ۴脍2>we/6N:_$q ,S:Y|l@Y$zJAD¢r;,|8MOt]|I~,Q2=^""7!ߔ&tmF ici>+rSaD>$eUAֵ%p)@/@Иj\Qh8 0|Rq//B}âg!?+m [Td>Lan,S!}܌Ɍ[I_@"<,Mz!4wJβ3 !gg \΄pY1VD'd'eF:q]Tzn/A70(紶>)6y G9 ܣqi1Gr5rJjF8h\kTMoUbˤ(҅ZnJH! yedΔwV? A5HϩJIFZ V孺,{/ %mci &dɱ- ,,k? mVO2-Yb~i`t VdMwUYӚ`"MZU''aִ&T!*k#g09%S= VdMU]+Ϛ\ ʚiÛ*()͚F[ǴiC灯jUYӤ\Yӈ`@4>U< |V5MZB6ZU4A 5|0UeMU*nE` N:ooC.n(i- dM$/-u*]ʳ E[ Ț&iT~'pV5-ưCiHAFVܗdM$YӢwZU4ޚثUeMҗڀY-5i>`@ִ86-8kתEexm N@VH?`Eִ;vXK尟Jt Т(`@ִ({ iD kUY$ =iQv4~*kF5UeMd$kZrqdMC 'iQY ȚW?Aşg"k %// /fLۙb 7_TF+B EirJghF-q.)WFu:7 LJ5J%­qB#O927%u~zeRU6rP${3^_5?28 ɞ_s ԩ[xzYuE3a)ȧ:n>=ހ|CڦsS7 ߒmn +dƸ 2`P`PqySht釄*RprfAR80xrL&KX7k4͚&D/7{!ǰZ ȓ*Ɔ굏A,IFWIr"ǁb}V ˳SԥaxX+b ] it!X8yLZk{h6bdq5)"u8yF!҄RMV!%Ið5( LXG>}TS,iE^c"%d}\J!TIJoOB뜤SQ&jƟ4j9OB|RD5>&R)B+0e!ʬFe5sn`PM/~dُ/e9ݙp ye K2j2^G'No @pD+%i_棭$E'SP -[38{V ]l`Pؽ~v* i"4D}#D)H%L%䨂n}#tZe9cOCS6.!%IY(yq&7H=Aֈf"BO5rK*[S_E@R,]D+dʐ&|GFc(Z`Z^NUȴPHNn`B @!ݖB6fd] @!hA\#ZU(U 8"Jƀ($U"pLPDZ)HE A} .q=bf6$p]c ' PN_j6kU(VLY~1;`Q(⳪6XR[$V%)ڴQULM @!(=a첈i`@(5 @!-dBQ(=p݋ecNrqe]/Q9 @UPjJy UJ`@p2> lk @ATzbQ6* BPW(q*E]Y`@(U4 @!ڪy7X QIJ˧Q1X".lR薩nӊg#pz0›Dy9U ʬ;<€qod7nCC`*K- ⑬X /VH:_ M3s orywnɛYeGx߇MpOJ}K(ٝ~@+ث\ZH(mϭ_<*]Op+CUO\5tؙM˭`,e&)^ K˴ ^P]:Dg0%v+T&MV {_/8@Jn$<$9:B>Zm7qw;~4UJo;N6ҡ&+ .2R'D"n2m,[Q+hO6H(sWROCЖhxc.!["L}jn]b$$D". X&$ǁ! \#Yȳ F@n"TЊk%,V^TEHtѸ*5q ::U^G[eqkޯ"ZzQӞ`ts`:M/1;w|vb@w>1ieR z%ӞuS˙&ĉ~MܪӫںɤGk,V^mߦ*O岶{R4VC~{tfY A<?cyZrnFwUߪ>]D^:|T:Qe1jƍSaG߈؟pܨ6G3 S9`^>w蓄*65!3:d.EjA<4F- I킼K[ bWǭ*Avá/g"cTC_ <6 dNPSȃ0:!y Q̪C>  #6N?x[ebC%q+HE 5c4#'v vU~[[%Mƒ*%5wbr_QNB; d;HZr[mKȐ)|; T>l|Su,ֳ<_ " lkSZ%̩]ݐvxu2&C]Ɉ{/Ÿἥ{T;)&E:̂oD} pB7Q3^1$;l\>EZ.0Jio`O4Q>ƛGI Dxh0(7h-ZYR8w { ]&v攸vCvuȺVn2nIql-,PFxS|ͬj܋ɜ3Vsb7v%`7 ߐ~nκܥofۃ(G5~[B]_]aJoOEԺ$z ޔѼu1½tm3Ar4Fa>i,ii]SHc*Ĉs+\vp܌D_2eLC~^7u(nYޱ! j^1Y cEBWj/@~8 yR|/ 2t*/Uò͑~=+dRz4rs>edX :2F=z__匙$%y8^B4Ǔ0ڝфQu t Z-2QM:E-kpuK ,R L.Gf@ O&$iZn'cL8 wAI of> R'{ʃ[+4G ]XԹnSs9mDu\sVglޣ>p4k]4}LSt"`@PKܥa_B o& 'Lt/}loN&)PWO~f&eodB-p&V;od-Ý Yȃk=yAM-\2١?.VVҶ_LN8oLHP~ ⑤3<.c:b3qՑ(G<4N4HHQl֊YwI’2Q,3qoeO}UB-&̅66N:ٌGNޗS)hZEȔZhmH)6(RJSTK#TN[DyqڮT .;"lg;^N0b8'%c_LETpudy4wITV#C dq’^o ů2w A<*{Fz *"\`ĘٮvT+,cWN:LC1PZaukJblve',AoJJ) NbHI^&IN,դU%Hrff`V ]sJNh^ %SZ)WV"PaJNj RDtN`V ]z-&;2A:_'6r(D굗A<1؀qT| $G QkinժsvUWbtnqxM-ہGM? Eo_;CV\sہ6܀w,ʌA vPOF"l}'[*VCnW^H/DsȒ4$7 JXSsne3j9 J沞OS>̧m~W

^H!> Bx rG ewN(xz.T{&a`}I;E\Y]$>`r"zv{ ˟i$8 <4II?6-2ͲB)“pqU i0$kj >Zolʯ dN%Pu2dqn*is{l׾bSu}R_/e0/#}姍N8$ywgx^|>< lg$tv $ k6`*r\Px톊;< 0 T p6ܣF934))ΡYWE~00ېoKիN虴7|;]I[n~f6u,۠ < W!_~^Z?:ΛnΎT:~~$mc%t $/eT/#6BlH+ W@PvA`y k>\`k|0Ni G-S2MMESgVH} n,xKY"'BŦ.W։<98*n 05N`*$Fm͕ܚ2טQ2ݑk) )0+/`EDMN(']򾺣J.o2Pn$!s$$^QM/7^O&ϭhDN.geΌ% ykffհ:J0$[]a? u§ ς:/ݸش(4Z05 ),zλᇅp7*y)ux_e 4ܷX">#v:Yyl)pȑ#@JBꔂKRHa8>K X%",Si{0BYL KPd5LaEvɧRDYho*EmCnVK{Me <cװf܅  w- ʄrܵc|~E+o`O4|;6tB}ޫ#Enx;`%Ӟ]}\_0'N Lsf2;L}o{ekfވ'|)k[r`u90 C~{tfY A<qr'S /=y0L$ ki84-ZX}J4I}tdD ̱HIg$1 a?6"D 3Y[@eztZaӔ7i4$q[z&N7&A&W ]f!1ps&2ϕr{-;W۲>7= EeҖWz'ƳW TA|AEo TP͟O* "v7}ԛPj|Tgja4RU=N(T{"~"a6 Q*'ztډm+w_[IO6?f%vܡ&,H2GrP]95"fl 4uw^+-;4-)HnCfCKT?pQַzKT­G؜C2ꆣp ul:8>#7a=G8oA>Qe{jtC ҍ.hɴRkoռK}EuVT3VXD-8 |*^_*5Z]*A<&I7kCHJלYtm;:'o wI5ƽ33ʜ/1NE/@̸k&j/@d;|x]wOBSs Qk1MmmZ] Vl*Lokk"Nߨ IJkm~t\JWkUMvx5^3lsx/2)3o 4xGgf]ym죵𬽲[xqmB!I4N.:}b$9|fUbᮤ^rQ`3U3덏7.T>{XnZ)6fΏ_ΘF~ִ La%;]̕Zj~+5;X6WͲBK۲B.RV4* mJ-\5rُ BgN7wʹS%Qy4[0?XQYT1nMMF{mgs~39Е g,UfX(\Wo8Uy 0RƓ|MiU}} bҿ[L!HGe,h "a"."b" DBI/tests/testthat/helper-dummy.R0000644000176200001440000000040014350241735016403 0ustar liggesusersMockObject <- setClass("MockObject", contains = "DBIObject") MockDriver <- setClass("MockDriver", contains = "DBIDriver") MockConnection <- setClass("MockConnection", contains = "DBIConnection") MockResult <- setClass("MockResult", contains = "DBIResult") DBI/tests/testthat/test-quote.R0000644000176200001440000000261514552712323016117 0ustar liggesuserstest_that("identifier", { expect_equal(dbQuoteIdentifier(ANSI(), character()), SQL(character())) expect_equal(dbQuoteIdentifier(ANSI(), "a"), SQL('"a"')) expect_equal(dbQuoteIdentifier(ANSI(), "a b"), SQL('"a b"')) expect_equal(dbQuoteIdentifier(ANSI(), SQL('"a"')), SQL('"a"')) expect_equal(dbQuoteIdentifier(ANSI(), SQL('"a b"')), SQL('"a b"')) }) test_that("identifier names", { expect_equal(dbQuoteIdentifier(ANSI(), setNames(character(), character())), SQL(character(), names = character())) expect_equal(dbQuoteIdentifier(ANSI(), c(a = "a")), SQL('"a"', names = "a")) expect_equal(dbQuoteIdentifier(ANSI(), c(ab = "a b")), SQL('"a b"', names = "ab")) expect_equal(dbQuoteIdentifier(ANSI(), SQL('"a"', names = "a")), SQL('"a"', names = "a")) expect_equal(dbQuoteIdentifier(ANSI(), SQL('"a b"', names = "ab")), SQL('"a b"', names = "ab")) }) test_that("SQL names", { expect_null(names(SQL(letters))) expect_equal(names(SQL(letters, names = LETTERS)), LETTERS) expect_null(names(SQL(setNames(letters, LETTERS)))) }) test_that("unquote Id", { expect_equal(dbUnquoteIdentifier(ANSI(), Id(table = "a")), list(Id(table = "a"))) expect_equal(dbUnquoteIdentifier(ANSI(), Id(table = "a", schema = "b")), list(Id(table = "a", schema = "b"))) expect_equal(dbUnquoteIdentifier(ANSI(), Id(table = "a", schema = "b", catalog = "c")), list(Id(table = "a", schema = "b", catalog = "c"))) }) DBI/tests/testthat/test-methods.R0000644000176200001440000000102614552712157016425 0ustar liggesusersexpect_ellipsis <- function(name, method) { sym <- as.name(name) eval(bquote({ .(sym) <- method expect_true("..." %in% names(formals(.(sym)))) })) } test_that("all methods have ellipsis", { symbols <- ls(env = asNamespace("DBI")) objects <- mget(symbols, env = asNamespace("DBI"), mode = "function", ifnotfound = rep(list(NULL), length(symbols))) is_method <- vapply(objects, inherits, "standardGeneric", FUN.VALUE = logical(1L)) methods <- objects[is_method] Map(expect_ellipsis, names(methods), methods) }) DBI/tests/testthat/test-table-insert.R0000644000176200001440000000161414444047701017352 0ustar liggesuserstest_that("appending with zero columns throws a dedicated error (#313)", { skip_if_not_installed("RSQLite") db <- dbConnect(RSQLite::SQLite(), ":memory:") on.exit(dbDisconnect(db)) dbExecute(db, "create table T(n integer primary key)") expect_error(dbAppendTable(db, "T", data.frame()), "column") }) test_that("appending with zero columns throws a dedicated error (#336)", { skip_if_not_installed("RSQLite") library(RSQLite) a <- data.frame(sep = c(1, 2, 3)) con <- dbConnect(SQLite()) on.exit(dbDisconnect(con)) dbWriteTable(con, "a", a) expect_equal(dbReadTable(con, "a"), a) }) test_that("appending with Id works (#380)", { skip_if_not_installed("RSQLite") db <- dbConnect(RSQLite::SQLite(), ":memory:") on.exit(dbDisconnect(db)) dbExecute(db, "create table T(n integer primary key)") expect_equal(dbAppendTable(db, Id(table = "T"), data.frame(n = 1:10)), 10) }) DBI/tests/testthat/test-sql-df.R0000644000176200001440000000037614552712157016157 0ustar liggesuserstest_that("NAs turn in NULLs", { df <- data.frame( x = c(1, NA), y = c("a", NA), stringsAsFactors = FALSE ) sql_df <- sqlData(ANSI(), df) expect_equal(sql_df$x, SQL(c("1", "NULL"))) expect_equal(sql_df$y, SQL(c("'a'", "NULL"))) }) DBI/tests/testthat/test-quoting.R0000644000176200001440000000064714552712157016460 0ustar liggesuserstest_that("NA becomes NULL", { expect_equal(dbQuoteString(ANSI(), NA_character_), SQL("NULL")) }) test_that("strings surrounded by '", { expect_equal(dbQuoteString(ANSI(), "x"), SQL("'x'")) }) test_that("single quotes are doubled surrounded by '", { expect_equal(dbQuoteString(ANSI(), "It's"), SQL("'It''s'")) }) test_that("special chars are escaped", { expect_equal(dbQuoteString(ANSI(), "\n"), SQL("'\n'")) }) DBI/tests/testthat.R0000644000176200001440000000060214552712157014004 0ustar liggesusers# This file is part of the standard setup for testthat. # It is recommended that you do not modify it. # # Where should you do additional test configuration? # Learn more about the roles of various files in: # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview # * https://testthat.r-lib.org/articles/special-files.html library(testthat) library(DBI) test_check("DBI") DBI/vignettes/0000755000176200001440000000000014561352217012666 5ustar liggesusersDBI/vignettes/DBI-1.Rmd0000644000176200001440000006004014552712323014064 0ustar liggesusers--- title: "A Common Database Interface (DBI)" author: "R-Databases Special Interest Group" date: "16 June 2003" output: rmarkdown::html_vignette bibliography: biblio.bib vignette: > %\VignetteIndexEntry{A Common Database Interface (DBI)} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- This document describes a common interface between the S language (in its R and S-Plus implementations) and database management systems (DBMS). The interface defines a small set of classes and methods similar in spirit to Perl’s DBI, Java’s JDBC, Python’s DB-API, and Microsoft’s ODBC. # Version {#sec:version} This document describes version 0.1-6 of the database interface API (application programming interface). # Introduction {#sec:intro} The database interface (DBI) separates the connectivity to the DBMS into a “front-end” and a “back-end”. Applications use only the exposed “front-end” API. The facilities that communicate with specific DBMS (Oracle, PostgreSQL, etc.) are provided by “device drivers” that get invoked automatically by the S language evaluator. The following example illustrates some of the DBI capabilities: ```R ## Choose the proper DBMS driver and connect to the server drv <- dbDriver("ODBC") con <- dbConnect(drv, "dsn", "usr", "pwd") ## The interface can work at a higher level importing tables ## as data.frames and exporting data.frames as DBMS tables. dbListTables(con) dbListFields(con, "quakes") if(dbExistsTable(con, "new_results")) dbRemoveTable(con, "new_results") dbWriteTable(con, "new_results", new.output) ## The interface allows lower-level interface to the DBMS res <- dbSendQuery(con, paste( "SELECT g.id, g.mirror, g.diam, e.voltage", "FROM geom_table as g, elec_measures as e", "WHERE g.id = e.id and g.mirrortype = 'inside'", "ORDER BY g.diam")) out <- NULL while(!dbHasCompleted(res)){ chunk <- fetch(res, n = 10000) out <- c(out, doit(chunk)) } ## Free up resources dbClearResult(res) dbDisconnect(con) dbUnloadDriver(drv) ``` (only the first 2 expressions are DBMS-specific – all others are independent of the database engine itself). Individual DBI drivers need not implement all the features we list below (we indicate those that are optional). Furthermore, drivers may extend the core DBI facilities, but we suggest to have these extensions clearly indicated and documented. The following are the elements of the DBI: 1. A set of classes and methods (Section [sec:DBIClasses]) that defines what operations are possible and how they are defined, e.g.: - connect/disconnect to the DBMS - create and execute statements in the DBMS - extract results/output from statements - error/exception handling - information (meta-data) from database objects - transaction management (optional) Some things are left explicitly unspecified, e.g., authentication and even the query language, although it is hard to avoid references to SQL and relational database management systems (RDBMS). 2. Drivers Drivers are collection of functions that implement the functionality defined above in the context of specific DBMS, e.g., mSQL, Informix. 3. Data type mappings (Section [sec:data-mappings].) Mappings and conversions between DBMS data types and R/S objects. All drivers should implement the “basic” primitives (see below), but may chose to add user-defined conversion function to handle more generic objects (e.g., factors, ordered factors, time series, arrays, images). 4. Utilities (Section [sec:utilities].) These facilities help with details such as mapping of identifiers between S and DBMS (e.g., `_` is illegal in R/S names, and `.` is used for constructing compound SQL identifiers), etc. # DBI Classes and Methods {#sec:DBIClasses} The following are the main DBI classes. They need to be extended by individual database back-ends (Sybase, Oracle, etc.) Individual drivers need to provide methods for the generic functions listed here (those methods that are optional are so indicated). *Note: Although R releases prior to 1.4 do not have a formal concept of classes, we will use the syntax of the S Version 4 classes and methods (available in R releases 1.4 and later as library `methods`) to convey precisely the DBI class hierarchy, its methods, and intended behavior.* The DBI classes are `DBIObject`, `DBIDriver`, `DBIConnection` and `DBIResult`. All these are *virtual* classes. Drivers define new classes that extend these, e.g., `PgSQLDriver`, `PgSQLConnection`, and so on. ![Class hierarchy for the DBI. The top two layers are comprised of virtual classes and each lower layer represents a set of driver-specific implementation classes that provide the functionality defined by the virtual classes above.](hierarchy.png) `DBIObject`: : Virtual class[^1] that groups all other DBI classes. `DBIDriver`: : Virtual class that groups all DBMS drivers. Each DBMS driver extends this class. Typically generator functions instantiate the actual driver objects, e.g., `PgSQL`, `HDF5`, `BerkeleyDB`. `DBIConnection`: : Virtual class that encapsulates connections to DBMS. `DBIResult`: : Virtual class that describes the result of a DBMS query or statement. [Q: Should we distinguish between a simple result of DBMS statements e.g., as `delete` from DBMS queries (i.e., those that generate data).] The methods `format`, `print`, `show`, `dbGetInfo`, and `summary` are defined (and *implemented* in the `DBI` package) for the `DBIObject` base class, thus available to all implementations; individual drivers, however, are free to override them as they see fit. `format(x, ...)`: : produces a concise character representation (label) for the `DBIObject` `x`. `print(x, ...)`/`show(x)`: : prints a one-line identification of the object `x`. `summary(object, ...)`: : produces a concise description of the object. The default method for `DBIObject` simply invokes `dbGetInfo(dbObj)` and prints the name-value pairs one per line. Individual implementations may tailor this appropriately. `dbGetInfo(dbObj, ...)`: : extracts information (meta-data) relevant for the `DBIObject` `dbObj`. It may return a list of key/value pairs, individual meta-data if supplied in the call, or `NULL` if the requested meta-data is not available. *Hint:* Driver implementations may choose to allow an argument `what` to specify individual meta-data, e.g., `dbGetInfo(drv, what = max.connections)`. In the next few sub-sections we describe in detail each of these classes and their methods. ## Class `DBIObject` {#sec:DBIObject} This class simply groups all DBI classes, and thus all extend it. ## Class `DBIDriver` {#sec:DBIDriver} This class identifies the database management system. It needs to be extended by individual back-ends (Oracle, PostgreSQL, etc.) The DBI provides the generator `dbDriver(driverName)` which simply invokes the function `driverName`, which in turn instantiates the corresponding driver object. The `DBIDriver` class defines the following methods: `driverName`: : [meth:driverName] initializes the driver code. The name `driverName` refers to the actual generator function for the DBMS, e.g., `RPgSQL`, `RODBC`, `HDF5`. The driver instance object is used with `dbConnect` (see page ) for opening one or possibly more connections to one or more DBMS. `dbListConnections(drv, ...)`: : list of current connections being handled by the `drv` driver. May be `NULL` if there are no open connections. Drivers that do not support multiple connections may return the one open connection. `dbGetInfo(dbObj, ...)`: : returns a list of name-value pairs of information about the driver. *Hint:* Useful entries could include `name`: : the driver name (e.g., `RODBC`, `RPgSQL`); `driver.version`: : version of the driver; `DBI.version`: : the version of the DBI that the driver implements, e.g., `0.1-2`; `client.version`: : of the client DBMS libraries (e.g., version of the `libpq` library in the case of `RPgSQL`); `max.connections`: : maximum number of simultaneous connections; plus any other relevant information about the implementation, for instance, how the driver handles upper/lower case in identifiers. `dbUnloadDriver(driverName)` (optional): : frees all resources (local and remote) used by the driver. Returns a logical to indicate if it succeeded or not. ## Class `DBIConnection` {#sec:DBIConnection} This virtual class encapsulates the connection to a DBMS, and it provides access to dynamic queries, result sets, DBMS session management (transactions), etc. *Note:* Individual drivers are free to implement single or multiple simultaneous connections. The methods defined by the `DBIConnection` class include: `dbConnect(drv, ...)`: : [meth:dbConnect] creates and opens a connection to the database implemented by the driver `drv` (see Section [sec:DBIDriver]). Each driver will define what other arguments are required, e.g., `dbname` or `dsn` for the database name, `user`, and `password`. It returns an object that extends `DBIConnection` in a driver-specific manner (e.g., the MySQL implementation could create an object of class `MySQLConnection` that extends `DBIConnection`). `dbDisconnect(conn, ...)`: : closes the connection, discards all pending work, and frees resources (e.g., memory, sockets). Returns a logical indicating whether it succeeded or not. `dbSendQuery(conn, statement, ...)`: : submits one statement to the DBMS. It returns a `DBIResult` object. This object is needed for fetching data in case the statement generates output (see `fetch` on page ), and it may be used for querying the state of the operation; see `dbGetInfo` and other meta-data methods on page . `dbGetQuery(conn, statement, ...)`: : submit, execute, and extract output in one operation. The resulting object may be a `data.frame` if the `statement` generates output. Otherwise the return value should be a logical indicating whether the query succeeded or not. `dbGetException(conn, ...)`: : returns a list with elements `errNum` and `errMsg` with the status of the last DBMS statement sent on a given connection (this information may also be provided by the `dbGetInfo` meta-data function on the `conn` object. *Hint:* The ANSI SQL-92 defines both a status code and an status message that could be return as members of the list. `dbGetInfo(dbObj, ...)`: : returns a list of name-value pairs describing the state of the connection; it may return one or more meta-data, the actual driver method allows to specify individual pieces of meta-data (e.g., maximum number of open results/cursors). *Hint:* Useful entries could include `dbname`: : the name of the database in use; `db.version`: : the DBMS server version (e.g., “Oracle 8.1.7 on Solaris”; `host`: : host where the database server resides; `user`: : user name; `password`: : password (is this safe?); plus any other arguments related to the connection (e.g., thread id, socket or TCP connection type). `dbListResults(conn, ...)`: : list of `DBIResult` objects currently active on the connection `conn`. May be `NULL` if no result set is active on `conn`. Drivers that implement only one result set per connection could return that one object (no need to wrap it in a list). *Note: The following are convenience methods that simplify the import/export of (mainly) data.frames. The first five methods implement the core methods needed to `attach` remote DBMS to the S search path. (For details, see @data-management:1991 [@database-classes:1999].)* *Hint:* For relational DBMS these methods may be easily implemented using the core DBI methods `dbConnect`, `dbSendQuery`, and `fetch`, due to SQL reflectance (i.e., one easily gets this meta-data by querying the appropriate tables on the RDBMS). `dbListTables(conn, ...)`: : returns a character vector (possibly of zero-length) of object (table) names available on the `conn` connection. `dbReadTable(conn, name, ...)`: : imports the data stored remotely in the table `name` on connection `conn`. Use the field `row.names` as the `row.names` attribute of the output data.frame. Returns a `data.frame`. [Q: should we spell out how row.names should be created? E.g., use a field (with unique values) as row.names? Also, should `dbReadTable` reproduce a data.frame exported with `dbWriteTable`?] `dbWriteTable(conn, name, value, ...)`: : write the object `value` (perhaps after coercing it to data.frame) into the remote object `name` in connection `conn`. Returns a logical indicating whether the operation succeeded or not. `dbExistsTable(conn, name, ...)`: : does remote object `name` exist on `conn`? Returns a logical. `dbRemoveTable(conn, name, ...)`: : removes remote object `name` on connection `conn`. Returns a logical indicating whether the operation succeeded or not. `dbListFields(conn, name, ...)`: : returns a character vector listing the field names of the remote table `name` on connection `conn` (see `dbColumnInfo()` for extracting data type on a table). *Note: The following methods deal with transactions and stored procedures. All these functions are optional.* `dbCommit(conn, ...)`(optional): : commits pending transaction on the connection and returns `TRUE` or `FALSE` depending on whether the operation succeeded or not. `dbRollback(conn, ...)`(optional): : undoes current transaction on the connection and returns `TRUE` or `FALSE` depending on whether the operation succeeded or not. `dbCallProc(conn, storedProc, ...)`(optional): : invokes a stored procedure in the DBMS and returns a `DBIResult` object. [Stored procedures are *not* part of the ANSI SQL-92 standard and vary substantially from one RDBMS to another.] **Deprecated since 2014:** The recommended way of calling a stored procedure is now - `dbGetQuery` if a result set is returned and - `dbExecute` for data manipulation and other cases that do not return a result set. ## Class `DBIResult` {#sec:DBIResult} This virtual class describes the result and state of execution of a DBMS statement (any statement, query or non-query). The result set `res` keeps track of whether the statement produces output for R/S, how many rows were affected by the operation, how many rows have been fetched (if statement is a query), whether there are more rows to fetch, etc. *Note: Individual drivers are free to allow single or multiple active results per connection.* [Q: Should we distinguish between results that return no data from those that return data?] The class `DBIResult` defines the following methods: `fetch(res, n, ...)`: : [meth:fetch] fetches the next `n` elements (rows) from the result set `res` and return them as a data.frame. A value of `n=-1` is interpreted as “return all elements/rows”. `dbClearResult(res, ...)`: : flushes any pending data and frees all resources (local and remote) used by the object `res` on both sides of the connection. Returns a logical indicating success or not. `dbGetInfo(dbObj, ...)`: : returns a name-value list with the state of the result set. *Hint:* Useful entries could include `statement`: : a character string representation of the statement being executed; `rows.affected`: : number of affected records (changed, deleted, inserted, or extracted); `row.count`: : number of rows fetched so far; `has.completed`: : has the statement (query) finished? `is.select`: : a logical describing whether or not the statement generates output; plus any other relevant driver-specific meta-data. `dbColumnInfo(res, ...)`: : produces a data.frame that describes the output of a query. The data.frame should have as many rows as there are output fields in the result set, and each column in the data.frame should describe an aspect of the result set field (field name, type, etc.) *Hint:* The data.frame columns could include `field.name`: : DBMS field label; `field.type`: : DBMS field type (implementation-specific); `data.type`: : corresponding R/S data type, e.g., `integer`; `precision`/`scale`: : (as in ODBC terminology), display width and number of decimal digits, respectively; `nullable`: : whether the corresponding field may contain (DBMS) `NULL` values; plus other driver-specific information. `dbSetDataMappings(flds, ...)`(optional): : defines a conversion between internal DBMS data types and R/S classes. We expect the default mappings (see Section [sec:data-mappings]) to be by far the most common ones, but users that need more control may specify a class generator for individual fields in the result set. [This topic needs further discussion.] *Note: The following are convenience methods that extract information from the result object (they may be implemented by invoking `dbGetInfo` with appropriate arguments).* `dbGetStatement(res, ...)`(optional): : returns the DBMS statement (as a character string) associated with the result `res`. `dbGetRowsAffected(res, ...)`(optional): : returns the number of rows affected by the executed statement (number of records deleted, modified, extracted, etc.) `dbHasCompleted(res, ...)`(optional): : returns a logical that indicates whether the operation has been completed (e.g., are there more records to be fetched?). `dbGetRowCount(res, ...)`(optional): : returns the number of rows fetched so far. # Data Type Mappings {#sec:data-mappings} The data types supported by databases are different than the data types in R and S, but the mapping between the “primitive” types is straightforward: Any of the many fixed and varying length character types are mapped to R/S `character`. Fixed-precision (non-IEEE) numbers are mapped into either doubles (`numeric`) or long (`integer`). Notice that many DBMS do not follow the so-called IEEE arithmetic, so there are potential problems with under/overflows and loss of precision, but given the R/S primitive types we cannot do too much but identify these situations and warn the application (how?). By default dates and date-time objects are mapped to character using the appropriate `TO_CHAR` function in the DBMS (which should take care of any locale information). Some RDBMS support the type `CURRENCY` or `MONEY` which should be mapped to `numeric` (again with potential round off errors). Large objects (character, binary, file, etc.) also need to be mapped. User-defined functions may be specified to do the actual conversion (as has been done in other inter-systems packages [^2]). Specifying user-defined conversion functions still needs to be defined. # Utilities {#sec:utilities} The core DBI implementation should make available to all drivers some common basic utilities. For instance: `dbGetDBIVersion`: : returns the version of the currently attached DBI as a string. `dbDataType(dbObj, obj, ...)`: : returns a string with the (approximately) appropriate data type for the R/S object `obj`. The DBI can implement this following the ANSI-92 standard, but individual drivers may want/need to extend it to make use of DBMS-specific types. `make.db.names(dbObj, snames, ...)`: : maps R/S names (identifiers) to SQL identifiers replacing illegal characters (as `.`) by the legal SQL `_`. `SQLKeywords(dbObj, ...)`: : returns a character vector of SQL keywords (reserved words). The default method returns the list of `.SQL92Keywords`, but drivers should update this vector with the DBMS-specific additional reserved words. `isSQLKeyword(dbObj, name, ...)`: : for each element in the character vector `name` determine whether or not it is an SQL keyword, as reported by the generic function `SQLKeywords`. Returns a logical vector parallel to the input object `name`. # Open Issues and Limitations {#sec:open-issues} There are a number of issues and limitations that the current DBI conscientiously does not address on the interest of simplicity. We do list here the most important ones. Non-SQL: : Is it realistic to attempt to encompass non-relational databases, like HDF5, Berkeley DB, etc.? Security: : allowing users to specify their passwords on R/S scripts may be unacceptable for some applications. We need to consider alternatives where users could store authentication on files (perhaps similar to ODBC’s `odbc.ini`) with more stringent permissions. Exceptions: : the exception mechanism is a bit too simple, and it does not provide for information when problems stem from the DBMS interface itself. For instance, under/overflow or loss of precision as we move numeric data from DBMS to the more limited primitives in R/S. Asynchronous communication: : most DBMS support both synchronous and asynchronous communications, allowing applications to submit a query and proceed while the database server process the query. The application is then notified (or it may need to poll the server) when the query has completed. For large computations, this could be very useful, but the DBI would need to specify how to interrupt the server (if necessary) plus other details. Also, some DBMS require applications to use threads to implement asynchronous communication, something that neither R nor S-Plus currently addresses. SQL scripts: : the DBI only defines how to execute one SQL statement at a time, forcing users to split SQL scripts into individual statements. We need a mechanism by which users can submit SQL scripts that could possibly generate multiple result sets; in this case we may need to introduce new methods to loop over multiple results (similar to Python’s `nextResultSet`). BLOBS/CLOBS: : large objects (both character and binary) present some challenges both to R and S-Plus. It is becoming more common to store images, sounds, and other data types as binary objects in DBMS, some of which can be in principle quite large. The SQL-92 ANSI standard allows up to 2 gigabytes for some of these objects. We need to carefully plan how to deal with binary objects. Transactions: : transaction management is not fully described. Additional methods: : Do we need any additional methods? (e.g., `dbListDatabases(conn)`, `dbListTableIndices(conn, name)`, how do we list all available drivers?) Bind variables: : the interface is heavily biased towards queries, as opposed to general purpose database development. In particular we made no attempt to define “bind variables”; this is a mechanism by which the contents of R/S objects are implicitly moved to the database during SQL execution. For instance, the following embedded SQL statement /* SQL */ SELECT * from emp_table where emp_id = :sampleEmployee would take the vector `sampleEmployee` and iterate over each of its elements to get the result. Perhaps the DBI could at some point in the future implement this feature. # Resources {#sec:resources} The idea of a common interface to databases has been successfully implemented in various environments, for instance: Java’s Database Connectivity (JDBC) ([www.javasoft.com](https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/)). In C through the Open Database Connectivity (ODBC) ([www.unixodbc.org](https://www.unixodbc.org/)). Python’s Database Application Programming Interface ([www.python.org](https://wiki.python.org/moin/DatabaseProgramming)). Perl’s Database Interface ([dbi.perl.org](https://dbi.perl.org)). [^1]: A virtual class allows us to group classes that share some common characteristics, even if their implementations are radically different. [^2]: Duncan Temple Lang has volunteered to port the data conversion code found in R-Java, R-Perl, and R-Python packages to the DBI DBI/vignettes/hierarchy.png0000644000176200001440000022345514350241735015363 0ustar liggesusersPNG  IHDRJPwFiCCPICC Profile(c``RH,(a``+) rwRR` \\À|/­+JI-N8;1doyId$e @"- v:}¾V dl&]| SR@0$AIjE v/,L(QpTg^)(!?ÓQ B bs$20A20,a`S3d`g`7' j #1!>CI pHYsgR@IDATx |չHH&  hPTIe K [B@?JQ[*P-޲IPH,H s dO&3gY|uf9K<@@@@@<4@ذaǻt `\,/@@D% 7nL6M#8T':^*C@Hzڏ uԑiԨH` 8u D@(Sfgp     $Jݼi    -@l#@@@@@7 QL@@@@@leq    R7`    e (-ۈ3@@@@@Hy<@@@@([DiF    n.@;!    @$J6 @@@@psn4@@@@ QZg     (uy     PҲ8@@@@\Dw0C@@@@Hm     $Jݼi    -@l#@@@@@7 QL@@@@@leq    R7`    e (-ۈ3@@@@@Hy<@@@@([DiF    n.y 6liӦN>}z"    QhqCX~R[xڵR_E@k\__t[Q>G@-GI) M믿[Y&+)IrѶnZZ֯RCO~;i>VsbDZU @@L,@ĝG  sr%=zWn4[lH{*;O~-HlZb™#ẻҩ;^fj#~ [I{9)4E@՛,}#`9nqv\N$%Jbbw 40   ++  PQ$[=[̅$wy!""=.nڟ]f7LSx %ݝrIrL_P-G$*($2%}dOjM,JçΖ-}1Yp XBs˜n 3[S},~5RXğ8+\>(CW4ms5ںrĆ @1Z<ت3IOmeOl=%@,**Y\3om|^T<mX}@d>v}uMD 욾 5Jݻm*a݆^ =KOd\4ٿȽIKWHU[1)*[k>[#z^-[lۏr2ܡeW-'@@"va@@|idL I4r>LJIm6g 7rtUE'=&'SR$99Y\cwѤdLcZ!ٳg:_>}:)+9~IIH5'M}`璚-i22zUx2)fd1v4hGVK^Jt"u#I<{fH$czrG- )e|{\IO=$K/5H=cg"j)}'Y^mGW?ID驒} 39AL+/5ef9*)F_SjIv1Ҕ2e@@{ 3{HY  `mʮ]QF)R.yhOPc&ʢըlY:OF[%YWT,mNY*~mlG}T8Iʙ_8>} ir~Iz>t(jhAg$hWW&eK wA|2$@滄Γ8ԢǞldjppHbMZ.2w+v1Kdͨlc3'vcUewK\I^˼,0c iذL8 v@L'Ru# irW(1sB$UeIfF.'ON*H'r.@!ŮR,?IoTf!3[IRuOƨ׊$$X&.FRH,6Ij$:M$Um_mlZ#taXѩAdn ?P8 @@$JH  @91,cd%D,bsJ55Br̤tNދN brZ <`34ӷe?YuBL-%Sn7FuNۃXumZ$:i\g=VdSEO-#V/F&Wr͔M?ʢkEH\֏3~' 7퓬V/LxBN /|^p̜INd n|  `w۝@SH)'k˙id_ۨƻN#i6Pߚ_Ίs%-\P&%-/iY )!ӈǟ.Z/4hXmW*.LI[o6elհ]ؿΔr-hQH_닋Bnэ4@hf2  @u xo&[/i,и]JZr:zUDTzgȚw^)L"|,F^{Pef-[UnFī  H:Κ@@*+_^l׽̍f>؍*[-! xkzN_R@@ -ؼm$r@@ (u*?# K?X]2SBك)8|D>!ߋ`4i09 @@8s  .&%!Q$θeggKI&J|" TEOUZ@@ q   `OS@@@@@$JMm     QjOMB@@@@S (5e4    SD=5) @@@@L)@ԔF     `OԤ,@@@@0RSvA#    =HS@@@@@$JMm     QjOMB@@@@S (5e4    SD=5) @@@@L)@ԔF     `OԤ,@@@@0RSvA#    =HS@@@@@$JMm     QjOMB@@@@S (5e4    S˞Q O2ydiР $@3g̛7$@@MFq[h  ,;wt@ x{{s=W+8@!@    `RSw#    =HC2@@@@@$JM}     QjE@@@@@S (5u<    CD=)@@@@L-@G W̙3 @ϟ7E !@5(@k׮ɲedРA /xDid[n>9 O,- ^  i$J=i/ Nؽ{e„ BJ8}$%%`ddv]v%66Vڷo/cƌuIvvٛF  P 5ʥH@pT=ztɒ%#G#GJƍ=\ Ç_ۗx\Yj۷Ohӈ Zj٭ B@ (5o9 .'puٰae:A#\:$J]/<%vڵkE%MSRRdС)?N@(FDi1(< otrt͚5jv+=RDGv4Z-ojei @@Z@@ZZXB'HHRݱc4k^UP P-Z^{Mj3<#wyN@pǴ@ ͛urһ׿{ҹsgAA |AQ3fȞ={tTaj~F" @5 0)@wPԺ+WvITT 2DܡyLwrP}7oޔx4GISuʁ #RKZ ].]*AzE{׮P jՒ^z[vvlڴI'M'O,aaaz>}+7@@(-  )?ѣjU~ڣݻwF:*,!111zDZϴ[nRF*O  x7F@\N:9l2=bTm4l0wX H_zZΞ=+k֬I3g~#>>!`J6v@rre-~~~zJlAP  #be״@iiirJ QrfL*BG(K ((H~޽{uҴW^:Q>eVBu@)rBq ͕͛7W_}% .]8:CZQZ?|:i6zGD2Unb cH:ƙZ@(ÇurT m׮DEEM=ԩS283 (5So \~]o߾]z)4ӧKZg 0廈@|QN@FzLWP@ʒMJJ#Fj)@* xyya0׮]7ի7[4Uy #Jݹwi @ /^,ׯ.]ѣdS; 0ԝzKdݺuzzÇ%<<\ϐڵԨQÝJ[@$J @RSShQ3FF)7`IJD)p}ާFFGGEmfO~D @9H@<[ƍa=~2tP=z4$$ijah=v QjD@ǎӣLW\gPDDDi֭U! `7D@78pZfyurtF)8WDs&Pv=j]wUb@Sة@DQS&Mjj}BB4oܕ&6@.fV۟'پ}?{l=%?22Rk@02j\ veݹsQG4]ci.&RAj[i\\t]|١oKr@OgK &8r䈞Z6urԩS" 'Pvm0`]rE֯_/-I&IuҴGRV- @}SO=&-WDyӧjFիW(S5=l\ @HV@\Y:9|r=vec W5b4kÇQWi-O , L ̔kɓ'gO?Tڶm`@JxEf̘!wIP ISgÆ K-@#JH .!)jh^f͚.A @(-ޅgd7orz6m{L'M(wy'v@j`Di5R4 @ :uJ.]oYfIrj@@jUS*i:e IS޸wO )wZZ ++KԚ _222tt2~x]G@ZWg$&&?|/,?//"! P FVK@#g%I7ڥKׯxyvV@+Pn]yٳf3gf#86(jCpYMW@=e˖*!ݻw4n=L@@\M6^zIRRR&P/]!*iڦMrI (6s ܸqC6lؠG۷O;\U`3R 8p@'MW^-M4 Çw]x@(FŠ s%Kbѣ걏sV@0 noܹSk׮Ҿ}{ Txx 9@`D@*pyYbZ55j4oܡqP8Oγf}ZoȥKDm6- `fFpQYQWMiS?SRF @Y(u<"@IzJaF)?$ {(u~ K?~\]ls=zja$ %#pM/Dݫk֬VZ餩|Ӹqc@L 8Xʕ+K7ey|zg$@@=̞=[[:u>>]s &` :@W8uꔨiK,z#FJā&` ;@@ ##C֯_jmv~@.` ` &D'%111zjّ#GFGfXu 5#v$JݮKi+p9QkZJj-S5ҴcǎkB@3 (5So+ @={董j.]]/^^n*|XFP[5<҄F# Q(iA,p=rtŊz(2dSTe (-ۈ3@3RSS2IrQAEFFJppgj@z_8RzGUf?j(U˖-u! AYf/ѣG(_z:~DD1BZnm(@@ 0 t2tҥo>}zY&[GSQ)=M;@^IUV=ܣGѦwu@#HzdhpǏuGUEzÇK@@;46  (Φ `W>Lz!42dԩSec&0@UHJO P1 E54""BoU8p ޻F?P@MARdԨQuViժ [C  TL 00PLoПմ&MX8QD'wUXӧ̘1Cz)g2_w1  {u(;wIST(pWj@zz_=n&uGMmƤ6fRYKi x;ޜ@GWV҃ x 4߿9"@*$ qq2x+Wdڵzj/#GԻ}5H9@@@toooyիgɲeW_}iϞ=VZī Q hA7)jh޽f͚i"&`D:P@;\xQHP#M=*jT T.]P:E  QZy;D78}tuJTTAZ~}7j%MA\SDk Q!PW^-*i6KU[Z۔pã-N} 2YYYb <<\222d/, 4޽* PQp9 .ѫW]y.+!  @ֹsd͚5oӧEe;vZ%\'fN4yl޼Y.]**):p@ }'ܧ6sN N8!R Su HHJJSWX?_ "uP[D@W8tN%5j7>|8\È ` t! @/_֋jjͨQd֭ҪU/ @@8:͜9SvܩOtMtTmZ~}s P#JKp@^^ѣһwoQ=FN@%R{IR @Y[Q[lΝ;뤩 je:/RcZRRRjQZ?gQ s   }۵kdƍ:iF̈^z:]0nݺ%#Gd!uB@!@ԉ PGGi֭s9 zo#\*-+Wp t=~2afXF@@>~'||{Z4,,L?>w!y(>8T믿Sz:uS:X@#Jw `&(>Lz!=5`$V QZ O!@Ξ=D_dԬYS'GyiҤI j@ QJ@qlٲE'Mm&ݺu0;5 M6ѣ{!C(>f@@@j׮-ԷL=tѢE+O?j15\_GDK !!A7o u   @95j$ƍӷSNjkdzMvڕ$NAG 0ԑԅn޼Q;vȀt'0q@Q @  #W#M(ӈiѢ#(Ce2.,/+VH۶mLϗ;ih?   P!ۋ͘1Cvޭ=zߵTtСҰa  `?V%%!6/_?X???ٺulܸQ'JIMW:@IDAT@@p@ΝwߕG믿.jSܐ=tz3'Fx#J=i8yyy7f^zɴiDYF y   `ZjI޽-;;[6mڤGN AXd^A#jѥKJfQ5CÁ #Xԁ `65/&&Fo64hN> f1[giQj"P'pYnNDȑ#}gJ( @@@u֕{NΜ9#k֬ѳΞ=+Æ #F?\ 0 ;wQhnQ5CM@@Y(u<"Q %%EO_r?22RkڦM36p).N>իj:ѣ/ 4e @%HVK@08ѦwuF} @%h\ կz3tYx$$$Ȅ $ !  e ӟȑ#oʷ~+]vuN:>x`DGt3{jN:ѣgwDO@;@ 0ԤG .)#[n Q? {wC??"1?.:tw}5Ex“QIM[R@-=gyuֲgYb <$[:B-&Kl… Eˁ ~ZIIIzeˤ]v2~xٲeܼy5jȎ;EҹsgoAQaNsCƍi&=zT"2d=裏Gi F/e#Jը߾}aÆn@@p dڵzj9zFvҥ ˯~+ pSQ)=M;B 11QL Tm{OHE@c4@5zPu͚5㋙- @m۶+x = ԣK&QxROmjJ߇~וy/R:*Qkv4 g (US T1i$VZz]?/;ȳ>+j:j@>^U;[ѣԨQKy @P̨/ɓoMi f~Ni~5?gΜGꤪ^ˁ 0z8M@MG/ Mh{|wtR}urTX`{*@p{5tΜ9:Q6rR3+8@@9>>>zMR.iiWw QꎽJ*+L8Qݢѫ?Dz}ڵzJ1B?Vq  m۶?0^xQԨ]v7O& B@}@zJ& gZ.7h@V^-+W _w]USyCW/ "/xyyɵk$%%E+X@@p@MJ\@M39sK{=ƲI.]^zIoEI~HZ"q@C''N5T|@@%@YkZҥ;rbۡvTkL0AR@(^@%GH .x@@1Lw3'|"Ndhi;vLN5@<^UVҰaC@@9(u;L@r _~Yӥ$j^ffdM%\@.#$@@B]-0@q_|DEE稍'ԩ7PkJF@i׮׿?  PѣSN%  8Fq ۷O}QַMʽ+m۶ }_=V}&m%a#   (5Fjƍr&/!   YD{@@@@@.ldF A@@@@3 (5s;    ED])@@@@,@̽G     `va@@@@0R3#    ]HڅB@@@@@^*ׯ{3s[@B@}ڴiҤIg 999oKzz+C  .&+"#;op?5h,_~L8i1Pq|w.ޅg@3 X~w#JUcԈ^x"v@ AҥKpו6l+u .$p)Pll+c@ߝY}I     `v@@@@@0Rs#    H"@@@@@$JD    v QjD@@@@@s (5w=    AD)@@@@-@G     `v@@@@@0Rs#    H"@@@@@$JD    v QjD@@@@@s (5w=    AD)@@@@-@G     `v@@@@@0Rs#    H"@@@@@$JD    v QjD@@@@@s (5w=    AD)@@@@-@G     `v@@@@@0'z dIK}ߢ   >xI.A  ,@ԓ{ ۞{e$1kt Y=M@0@, jǘI 7@p@&'k"Hԕ"M[Q2"֟ZD w@N 7[/Jx+iīA3fXع3SSnjkJZ6#vTa|@@ ͒=s]8(ʓ)M?I lIMOyD{:"uRNCipwSicCEN:H)u5CwD/׷/iW[5#1ʩ(4]Ff|2mP\uaҴe ҩK_"9iUDIV@ޛ{RzK6P{-UۢCOwh)rTײTt;29hq?|8~[ϕs'JcsxX9+/c muƏ֟ZlO1  =sy罵b|-/P?5J>Ԭ2oZ%"OϾ"im\#S>h ccn:wM )υ}vwfjr`q| 7O1w \ȕm*sf:F'[,˔59 AUcdev7TC&vR_.22 X T731FFO/{߬)FS%1-`-LTm.??]7Hq](UTP '1XT&SWW?X]@ [ޖY ~m>s,ϭFL>gl8?"wi$JTA9]ڗYrh9v;M7dA̹r׫fE>)1E Wz7?/9U&0r")Q z `V$7j)$$iqVݻxV = _)LUKLp~^7~_i&,׼6oLFI YgA՟q<6oR%Y .g}M;5潯e$gƲ^u?xܼ%}1>clSrD%r..7u̼q燎7xmjԩ6Y㬯/=xn%U+oŻgFl3K.0}sV{=TPq>_U,W-_kIK,?W= Y'68jHWËysms{fI%cQf2bfOUP>U3oSQJkzpNȲZzʚ:[% ٲ7U:53K3xpKs~6٥~ҐM39zRf_{7Wͅsy*;M02bY‹eƭgI2zK6QjM~?hq#L{QƏ/>;Djx7 \h[ Qiͫ4Xt# JpJ/R'H+=:H>crb\7[Y`IA$餹Ѳ;1w?QU?l$ڀ@6hqvX]~emk.l4-npkw%tXk B~ddj&".M;wL2$Ir?{sUJ w,uÓa@ ީ/zwݺ{j$Yk*-:խsg}./rZb *ަŽBFb^* O13Lc^h?nUJ: +t&N{/: zkځ \"U:F3?RvS|6?urE'1OF̿mmӶkf}l;Bհ8ks**-E4 8F{Sڷa}b1k%Ͷg8 1{Q2] ~QfKhqp9?\aW .ezr}9S9{=>To@/3 ~rty#z)Jq2StfM}ߵfzX,Uő\PJզ@ǣZ/O>ykz.hMU{Yð=B؅ 0<׽PJszǾ֣YW[Nx(K vz|xTY3ݕrYcfWVfio:ۼ7W"VLL?;:ߨ5o&1C4LGLy߬8g}{VMPPK|單̥JZ(X̽qsbZ7({4yEz7b؉L<7\5chEҪ …qׯoFҘQϽpTy)v-n^2]e3%#O{^iˆa6<״Eg`^hR6o嫸&3Ov>3,|ǝnYnF7 CߨE4I@ ʏb]LrVO{$[CƝϪ)kR WBjmԤ~x2ڪ__'H^ؚGۗ̇¨O֕{ FYo5'MT7xΕXӚҡڃVI{]]{fP!&v>ЃukDƾ+_B՛FЭi5/;bj$V}KyId_t^J5OOҦczq } tҕwY"=MO:JV3 46aq8"Wn@OFRkz01 Qs@`" A쎦[mPڊ~Mј;jm7?y_Zo. 1uZ%`a%=+OkwͮݥL-> D PNw'ض+ޅtx5w[wH;;0-[5 q޼ܵI=1)Y{o_P{KoܥՎ^'ť %zX+ԃ&9NfV/NM\] Hٽ256iFkP7_LQXs++d\ٗ;BH5ڬ`.Uj)s>,k\Zuik{Lj툡m19kXOd9]9̩\sؽ럜݆<}Fp/-]7*S.awo?j[]nNxu4_=5գJKpZo#WUi;jib/ݝGǓ`SV^zN+eN?UN'WyKWg:? k(m᷂üz}gn)#oMt̓Ua+ֺ$>G5 l` \"k 82qy@`iY>7'x30O+o~PSca4ڻabs2==crѩƃFR+(Cݝ7֙lg~kzcUa]%լ?y OTNr &, 0 "mzz}zUjo]ݷ7uu~|jjMm:7#X]/ا?Lw{,˜%7($( =m^`î pk.tbc|HE8jVOw N.ܡT}g;o)1Js4u-&wk˶9 7ڄ)!vN ya!ɕd 5@W T;YS\ a\Yv0 .p= Z~KwQ=^|.[I3t3?f3kӤ&μnn(7z@}bwbOyKwhϦŶVTrq__q (ҨzK}KC\ln.n:s Ρjowkxm\@` {bp׿#2oS7ڸͷ]]?zYvqU^7ڢwgW7o:i^]'ۤ7p߷ ӏ%oS.J~b=Ъ:9Mڣ8>xh~G*ڛPO>gnMݱiI`xj<ӧNIuǟoj*bpy+^~HNE:sͱQ5L]UoL#jCixpڤ1Մ>+]MyԜ C95Uka[+M/!N/wbǞF\BB{OR%Pϛ@R{.>3o@=o-Y{%B7 {/JY0)S6wkǗ8 %;!ֽٟh{(5Z1=yToӥVȷ9o6xܼhj1VϒBZk߭[ާWGqmey_}{U9m/6Ӧޫ>⵺d|>&cFnjK=TL=NfkђeZ45Ma=u7;e߼Yk=!_ޥ[j=gNJ- h:NY7_ֽ; sYo)>Sm}_nPÏdzʦ7Nי"\yY@ "0 &_eU;жU|[TksG_lWybZiw׻]߱ʼ2)"7O7:K e4Jm\NsV>zݶw+hY?}\qjvR͞+ϢE;j <.gm< |CY, hUx3O)w̵sNUª}Hwo}aLaxjCc>*_ `|iqq8̗gx"+/ÐwwrF-g[$y_xߚ5k'A*%ս?߃Lzu:h.tBy_ =ezSYF_~1ߑRot޻{IűrOmMo룗_1Tp7-쬏r^2xGˢMXZno%uV_YYY#Ap51sؾ78P*\Տ1կ~/px|UվC}eE[;8YY"J-VM 94FW`-"Ʈ1(`lG2[R#-߶ TG쓆C/jS|ˉ߾:{/3o/7x}יSަC1 2 ұV{d/ǻc)Ѓ q0/{x̐^Uc, _ T|G7eÑك  k/G}qX6;d0kvWǒs ZWݨ+bx*pCniZijw/TCMϿ&*TUZQ]s“!̂hNqaz޿QnJ s_W;Osj@#0 Lu #K'l <[ޥklY6^,mW!u+ "3fn}a1Tj3t>l+ Bo t4CM`YjSyUjdƲ,Phn4W-^g?ih-aʁr&GQPp8;=gwr䫤Z:: @սW/c敨ցt{r DzORm19Tu䤺Z'CzTmUV^sf޾:Too_)WX^ ~X-*oSyZrG%mԖQ6YEQz/mORhUaL-kۣP̈́6+0Dˊ#,k"g 0AxOQIѣa||>1zS[mѦ<ya}U|WU;{?d[ y?ϳ-U6 ጼMj>Ra^iZ-kSCGYOO<裏/Ѫs|,δ!(37LkYk}!yԬ31C0p >\O~?~ 8: w歵SL'uŜ9HwFqlљsy+e֬9uWDžV9Ϸi4sv+[,<3r(wwu|1kߴ{rll[,9|+_1giÆ "U HcǼQoΝ4\|yw˪{iWQVL慈(ɚ9Yq͌޽/|4͜1C1[ c2*v:D539+3 jB@`HYZh~hFfգ}UIxNz+#s4v #/01EٹfEsq#`&w mPGbc'`h#    P:E@@@@@@`h( ~@@@@uJGH     ]ď    .@C @@@@@H7l oүJ-_s8    !@Cn~\x1 q@@@@tep     @ 0Gi B@@@@ P0j"B@@@@d4YKt!    @h(M5!    @ P%C@@@@@ a4&@@@@@ Yh(M֒!]     0JFMD     4&kɐ.@@@@H &"@@@@HVJdH    $L҄Q    $ Z2 @@@@&@Ci¨@@@@Ud-҅     4aD    *b%K.??&kI Ξ=/|WrH L:UUUU صk`yveL@` ؟'b|{ŋ'9FƱ@AAF9xgeU, &O{׽$9I d (xv6c    )(SEb@@@@@`$h( UD@@@@1%@C*.    #!@CH&    )JTqX@@@@ JGB0@@@@@`L P:"    H$uC}ݧΑ ^۷o3 j,iDXݫg}6ӓo|Jp&'? g @Dq"D܉UD;q. VOO8/[o8:( <_JgΜ|p}8rB@]gK+b̉( @3    $^ě#    $ IV $@@@@/@Ci͉@@@@L$+    4Ĉ    I&@CiA@@@@ PxsbD@@@@$4     @h(M91"    @ PdBr@@@@@ 4&ޜ@@@@@ h(M!9     xJoN     d4&Y@@@@H 7'F@@@@H2J@H    $^ě#    $ IV $@@@@/@Ci͉@@@@L$+    4Ĉ    I&@CiA@@@@ PxsbD@@@@$4     @h(M91"    @ PdBr@@@@@ 4&ޜ@@@@@ h(M!9     xJoN     d4&Y@@@@H 7'F@@@@H2J@H    $^ě#    $ IV $@@@@/@Ci͉@@@@L$+    4Ę`GyDiii6m7Pff}n@ƣsE} ?&MǬ'@<;B$ q  vttS__}uV@Y4e;o_z I@@@ p³sI5z='J //'R|V/+VD:>@-`9і hُ ΣO"@Ci1k߰o~s@Xn6F<}ҥ@HHh P:%@ #3sLzDa' PİF0|SJ\ $LgQQ PCWӟt>^gBC&@=10:? /s)YJG֗ГD Rz$I @` tMa9bC ;@@ xvNB!I 4D6ZzлgJx@+iRF0&g 'SiP:5V3&D#I//2 6mN8J'\O Zw[  H D'l@NSƚ cH=|3dF.DA 1q  $IS$dh(t{'zN9+ 0yJ'O*#&BG@Ə,h(Wa@zB$ zbL:O}j $" !CM,J'VyOZ=|&Me˖Mx @FN'': #L  02<;+& _Fp>փ+{@/宻:̰@@Ygd.6)#8a#l@IDATz{߫%K$[H 8XzY L'B)H4FRa߸xu @rlذ!9B*@@!<4. EH@@@@@ ^Jz@@@@4"$      r=    yJ|@@@@Wx@@@@Ƽ c    +@Ci\    c^1_d@@@@H7}{z{315c@Ng%@{{~a|dĀ!ӣ}k|^aȥ$RggJ;qիYBm۶h&HG}_o͛7/iDB@H_Wu5hÆ ƐcH?;P:a ԩSd-\0FL'o=b0cM`ҤIz߯%"~7rLv<;߲%gG\      Q!q    JOY@@@@ C2@@@@?4$'     0DJe     0~h(?eIN@@@@@`4@@@@@`P:~ʒ     h("!    t%9A@@@@! P:D8.C@@@@#@C)Kr    Ctp\    GS@@@@(@C @@@@Ə ,      Q!q    JOY@@@@ C2@@@@?4$'     0DJe     0~h(?eIN@@@@@`4@@@@@`P:~ʒ     h("!    H?Y!' 0:.G'mfF@YCmVM3c@@d4J4 0AԴkr[=ʥt>D]ڷvۛӂF=u_69D@`\hUkoJ'sݭW-Pvyp4X @.uӜtI=t9;ÿ-.sNgOwϏXْ}FU@`La%MNQjzSSUOLe Э++;2͖~mٮefyĉC:yF{nvЪ`_#E~q" W@0HvGv̜)=W6-p$|WG)w+m\eUJ˕=I'ЦٮSuI]47\x:̗hWwaQQgap~#lR^oICKZUYzG#—*;Y e5=jOx}}Si(Ļ-/4&m5-PV@F\g~yvVǫzdr2'U]QĞȣ]A~7Q1R[Yxɓ*7j Hy"9}m$ ghg5ui׫C Z6.mϟ졞jnW}}NA? 5fCF^`Q+ɆzxGFR7bmޱ& -CBAı֥9z#izv#nM0%%[>OGC:h@WgD%Tkż5Q%$t}>Lf0,Cx quRs>vo 4JXﾫӿ>lzz]}>u.:{^3s*-MϺVX~>8Y:v07e(7w8_Góh3?/ۼϵG>Ku\8vT˞w'_٤ԹzB7Ohme~q^1]7t_Pev߽9fvK*(|I[WlWOkSN-[*&}!~s:k:gƔκF^9-tE cL쟟(%un PGk)6[9tu/TQ;L3ZKGU+z޲O:]f-[0t17wt}Z_]Buy"k}W]\=R_uٯ:gVG m>{:N/z{L{Q_-X*sw'6MOc/]ۯU,xێwo>ZWO׎뉒.pc^RMKzw3w4>oA!]mjxIo!ХF:كP\;t꼰zTZCf^+ϜNyY?iGw}VyDkb}q{mf e\zJO׺aeNir|-=mzSLby3D-ҐEY~iitF/{U^:+Sr>r]g "@ƞC{vVufO[^jzvެ?ghϭzHE[(A5/AưtR_mm n_E|?YO~\gA#tܬ՞rgz;r]׻;ry(cKۑoh?=>jW#-[+zg.7'tj+]K8\v)?k ׮g¨unP#JWlw\w!GP}h{}N:6#a&xwC=X.[l޽;K|sV,lݺWVV˩C>*wg$z}+qnV8_gyX͆v/[}?rYE+|E^W`˯Ugy|vpsݱRL\8OQ?3uc: ds҂XaۈCb_II+^_qISlS~H1}ՅQ U*EHgabp(ЀI+.73!RGT-kqLK6Ysj5C;5GSZqBהN =YPBқguk=އte>5W5ԇ:AT_f6ugڪOّv3?WWX?/z7PgM X:{άy?~XZLKCFV=W_uTu;)׋ ⫯dnV͎4E3W05;Ljcޡ7FXWt'BW:֮vlj9h q¦&6[ xp=l x޿myvFnR)UO8h]_}~#&)i"(La X?_mOCZvs576*壶9JG?XW'5FMpk]7፤ x ꊾ^s>vFyZkzO{ig55o;ޮ1uV]eAXXf>QPcmd$CK}^2/}mfʃ(H+Jџ]Hj) 4s)K~hmn$5Oa?HZTVc?vP\ tt&ޘ=@#$] 0n[0/7Y_u=c5K4wf&]Tܦg[hvm߰24|yZ+/zL..)׶=q\_H_T,ӋAEaX<]eP,vQi\Յ 9xjy=|5P7=q,{/6=w7zLe*+) ˛wyJ7g_Mv'Jl۶vzպ=7)LoVSviټLJ.rv!W@0Ô`x \H`D`9y3mgϿgHo:{(|*@<#U_W]¦wցѮ /wMg 9>t1e Ѥݴ3Ȫ7p)E>w⮧=E):) {3y(lڧ/2|`z#23$4l}BWj.W+!pOWXgxY?;{Lrc_AA5Up2.㺧 o#_;RYg(.tޓYCKC!eC'COPF{b 0j\i/T͐W#[EwZcܵM-r{H?^󎽣˘z.WPQ7ߍzd0.>3)3/K &sþ)ԑo+?l1Avd,&3lMæB3av)ۧd_uB?wkﷶ I1]_yO^1Zyw f Ǒ##QfU-j9v nXOVt)G9rLb'꺠Sg2k¦q ѡڃΡf]}.QUsZc{ᗛaahʕP)dmt]9Ǟ՘m~`]2 G_k}'g}CaYkaF05K*ř7 [Ҟ [ͮJ[̃?qk]tywBNt N_`/-k x9Dl j,;tRf>O5#%0_Vi邖hTfej`w𷳏ipwpeZC_IW]俛hz;L֡Ǖ+i(M3$LG7+J\o] eۓ2{;]j;+(W~l@CkoGz᯴nn8©gz0p-gjb {4ӳ7ju\ib ޱB?Їl~kFw>%+_~B UV[_юyhV{(Y!ѯMGP_u]0C׏~?K5>Ҳ_ݧtS$Гljԧ?|3y#oi 3:4fvvg)#W lF}-tl )}f;[V |axJj͹t{N6Sڕ;+[|vsg9iZGx2I#hkT#"r"@,tyv4^%^]kk$'2ܺmȽc%QZ;G~oq kۈDD$"܎ W#O70 ' t(h{~ξ B[/;2÷\A;+:tSBu -*d~ի'2+q6y^̇7_?B_o>Lg~~.nSo7/2/r~Gz^UѶ{}3ޙ<i'KdMvc!pq $@K3t=*S[iuݢ[_]8[g.齹.RզپSmghzg]urGj=שɎ&:f~ٶAK+dשƃFRkm^yf^NWWvA+IÃv8뫰:R3iܹVgrr;@'seϳ_{Z*^=?-߿.4 "lRn?}-noE͎|Un7#c|w`c@J$)π&>,X ڝOչ1o[}  Ny ui)Z\eKg+^+o]4hŝfEo;{B=Y {P@вϮ m5-izsGbVOw ϊSrݟ )":Nc|;*5 {{[M7ͽūo~JyQZNթU>0ݞ@` Lv}߼~q?_z c^i F_-?%[6=~Yi|]c ڸYٳI |usm-s9g 2Ž>YUoܣ=4ʭ騞9gt}8ʢLie+\kzOM{:xPwe;֩) B_gk\7 0\<;4P9 sYw&OŚo¹zJ,Ε}ϏqV[Vk l>7lUoW?lD៟0 Cys}Y`t]%4 ~꾕 c P:Oo+ 8KN\4yL'7Yޏv LN}U j vBjJǵk<{6<'mPR4> | >ҶtCm:N'=Ey*ա{tg-0)_8ݤ:jl}Q [M| ᘭiQ}/7=nf/HѶ{o ckAۛjMf? tBZNʙP>9u2#N; mVаOMCK|A{ۥll&o GiI=o-Y{4.;XC "ӡݟsǎj8hqW;VGmg~޻T^u^;M=QwܪzLdP/+ue'uBo.ӻtl-YQa<ywևtG'~Gqme!:#usz3#j :S϶mNשjh^~њӺwhmPn1tbyI2CW쵝ua=W/t4K~f]fqQa=K6{<i/)P;Ny^P7y\%ݪ}O6f1R6[jB'g1a 0xvWDRӺ֤޺W&^KOtL:gNJ-rU7KF_ZFo|JCe9޴x}Eme-ް<-77,kl{ˮy\x82oku_þk *o=V1t&_X|K=k/%v_p Ɓ=>1_7ƛwwrFcш8#[cwٷHw 3<":*ϭIoAWTy)>վ - ;::'} }M-;,/k<./7uf?uu~1ߑh~*sa6W,跭﬏RFd>_[62܂+#y&eC9vD[%<;G֏U>~$U'z|EC|gނP?FFeoluR{ s[4p{@Fٙ Kr t3c[pG>Zrm"xRvmݬ[K2zW +jy=Y˷T8Qeye_Ly{gցvq$}k*mp.tԹ9Lt^z{ٟ-#/c^\TcGu|S @wğP!PsٓOr ^w6o6\j!OCC/1wJ׫81GoD nTv1[\nX<;j/хa|w4;^m ,JZBU1fDWrpgH' bYoi,Tmsڐx`&ݱ=4)&]>mZ5$Бͷ&vM]wTLzmNf;=gwjOJ*)-H %GH@`\ -D$d[<(Cү^mai;#c9jVMQr3nNUJTLOֺ<ۋspjoH_O޾QDMG4ODGΏ]cƹYuu]ޫk&CR[(i(,PmK,ތMj>RhAY߲~VD[$bXr:[jUVo7tm\֛EƝ΃/R9h7xߐsףa_Nz~O}nKL/*V 靗7PzyUYZ ?_{f8fs޴y,C~Ԭhu]~PN7/;Meյ5Y|@#mwa}ÑjP/3j|_B !yN9&[LV7ouqt-7֛yZ'Pcc}$N%IW TFF:ޠ~ޫ5koOH_W4k,mذ!! w$W=j;ըߚ Njrf-:gz=^*?+yY3I+} [SODӯBs23/ic9gzG|5k23}UuruҦ10;.X\2M3gP PH[鸠3fFuw{,ovpqXqO9Lyyiwh~T}sf?jyӪc064A6p(1-qiv>ԤcZLHtĘsnybL!0]j:A3g^٦Qa%!/+{ۀs۾TRHZoff.[W6:N̜\ N+%]Ygb{HzW)5? ff 3/i+󙝕ZfdfدH3㬯Ms| :o&'De5@&0{!!7n,Yb(W5305AP:̠ [󗬏!qDo qN6XC0W( I)HR J &QB%˴xGVyjoӽot덦y!kΙ-|%hو@ W ':@pp/`c P:|B8ݳZU%ֶf9X/8xP_s93Ra:ךv1XܼYEaa$@"Cq#@C)J2ү@JVoc~N ӣ!u߲  @H*d $^{ěcR $}(2Lb&@K{Ή.B@Q*K4! 0q8eMNb`@@@@4NR'         LDJ'bg@@@@pP`@@@@& 3    8h(up    Q҉X@@@@4:8@@@@@(@CD,u    Jl     Dt":yF@@@@ 6@@@@@`" P:K<#    CR     0h(N@@@@@!@C @@@@4NR'         LDJ'bg@@@@p8@ F3gΨX1^i h}{뮻-!SN֭[.iH@K`׮]*//Ɓ¸?;P:{d2?N 0,%%%*(( yf]~!+ƹw]{gkk>o~:qDp OѲ>Mn! SM@@@H.UVK/ >c[ <_O4I+FUQ?03gTff{7    G?ouocXCC *@Ci|^^"lҥ@@@ӧO>ξ-gE"c'LLJܯڈSx    .`=G[u]ɓ'wX$-o1bʬ=    @l'd,/Vmf: J O)V84&qY[N2şB'M"i 1 X]vՓ[/^ nGiL Sj}9}lAp>LJ2?iICINO~Qq@G>OhѢEǵ 0Nh(M₵)4iW5  c]zYaiJCi$! p r-tD '@CiHxbYv1?iICY[o8ު!q,  H X󔦤n(Ƹ I^Vk$O)C@``?^s/V=gaʂ @`%KTc\$/|PmmmIJ @l) -B@/`Mon\B$/=ǂ xpSj=XCX@@^dMsǂD4 @@`2?Q0   BA`q* /I7%@@_ @!`S:eʔO`@@FQQ'jٻ6;__vb\4]'ŢMJS$Ҥĥ !U}i".Ɋۤw}pE(O:bE,[:(--q 6`nTޞIǶ,yHsf9gfPUڤI꧀(@ P@~ 4sC Pr u]7%BR(@ P->>(@ P +J?K/ܹs ,(@ P(0Q:sK P(}cОvo <,(@ P(0&X P&7 | _Yg)@ P(@`Gi3H$@..\l۠2U|G"9x2 Q^u}.Z Wu'OB`LȲ4MW_}^{-,YfJN B}ݗq@iqu P`Xg0zA 0fώ4^{5#<_vHL9YQd!_w}n5Fgi.vnۃe%˅SG_s|+ew.rF\2(@ P OG=ر?!mn@cɂ s1]V\U,CTͣh|+iFV-Mau"m`SDQ.)?}ڃ+I7z'mg~צܹSݻw=A;U,u9EcqzqL |8Fhd?R$+B@r|mIwe=#okL+- d+Pms!r.0ZvsLB*/҇DۦTa$nH:L^Z$yzq0ɧoZ^NC'̥$#`ڼJ4(G]F{5٧H*-`hR(yt{N@fO}`8¾[m0'H-_^JnXԙ/3Sޓp pNy6]z͗xc(j[{̷Goe; !# \" Im5ㅉt tirW;GyʹITv[-V2!&+>YPz޲n :ܖ3*kt;jqc:58N=Y+@@8M1Eh1CMPFSܒ|"h\6SUMc~7#mz[4k]j=ż_mf2AO^g[ۉ"U>Tj.Gy yaw0L&zG[^7[2܄c! s4vvA8x.ۅ'%X4KmzF8 Ѣ(_90ukS%Qvoea&;1O,qR{?u;فNM3`z6iG=:#VӦ',`foeMgOJP-wܦ>MގNͺ];aTw?l//7coNQ^ ŗtpG|)2~&_hLDxFciLg,gm>nL5~8O0p|+rd&Ř\"sx ^fuz6 cc-R4c2aS'WrPve\(0ȳ꥖B}bSmnq#_k q|Nl*)_G֢0Q=vX㘞2%[ڶv9tіg> P Ncslء^cζe]| &ݴ5v)wh+7.z_ jjv`S<onمxaquRWE8x$7ivqv؉,bh.E3Qa3_jș:7HV3]QaCTcNn9kFֻ#qZ5:[Hc`GiԷUsW%^=+V@^MbM6}Smf6oތ|v\P[, گ#3$g}_Zb_Ljr nIJ4\˖݂j%bX'vVˍF 6sLxU{ U6l#&:U'[[ y-k@k @k#.#v=NӸzr](@ L2S8d#eI QnCWjх٫MEw̋Ƽ7&c_k.[9Xs@ls•8Tw.o a zy7yy Տǡ :SRi7.vׯ6εf9dACS+rF9zy4>Y˒^+̻j7."yY6blV^/s3Y7Y{| eza~WF]I-_(0*qieG.. !;r_| ܾrrzA1x'ЪdQ>"BP154w/$ǰ%çb+f4mFzۈkN/ .p5/d+*jR%q$ybecvٷ?^%Y aOj:$ kţkbyT`DZ2s*`dv$?!g5oCbf,ZӪl n,ĖCX3!`BپCϡ+8M^M+Qrd~v, Ǭy xMٍq(ernD⒤XWΧ5jnʹAwYR|ܭ]97RY%ݾr1S5jG>wWAr'{wh4o9I[e l[bW;Kssxqwǩ7dyu9~~u*xdhڴxHO<-v]Fؗ|NSkش>x 5XwY){ufẻn'UqNՎk?>[LH&q+C8>p=n/]?zȑ۝ζ;tvȫë'_(3j>]]P*uȓqJMF|1ɘYgzqR3oU-oÊGȣFПΝY֤'bJuXUؗo2964l]rP{${/S_+H6 /GAgS?}\$|]jkʮg)@ L@ܨ(GRȞΉXy|/;0Ǿf>z~5r:IP h=tSvF1|Ђ+oɹS(ˉ OyJU}T<'4~,Wp֣IYd׵9u(H?oVݽJC?R:Jz`6W%﬏e+rw"EV4dE.S {r D P`&O8xIk5dDnUY~^ Z'݉ w9{21 ,>ԷeVaHD=ؤq;vWm7bF LD{s]y64m_0i~* M =|uŐI~)j3]2 =oc1K#z.;Ion|@^3wћn#ȇ!U h+WoXdO;nXons&D`=YN:|yb,:f1$;W]:g2yA𢡄QTU46?V \rly{3E/xoXOMh_F :4RmzHtM K~S^4{% u J/[r.ٝ oBX7V6&%5Y Pv,h[k%4E`WVi3Uwl]֠TL4˻N][d<~Sult̸sHl*g@ba cK~Z=*:Eh |rU+MlT}߼D^ilZT T/Iª5Ss`.g#oȎe9zȫL3:{|)q5r6SRqk!!rzrO Uq%Jv)z)3 rsi˞"|}e^m*-+}-k\:o3jU峒>sW̫dL]͇FV,Sr$g[fjfl4:I햤>z!HNbs"کlӿik˹Rn{ QWD΢rTVYHSh_fz̋PK8x.7v_-?is E|y^Ś9MX}{vsƴcbdPOq{:K<7LpnCHStʻvxl֋,]*,qq~N33[>N3ǾPҺԞ~KRKǞ]LvrK;YlmY-ZW m3z5JoůuI9{0ԎgcbW-6JM aǣO5E5ط}e,?8v𑫡WOk5~?ULqVG^b N3ᙰU-JGi&G[q0q129 P9E8x.weۆv|U߃ _T?o 1͞fL}x/<{B,܃F_?Şґ벣tuԯ_m-ѫGG_Ol|Q3cg0rͶa6ķ [@>,o P(W{'C=4yj؄)\Fu%wl|Szk ON7cp4}O4V4Ύ E[ky pBޜey_`|8낑Y]@FN{"_!Y-jYuM"Fk[@D !:'!-W}jht 1%bGF@KO͡k˺jqiXvv)ݛ1ymR|*NF+{:0${vlM^5" c+me?[aٿZ!chPn'-p@,꜖ ]aKm2w5zh$ ujS uPW@gaMѧ%1_mzAS &}˟p\]Z)EE_eʃ#,Pt zEG9D Ԛ/-o]S[7W} tDma)#dMc=7c^;6h:DȿI{l$(ԶsV,Ȳ]UW*JŒ..)-?&T _NKe;U뮆]ޣ^^FkI0 ;R6:jc)=1YHymnt5ReOO<<(҄ 49Ro%EE]BGpD{l%)|_ƒx<ܑD9nn@18*'j,M:Цtk-)s22FlNhdG.*,|b*πe'z{M}qR՝U|W;|)'k2:CfgL 휲}d)vHL3Qξ]M<&&k4} RŴ@ĭM$'}}mH))V^+S:4zq:GH v68_| Ig#dy^_l52[[kh,ewCdT9vm" ŷn,fwmg8yy{%ڭ<޼Ɋ/|% kYG' rT5w:C^7/]Q˷Q߁Ez\A}[*h(>RԶ<>'ll!d4g[cGVyicd^nb:4x3442(C2JoP'!_Ry |YPFSjb{K{|d驎 >m/؟Y(@ E8x˺]M<&&"k1D%LǡT1m11a2ٱkg݇//WGzXLҮMܪC5ӯO` >ƗyX 0܊|ojdֿ:> X:|c=cK.f]MIn}7ȧ )ڀc!zZݒbr[ *gҜʕ+Z. slQ]'o'm-ELM(^8-cCaaKwfm 1X+_ܩģh,7=&%$Z<)veG%?ҍD6DgS, T^9M-IG?6W]lӛ %o[wȋ_:2)2;|zpU|AؼYsCErH*XSn7y';rX+J|?8|2&*K~ߚh昨y&Jo;.2˃vq|>b!!O*]A RĶwUhHRpچ> Guqf(0T4/2DgK]!R1'󌃙 d˜G>wCYYt8prN|{Wz3K䞋g\˯l㚥v֯ "cƬYt+$H+wm(KP^ CPX$.+$5w̛?߉Ҏ+Rq\`׮]7ood4RNOfM C! ,i02xQT濸xf]z)S"W!yEa=#Hs(79P?u{F:ҙs1g<6'KQG`?zRN,R-G9'Ud DJyR~ԓŴacb/Nts:S){{ ! Ds`Q(b|Nyn1J#i&lJ\.S*]._YU-roNU|7UXn P9(ByJmFd,XT\l"._$eNU&3^EM2+N}&sS+0YlJ1lw[6OvO%XTa%&LQ6[($So(f(@ P(@ Pgva(@ P(@ P(@q`G0s'(@ P(@ P@> 4F P(@ P(@ ;JDž;(@ P(@ PY|t7 P(@ P(@ P`\Q:. (@ P(@ P((üQ(@ P(@ P"qaN(@ P(@ P(@|`Gi>(@ P(@ Pv 3wB P(@ P(@ ;J0o(@ P(@ Pt\ P(@ P(@ P QGy(@ P(@ PE̝P(@ P(@ P,|>:(@ P(@ P(0.(f(@ P(@ Pgva(@ P(@ P(@q`G0s'(@ P(@ P@> 4F P(@ P(@ ;JDž;(@ P(@ PY|t7 P(@ P(@ P`\Q:. (@ P(@ P((üQ(@ P(@ P"P4.{)a{V*C@q&Vqpbw P`t3ΉkQ`,XgK]n 0]vIu]/~ke P`,Ν;.m P`ap(W3`f Sy%8`GinBS Cq0#KA P[MMMBh"/kQ^^"fXguV 2=(@ P(@ P`o?}(P(-[ .g\vex1G(@Ü 8(@ P(0E֮]$z:Ky;sHr+zrk(@ P(@1#W&ɬY`ۓ(@ P`vķ)@ P(@ P$0|hMړ1J9Q@(Mߌ)(@ P(@ P*pM7%ҥKuJ_(@(MI7(@ P(@ P)p7Cur-֗L P@ VVV𨀋ϢQȩ@^uj%kPP(@ P` h "R as 7X_2(@ P,SOʓ|Y4 P` _JJJ֬Y_(@ LE뮻uI{mŊ֗L P@ hw^'-c̢Q'w)'n3D P"W~#Iꪫ8>i _(@ ?akʻ3 ,(@ ]GiqJ9>in)?(@U:N)'U}D P(@ P ](SI=\ ]:N)'-#Q(@ Pc-qJ9>X} PSr|xg P(@ P 2 (@ 䋀66}C-ܒ/b>(@ P(@ LJ($qJ9>\1(087p8쑻(@ P(PyQ]s`ڵϒQ)X"-1)(@ P(@ +6N__s\f(@ L_ Q\\ G0T+v%_b)(0 ?rRc-0c lذc SY |;z&ΓH1(s!*(ͯP(@ P(@ P @.)@ P(@ P(@`Gi~(@ P(@ PvN:wI P(@ P(@ ;Jx07(@ P(@ PtйK P(@ P(@ P Q_ǃ(@ P(@ P&@]R(@ P(@ P%: (@ P(@ P(0(t(@ P(@ P/v`n(@ P(@ P(@ `Gs(@ P(@ P@~ 4sC P(@ P(@ L;J'(@ P(@ PKu< P(@ P(@ P`Q:%(@ P(@ P(_(ͯP(@ P(@ P @.)@ P(@ P(@`Gi~(@ P(@ PvN:wI P(@ P(@ ;Jx07(@ P(@ PtйK P(@ P(@ P Q_ǃ(@ P(@ P&@]R(@ P(@ P%: (@ P(@ P(0(t(@ P(@ P/sOg{1)%3(@ H`Zgh (@ Pd`Gdv}Usn<عm>"mp8?6g7W)kh voNx#}7)?*xnn4T&sJy]+OG5 x;w.][+BH2Fj*(@ P`r qjܚ{ u/YOBc? QIƴo|[oK*>[{bYOoˠrrKdƑ{v !j]ywT"g_wwQ&}sǃͨTb8\.ڿ?=ǷbsYwFH~6FsjǺ)@ L@!ӏY!>kT{\_c7QYIѶӛmKiݑڑw5(_BNOi_LbukC2Xok8&Öe fqFyb4a3g6rXwкW.O%=/_Ԍ4/iIi٘-h44ufZ޴A@$Nܖfی9x}0PW/]&mo5c%flb ?W(@ P /Jm~ːb[V:+b%l$Q۞4jtb`;6YWmو9A,jof4x\HRH\tRo}#ld*:#@غ<0 (@ Fqm_GzT؝8+܀BI*dYOڬ P`|rt{n|8R'6YZ,{~،<Dko8-CO rm~ zJ*ifGKټ -?*C8}ޢn@_:{_gkދ*f_ws^|v+Yu3w@ANj5w`ebh^y۠\n'*ο+v߆*Fۏx!*^.'{O/p9̽l%,elcM+^k(*Y!HqnoNʼnW T+à|h6[9t'^=Wega駮S;`[}eS/(@(:8n QSOx*zY!b}N ߩf\ua4۰e%rtxסFeb7?7BI#:{}<,= ;j ܿ.^e {ƄWݵp߱3}84~rU47߿s^3 | Uk\ASh~?W¶`-?v hs*qwbXΜ=}qDDŽq{~ļj'^~{msۥ׭$4='wPJRey9d±'U;M&;;(ŠEzHa'x]B\y <2W6JYo>_|( \ˑm;-<g`;ljt,'q;T>.5Įuw'>#6jt8qͿl)R9eObڛIxoVߋXs{i LC+Q~h'Gj}"eH(ӊ?@ֱ6y*_@|6w.q%IDATM/bDESO"ݾ{=yk.r{W[Jŗ[DOmw5VD}z#Vi۷jmxz-~~e-]/߯ XnT6/E(3hK2$p(ɮ6# p`|BSL} b+zmS~&ZaOnuM2@.ʮddrs 0+o%VGkO2lMS@@8Mq.=M [cW({$#P>cXeǔ8XgKnu4 5j|"h%mtF^=~p=٦ ZZ:MAKed}%RMu^ᩮ.KjzGx<^Ѩ5O:d0C%[ĭіWGuj;=#ywz{k!#^l"G:!U|F AcUVδl=BީS-oz{WVi|cSn5e/gXEt[}=c䨍tfKvi8BL6Fm phHlFKS ;CZxᏏ3#|#U!Qtfj㹩cY?@6sfCQ4Hd%Zo7Ωkp0GԹ-7v\"mڒXGvX1FK~p|1ʭL歏|ξ]'xJQkIfL>i7_3hkmЧS>ֿWRNZoϢ}-D:<lK }Fՙ,qdJ^he޳k 9{ L8`n߮]4jѼ؁]U˥q2֤-7#Y6=m2=r c !o翱 U7onYKźz[۰ڶ`W6{ǂ[ƣmU[fmmceB| 79e45::nOK]雐W\S oZT;O / R'>yq[ܨn@.aΜ j/8w܆M^y=T[!y-cԹ} h hmץqHseW% PSA,^{1Б=~|r}l#qG|\رq5)Wxtm[O9UI(+bd2M~lqƙwM/J~vJo9āAXeN&?ަnD.9+"N~u>mJ;|8[޺'MLkSM/oNxv7Zc7!Ԩ6sab]Zd}U+ߵxR,$v6nrW'OJr,q/lzR݁[sR- P`i_"VgܾfP{;#G㩽঵@ۯ5mjΆ. B5z !lZ*.iI]t|إ&y)gv]q 䭀֥yhvtW:ָrnS,5Yn7?ŴE=m6Մ` ɫ/LW}xY>QԤsWZψi%\2\9[eukOz_W+|Z(oO5rZ!/7^Y3yسJW&e:cb| :c{[.uS#7ؿKZ?@0sxrEiS;gOĻEXd3Jc31# ]"z+o7+Vcۆfa]mY Vؓa\~#7:~prz"{@Uv%g\(09XZm;Dof:Vt~iדىօp~fS|زv >h>)qu#F4x';EX$؟Ν$ƌzG[ZGqwwĶS DCG;uyU=ٱ1q˕uNu,'.>}_+{~]HޑslO?]Ae|EMg=jd׵9=rF.êbPPp]!d%JG\g$w-RXlջBw.[`)'UaN`~Ȭ}buGflcukyk݇_l"8mԲ+kD*Yrqdnk1\;VtoԓgwlbmbR @No `':i3N>8uf45vЋ_jc摷s;b:w|p;͗Wv'-x0Իx䍞F2?s/ҥ1|On"K2Gu>$M$;_F8' ܦl{jg?l:e+n?g)@ LRs;)´sHn)(W$geli]ٲ'mq߿j4:`ۜ?e^'I^]IYǏ4K.3BV"% X\ёan+G?~"L\7dx[%Rm55昽ڲu K^q\8τCtyPn@X=q}>,{t\>bSPuӴ $V(02i_˨0vZXaZգo_0_W>TQKlxH&z v.l\kCk(ߦ&LUtjiCeE77^//$̕sD[bPCtu*3p˱.=jmlJۊu8xz]@B\+8rn[Tiڧ6;WFy;8ʋ,;=4?~ }qjc)ejTYRq+î]?guJRW6`*=뷨1W9x/~Z5 ݋JKf˖+OZlH}7JO:L6帣Ŗ6Sl14GIա: N ȓv p.Ŧgȸat20U踩c\ne0Vg޾X=\U0>(ryzqbOfeA D6z=6^U߁hZOe;-ƚY(yeG~bgyv[ʥ^/c>UeGc8 \ʲmݺO.S(Lk||-%yrLP6 GS/J\ؿ69t-º͏oŘZ)n9xwM+&~[ch~->j.5nPk""rʳ~Bм[x/a"kP'qLg;fe`ڶO3Of4ɇ`P?{s+U AsƭJ8fϚk۾2/efǎ>r5tkz}8ڇdwϟ{?Eܻ&+JAng3aZ𮑶X|' hk渍TW(0Erվ~Φ}X.Ӿk<o6ݶ⻸E<gEu4:A 2tu.?ݱGvoJ!; ىR{ocb̜TF\o0<3X;V.N@V5:EpW>h) qcv5UNM>BKlYg (3"E{K>K D6x@}uE[U}hܞIDkU>Sl`epm-~!nɗOwFAm?^e]- _U;2mFcd.\- zmc“uu{3f¢ѭ#z²lz!/2xe7r3QsNT޹_ P`(aZ/:CwKʘPgcWZ\ $Ē.Q)Z"cubM._OHO.Klyb`$nhkCu8eyRSujS̋;/îd]J lm~\,Mp?>Q[{]9udaر픺|脥ޑW.&JUa|4ߞH}G,Q>"a<~2&!ҎM+Z6H{Y{ O*O lMY}=)XeZ~Bٶ`BwMBqQ ڂ2砍*4,oBoS []juT=>d%أ>\qGdzC]Zb5"(XkTN;LscJZnB^[w$~BX]׃TTk]Gm[ h>]jRiuZHSI/_}0VkOKdMQN6eGivkmx& BEk&>uNhQIhFʜ[&kUoAe7e}fNXιc P`,ƪ㡣܉ew]lH۵:d]hKs=$Tct + ۳yF@3eψ#V/qId~Ol˼NyW}6#Ԕ$Zf:NNҁO22lvQOmJM;qa b XHiie'*S8nrׁ;h'S%ñ㟱Dz2OS[`\cѾ-X}ZdU kMxeU2XOnQMM~y2t/M'#߰a>I-WDszu$5ek'b\c\n>r0 (O:oz?:SکRTUܹ\yż|fٵvY.m ].4xm;D^vώ8PI^/x<` +eQ'_5~_(PtiP3r:p_!lz"_=رm5ZgB];CFcom<*aam" ŷno UlkaeSE-S~TeWnC'1@OSɜs*)2[ݸ=aْ[0Mj)Sjb{K{|dᔟ8}Z3GOlJY P`2 EZ:m_#X=L+M5.ZxȪ|lڵlcw헡>WT}T}h%צ]o}jƱ6aK|L@;GO4Xn/ L]4txow-v;z_}# kf͆Zˮza)W#36z^jJ8ۤ+;mN-J2\DOk,$gh櫕R_QdN%")fks:y{lˮaNPƹ[ P`L P>kCNcB!ÔX/Vi cmy׈2]4w-sry+qI^syD_ߌ6O6u)l ѥ1V"R7teFcu{ &l:62D{qt=LtOn ؐ07mPlU(4Дnlӛ?'͟&7)ēIr{.Ͼ !M~g?n7rҝ]$5{!kB\/6p}+>G:y @\2Uo֏({ԭtld<-D\zF~X\: zKnD\e~#Caezӽiͧ%}VKg } ZW[*Ύ@@m_z%.;W/SO\u'}9Ffysx-8y󬙧z3zcGm%zh(ܔk\|sDzY'Nh9W>P\ݡEn#S5ΠOJ>Y]wHw\dDW_ѡ܍9~@<:!տD}tHvojK?zSQIp K0 MΈϺɴ.liPPשAw{/.ׯ_k:0^ZzV)Z ~VtQ5;c;sSV~K6)ԄL߾$oo}^"#՝I_"/Cv,J]B;:`yF5kd 8۬vYalRwf$rG[cr[lZufȷk80ؾqqy8}~-(=JIswRbuU1b V/Z)mJK.y@ܤ}&cLLco"icEIS-+V[-[[CWsCJ^"jq0Sr2$ν]B Cm- KC$t˿O}՗)æ^K9qnئ%hKMؕ]@j'OJ6~Z9hħu]c_ABB~Û;J)R?sm_cHvN,(bEӶ2 p2׌wTJF ^- w[T8.8Kz ⠶)y:ϙ?i(Ҩ[c>[eT 8(P:+>jh&]U$]/;Iw' f: -0{4meq oFd,TՎ9(em!$# PguVj"@.4xn<Z//AkFiDwtIkM/o,&`D蕃lSa>[  PXOt@KbjSvO;tmm䷟ʀ ݰn={lvPϧ"  E VMņ @ZAÅ-H_Γ^ߚt %.g++vd @ ؃BDߒ$M3K~IH\%ۯd^ֿ=Zmc @ V}S@4HE |/1 ;|4,sJרAR  P@ R&5HV[*e/ 6y  @muGpTm$8_,E@ eV&?l.g  _:  @~IE@@@@#@;uMI@@@@@ @C2    xG@wꚒ"    A@d@@@@R5%E@@@@R      ީkJ    @@@@@;JSה@@@@ J 0$#    wz))    `HF@@@@(N]SR@@@@0(5     Pꝺ     ` Pj!@@@@#@;uMI@@@@@ @C2    xG@wꚒ"    AJonn'O6!-011!> G ܺuK=*---.9E XW+W2k2vbSf' 0vvRmg^V$a255UT@GVZ傜E\vV< @U숀;k= 0vZuNҁRd     (CvzIENDB`DBI/vignettes/DBI-advanced.Rmd0000644000176200001440000002657714552712323015512 0ustar liggesusers--- title: "Advanced DBI Usage" author: "James Wondrasek, Kirill Müller" date: "17/03/2020" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{Advanced DBI Usage} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r setup, include=FALSE} library(knitr) opts_chunk$set( echo = TRUE, error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5"), # FIXME: Bring back when relational.fit clone is up eval = FALSE ) knit_print.data.frame <- function(x, ...) { print(head(x, 3)) if (nrow(x) > 3) { cat("Showing 3 out of", nrow(x), "rows.\n") } invisible(x) } registerS3method("knit_print", "data.frame", "knit_print.data.frame") ``` ## Who this tutorial is for This tutorial is for you if you need to use a richer set of SQL features such as data manipulation queries, parameterized queries and queries performed using SQL's transaction features. See `vignette("DBI", package = "DBI")` for a more basic tutorial covering connecting to DBMS and executing simple queries. ## How to run more complex queries using DBI `dbGetQuery()` works by calling a number of functions behind the scenes. If you need more control you can manually build your own query, retrieve results at your selected rate, and release the resources involved by calling the same functions. These functions are: - `dbSendQuery()` sends the SQL query to the DBMS and returns a `result` object. The query is limited to `SELECT` statements. If you want to send other statements, such as `INSERT`, `UPDATE`, `DELETE`, etc, use `dbSendStatement()`. - `dbFetch()` is called with the `result` object returned by `dbSendQuery()`. It also accepts an argument specifying the number of rows to be returned, e.g. `n = 200`. If you want to fetch all the rows, use `n = -1`. - `dbClearResult()` is called when you have finished retrieving data. It releases the resources associated with the `result` object. ```{r} library(DBI) con <- dbConnect( RMariaDB::MariaDB(), host = "relational.fit.cvut.cz", port = 3306, username = "guest", password = "relational", dbname = "sakila" ) res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = 'G'") df <- dbFetch(res, n = 3) dbClearResult(res) head(df, 3) ``` ## How to read part of a table from a database If your dataset is large you may want to fetch a limited number of rows at a time. As demonstrated below, this can be accomplished by using a while loop where the function `dbHasCompleted()` is used to check for ongoing rows, and `dbFetch()` is used with the `n = X` argument, specifying how many rows to return on each iteration. Again, we call `dbClearResult()` at the end to release resources. ```{r} res <- dbSendQuery(con, "SELECT * FROM film") while (!dbHasCompleted(res)) { chunk <- dbFetch(res, n = 300) print(nrow(chunk)) } dbClearResult(res) ``` ## How to use parameters (safely) in SQL queries `dbSendQuery()` can be used with parameterized SQL queries. DBI supports two ways to avoid SQL injection attacks from user-supplied parameters: quoting and parameterized queries. ### Quoting Quoting of parameter values is performed using the function `dbQuoteLiteral()`, which supports many R data types, including date and time.[^quote-string] [^quote-string]: An older method, `dbQuoteString()`, was used to quote string values only. The `dbQuoteLiteral()` method forwards to `dbQuoteString()` for character vectors. Users do not need to distinguish between these two cases. In cases where users may be supplying table or column names to use in the query for data retrieval, those names or identifiers must also be escaped. As there may be DBMS-specific rules for escaping these identifiers, DBI provides the function `dbQuoteIdentifier()` to generate a safe string representation. ```{r quote} safe_id <- dbQuoteIdentifier(con, "rating") safe_param <- dbQuoteLiteral(con, "G") query <- paste0("SELECT title, ", safe_id, " FROM film WHERE ", safe_id, " = ", safe_param) query res <- dbSendQuery(con, query) dbFetch(res) dbClearResult(res) ``` The same result can be had by using `glue::glue_sql()`. It performs the same safe quoting on any variable or R statement appearing between braces within the query string. ```{r} id <- "rating" param <- "G" query <- glue::glue_sql("SELECT title, {`id`} FROM film WHERE {`id`} = {param}", .con = con) df <- dbGetQuery(con, query) head(df, 3) ``` ### Parameterized queries Rather than performing the parameter substitution ourselves, we can push it to the DBMS by including placeholders in the query. Different DBMS use different placeholder schemes, DBI passes through the SQL expression unchanged. MariaDB uses a question mark (?) as placeholder and expects an unnamed list of parameter values. Other DBMS may use named parameters. We recommend consulting the documentation for the DBMS you are using. As an example, a web search for "mariadb parameterized queries" leads to the documentation for the [`PREPARE` statement](https://mariadb.com/kb/en/prepare-statement/) which mentions: > Within the statement, "?" characters can be used as parameter markers to indicate where data values are to be bound to the query later when you execute it. Currently there is no list of which placeholder scheme a particular DBMS supports. Placeholders only work for literal values. Other parts of the query, e.g. table or column identifiers, still need to be quoted with `dbQuoteIdentifier()`. For a single set of parameters, the `params` argument to `dbSendQuery()` or `dbGetQuery()` can be used. It takes a list and its members are substituted in order for the placeholders within the query. ```{r params} params <- list("G") safe_id <- dbQuoteIdentifier(con, "rating") query <- paste0("SELECT * FROM film WHERE ", safe_id, " = ?") query res <- dbSendQuery(con, query, params = params) dbFetch(res, n = 3) dbClearResult(res) ``` Below is an example query using multiple placeholders with the MariaDB driver. The placeholders are supplied as a list of values ordered to match the position of the placeholders in the query. ```{r multi-param} q_params <- list("G", 90) query <- "SELECT title, rating, length FROM film WHERE rating = ? AND length >= ?" res <- dbSendQuery(con, query, params = q_params) dbFetch(res, n = 3) dbClearResult(res) ``` When you wish to perform the same query with different sets of parameter values, `dbBind()` is used. There are two ways to use `dbBind()`. Firstly, it can be used multiple times with same query. ```{r dbbind} res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = ?") dbBind(res, list("G")) dbFetch(res, n = 3) dbBind(res, list("PG")) dbFetch(res, n = 3) dbClearResult(res) ``` Secondly, `dbBind()` can be used to execute the same statement with multiple values at once. ```{r bind_quotestring} res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = ?") dbBind(res, list(c("G", "PG"))) dbFetch(res, n = 3) dbClearResult(res) ``` Use a list of vectors if your query has multiple parameters: ```{r bind-multi-param} q_params <- list(c("G", "PG"), c(90, 120)) query <- "SELECT title, rating, length FROM film WHERE rating = ? AND length >= ?" res <- dbSendQuery(con, query, params = q_params) dbFetch(res, n = 3) dbClearResult(res) ``` Always disconnect from the database when done. ```{r disconnect} dbDisconnect(con) ``` ## SQL data manipulation - UPDATE, DELETE and friends For SQL queries that affect the underlying database, such as UPDATE, DELETE, INSERT INTO, and DROP TABLE, DBI provides two functions. `dbExecute()` passes the SQL statement to the DBMS for execution and returns the number of rows affected. `dbSendStatement()` performs in the same manner, but returns a result object. Call `dbGetRowsAffected()` with the result object to get the count of the affected rows. You then need to call `dbClearResult()` with the result object afterwards to release resources. In actuality, `dbExecute()` is a convenience function that calls `dbSendStatement()`, `dbGetRowsAffected()`, and `dbClearResult()`. You can use these functions if you need more control over the query process. The subsequent examples use an in-memory SQL database provided by `RSQLite::SQLite()`, because the remote database used in above examples does not allow writing. ```{r} library(DBI) con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cars", head(cars, 3)) dbExecute( con, "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" ) rs <- dbSendStatement( con, "INSERT INTO cars (speed, dist) VALUES (4, 4), (5, 5), (6, 6)" ) dbGetRowsAffected(rs) dbClearResult(rs) dbReadTable(con, "cars") ``` Do not forget to disconnect from the database at the end. ```{r} dbDisconnect(con) ``` ## SQL transactions with DBI DBI allows you to group multiple queries into a single atomic transaction. Transactions are initiated with `dbBegin()` and either made persistent with `dbCommit()` or undone with `dbRollback()`. The example below updates two tables and ensures that either both tables are updated, or no changes are persisted to the database and an error is thrown. ```{r} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cash", data.frame(amount = 100)) dbWriteTable(con, "account", data.frame(amount = 2000)) withdraw <- function(amount) { # All operations must be carried out as logical unit: dbExecute(con, "UPDATE cash SET amount = amount + ?", list(amount)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(amount)) } withdraw_transacted <- function(amount) { # Ensure atomicity dbBegin(con) # Perform operation withdraw(amount) # Persist results dbCommit(con) } withdraw_transacted(300) ``` After withdrawing 300 credits, the cash is increased and the account is decreased by this amount. The transaction ensures that either both operations succeed, or no change occurs. ```{r} dbReadTable(con, "cash") dbReadTable(con, "account") ``` We can roll back changes manually if necessary. Do not forget to call `dbRollback()` in case of error, otherwise the transaction remains open indefinitely. ```{r} withdraw_if_funds <- function(amount) { dbBegin(con) withdraw(amount) # Rolling back after detecting negative value on account: if (dbReadTable(con, "account")$amount >= 0) { dbCommit(con) TRUE } else { message("Insufficient funds") dbRollback(con) FALSE } } withdraw_if_funds(5000) dbReadTable(con, "cash") dbReadTable(con, "account") ``` `dbWithTransaction()` simplifies using transactions. Pass it a connection and the code you want to run as a transaction. It will execute the code and call `dbCommit()` on success and call `dbRollback()` if an error is thrown. ```{r error = TRUE} withdraw_safely <- function(amount) { dbWithTransaction(con, { withdraw(amount) if (dbReadTable(con, "account")$amount < 0) { stop("Error: insufficient funds", call. = FALSE) } }) } withdraw_safely(5000) dbReadTable(con, "cash") dbReadTable(con, "account") ``` As usual, do not forget to disconnect from the database when done. ```{r} dbDisconnect(con) ``` ## Conclusion That concludes the major features of DBI. For more details on the library functions covered in this tutorial and the `vignette("DBI", package = "DBI")` introductory tutorial see the DBI specification at `vignette("spec", package = "DBI")`. If you are after a data manipulation library that works at a higher level of abstraction, check out [dplyr](https://dplyr.tidyverse.org). It is a grammar of data manipulation that can work with local dataframes and remote databases and uses DBI under the hood. DBI/vignettes/spec.md0000644000176200001440000030733714561344773014167 0ustar liggesusers## DBI: R Database Interface DBI defines an interface for communication between R and relational database management systems. All classes in this package are virtual and need to be extended by the various R/DBMS implementations (so-called *DBI backends*). ### Definition A DBI backend is an R package which imports the DBI and methods packages. For better or worse, the names of many existing backends start with ‘R’, e.g., RSQLite, RMySQL, RSQLServer; it is up to the backend author to adopt this convention or not. ### DBI classes and methods A backend defines three classes, which are subclasses of DBIDriver, DBIConnection, and DBIResult. The backend provides implementation for all methods of these base classes that are defined but not implemented by DBI. All methods defined in DBI are reexported (so that the package can be used without having to attach DBI), and have an ellipsis `...` in their formals for extensibility. ### Construction of the DBIDriver object The backend must support creation of an instance of its DBIDriver subclass with a constructor function. By default, its name is the package name without the leading ‘R’ (if it exists), e.g., `SQLite` for the RSQLite package. However, backend authors may choose a different name. The constructor must be exported, and it must be a function that is callable without arguments. DBI recommends to define a constructor with an empty argument list. ### Examples ``` r RSQLite::SQLite() ``` ## Determine the SQL data type of an object This section describes the behavior of the following method: ``` r dbDataType(dbObj, obj, ...) ``` ### Description Returns an SQL string that describes the SQL data type to be used for an object. The default implementation of this generic determines the SQL type of an R object according to the SQL 92 specification, which may serve as a starting point for driver implementations. DBI also provides an implementation for data.frame which will return a character vector giving the type for each column in the dataframe. ### Arguments | | | |---------|-----------------------------------------------------| | `dbObj` | A object inheriting from DBIDriver or DBIConnection | | `obj` | An R object whose SQL type we want to determine. | | `...` | Other arguments passed on to methods. | ### Details The data types supported by databases are different than the data types in R, but the mapping between the primitive types is straightforward: - Any of the many fixed and varying length character types are mapped to character vectors - Fixed-precision (non-IEEE) numbers are mapped into either numeric or integer vectors. Notice that many DBMS do not follow IEEE arithmetic, so there are potential problems with under/overflows and loss of precision. ### Value `dbDataType()` returns the SQL type that corresponds to the `obj` argument as a non-empty character string. For data frames, a character vector with one element per column is returned. ### Failure modes An error is raised for invalid values for the `obj` argument such as a `NULL` value. ### Specification The backend can override the `dbDataType()` generic for its driver class. This generic expects an arbitrary object as second argument. To query the values returned by the default implementation, run `example(dbDataType, package = "DBI")`. If the backend needs to override this generic, it must accept all basic R data types as its second argument, namely logical, integer, numeric, character, dates (see Dates), date-time (see DateTimeClasses), and difftime. If the database supports blobs, this method also must accept lists of raw vectors, and blob::blob objects. As-is objects (i.e., wrapped by `I()`) must be supported and return the same results as their unwrapped counterparts. The SQL data type for factor and ordered is the same as for character. The behavior for other object types is not specified. All data types returned by `dbDataType()` are usable in an SQL statement of the form `"CREATE TABLE test (a ...)"`. ### Examples ``` r dbDataType(ANSI(), 1:5) dbDataType(ANSI(), 1) dbDataType(ANSI(), TRUE) dbDataType(ANSI(), Sys.Date()) dbDataType(ANSI(), Sys.time()) dbDataType(ANSI(), Sys.time() - as.POSIXct(Sys.Date())) dbDataType(ANSI(), c("x", "abc")) dbDataType(ANSI(), list(raw(10), raw(20))) dbDataType(ANSI(), I(3)) dbDataType(ANSI(), iris) con <- dbConnect(RSQLite::SQLite(), ":memory:") dbDataType(con, 1:5) dbDataType(con, 1) dbDataType(con, TRUE) dbDataType(con, Sys.Date()) dbDataType(con, Sys.time()) dbDataType(con, Sys.time() - as.POSIXct(Sys.Date())) dbDataType(con, c("x", "abc")) dbDataType(con, list(raw(10), raw(20))) dbDataType(con, I(3)) dbDataType(con, iris) dbDisconnect(con) ``` ## Create a connection to a DBMS This section describes the behavior of the following method: ``` r dbConnect(drv, ...) ``` ### Description Connect to a DBMS going through the appropriate authentication procedure. Some implementations may allow you to have multiple connections open, so you may invoke this function repeatedly assigning its output to different objects. The authentication mechanism is left unspecified, so check the documentation of individual drivers for details. Use `dbCanConnect()` to check if a connection can be established. ### Arguments | | | |-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `drv` | an object that inherits from DBIDriver, or an existing DBIConnection object (in order to clone an existing connection). | | `...` | authentication arguments needed by the DBMS instance; these typically include `user`, `password`, `host`, `port`, `dbname`, etc. For details see the appropriate `DBIDriver`. | ### Value `dbConnect()` returns an S4 object that inherits from DBIConnection. This object is used to communicate with the database engine. A `format()` method is defined for the connection object. It returns a string that consists of a single line of text. ### Specification DBI recommends using the following argument names for authentication parameters, with `NULL` default: - `user` for the user name (default: current user) - `password` for the password - `host` for the host name (default: local connection) - `port` for the port number (default: local connection) - `dbname` for the name of the database on the host, or the database file name The defaults should provide reasonable behavior, in particular a local connection for `host = NULL`. For some DBMS (e.g., PostgreSQL), this is different to a TCP/IP connection to `localhost`. In addition, DBI supports the `bigint` argument that governs how 64-bit integer data is returned. The following values are supported: - `"integer"`: always return as `integer`, silently overflow - `"numeric"`: always return as `numeric`, silently round - `"character"`: always return the decimal representation as `character` - `"integer64"`: return as a data type that can be coerced using `as.integer()` (with warning on overflow), `as.numeric()` and `as.character()` ### Examples ``` r # SQLite only needs a path to the database. (Here, ":memory:" is a special # path that creates an in-memory database.) Other database drivers # will require more details (like user, password, host, port, etc.) con <- dbConnect(RSQLite::SQLite(), ":memory:") con dbListTables(con) dbDisconnect(con) # Bad, for subtle reasons: # This code fails when RSQLite isn't loaded yet, # because dbConnect() doesn't know yet about RSQLite. dbListTables(con <- dbConnect(RSQLite::SQLite(), ":memory:")) ``` ## Disconnect (close) a connection This section describes the behavior of the following method: ``` r dbDisconnect(conn, ...) ``` ### Description This closes the connection, discards all pending work, and frees resources (e.g., memory, sockets). ### Arguments | | | |--------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `...` | Other parameters passed on to methods. | ### Value `dbDisconnect()` returns `TRUE`, invisibly. ### Failure modes A warning is issued on garbage collection when a connection has been released without calling `dbDisconnect()`, but this cannot be tested automatically. A warning is issued immediately when calling `dbDisconnect()` on an already disconnected or invalid connection. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbDisconnect(con) ``` ## Execute a query on a given database connection This section describes the behavior of the following method: ``` r dbSendQuery(conn, statement, ...) ``` ### Description The `dbSendQuery()` method only submits and synchronously executes the SQL query to the database engine. It does *not* extract any records — for that you need to use the `dbFetch()` method, and then you must call `dbClearResult()` when you finish fetching the records you need. For interactive use, you should almost always prefer `dbGetQuery()`. Use `dbSendQueryArrow()` or `dbGetQueryArrow()` instead to retrieve the results as an Arrow object. ### Arguments | | | |-------------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `statement` | a character string containing SQL. | | `...` | Other parameters passed on to methods. | ### Additional arguments The following arguments are not part of the `dbSendQuery()` generic (to improve compatibility across backends) but are part of the DBI specification: - `params` (default: `NULL`) - `immediate` (default: `NULL`) They must be provided as named arguments. See the "Specification" sections for details on their usage. ### Specification No warnings occur under normal conditions. When done, the DBIResult object must be cleared with a call to `dbClearResult()`. Failure to clear the result set leads to a warning when the connection is closed. If the backend supports only one open result set per connection, issuing a second query invalidates an already open result set and raises a warning. The newly opened result set is valid and must be cleared with `dbClearResult()`. The `param` argument allows passing query parameters, see `dbBind()` for details. ### Specification for the `immediate` argument The `immediate` argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing `immediate = TRUE` leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default `NULL` means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct `immediate` argument. Examples for possible behaviors: 1. DBI backend defaults to `immediate = TRUE` internally 1. A query without parameters is passed: query is executed 2. A query with parameters is passed: 1. `params` not given: rejected immediately by the database because of a syntax error in the query, the backend tries `immediate = FALSE` (and gives a message) 2. `params` given: query is executed using `immediate = FALSE` 2. DBI backend defaults to `immediate = FALSE` internally 1. A query without parameters is passed: 1. simple query: query is executed 2. "special" query (such as setting a config options): fails, the backend tries `immediate = TRUE` (and gives a message) 2. A query with parameters is passed: 1. `params` not given: waiting for parameters via `dbBind()` 2. `params` given: query is executed ### Details This method is for `SELECT` queries only. Some backends may support data manipulation queries through this method for compatibility reasons. However, callers are strongly encouraged to use `dbSendStatement()` for data manipulation statements. The query is submitted to the database server and the DBMS executes it, possibly generating vast amounts of data. Where these data live is driver-specific: some drivers may choose to leave the output on the server and transfer them piecemeal to R, others may transfer all the data to the client – but not necessarily to the memory that R manages. See individual drivers' `dbSendQuery()` documentation for details. ### Value `dbSendQuery()` returns an S4 object that inherits from DBIResult. The result set can be used with `dbFetch()` to extract records. Once you have finished using a result, make sure to clear it with `dbClearResult()`. ### The data retrieval flow This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of `dbBind()` or `dbBindArrow()`, is implemented by `dbGetQuery()`, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendQuery()` to create a result set object of class DBIResult. 2. Optionally, bind query parameters with `dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbColumnInfo()` to retrieve the structure of the result set without retrieving actual data. 4. Use `dbFetch()` to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. 5. Use `dbHasCompleted()` to tell when you're done. This method returns `TRUE` if no more rows are available for fetching. 6. Repeat the last four steps as necessary. 7. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### Failure modes An error is raised when issuing a query over a closed or invalid connection, or if the query is not a non-`NA` string. An error is also raised if the syntax of the query is invalid and all query parameters are given (by passing the `params` argument) or the `immediate` argument is set to `TRUE`. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4") dbFetch(rs) dbClearResult(rs) # Pass one set of values with the param argument: rs <- dbSendQuery( con, "SELECT * FROM mtcars WHERE cyl = ?", params = list(4L) ) dbFetch(rs) dbClearResult(rs) # Pass multiple sets of values with dbBind(): rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = ?") dbBind(rs, list(6L)) dbFetch(rs) dbBind(rs, list(8L)) dbFetch(rs) dbClearResult(rs) dbDisconnect(con) ``` ## Fetch records from a previously executed query This section describes the behavior of the following methods: ``` r dbFetch(res, n = -1, ...) fetch(res, n = -1, ...) ``` ### Description Fetch the next `n` elements (rows) from the result set and return them as a data.frame. ### Arguments | | | |-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `res` | An object inheriting from DBIResult, created by `dbSendQuery()`. | | `n` | maximum number of records to retrieve per fetch. Use `n = -1` or `n = Inf` to retrieve all pending records. Some implementations may recognize other special values. | | `...` | Other arguments passed on to methods. | ### Details `fetch()` is provided for compatibility with older DBI clients - for all new code you are strongly encouraged to use `dbFetch()`. The default implementation for `dbFetch()` calls `fetch()` so that it is compatible with existing code. Modern backends should implement for `dbFetch()` only. ### Value `dbFetch()` always returns a data.frame with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows. Passing `n = NA` is supported and returns an arbitrary number of rows (at least one) as specified by the driver, but at most the remaining rows in the result set. ### The data retrieval flow This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of `dbBind()` or `dbBindArrow()`, is implemented by `dbGetQuery()`, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendQuery()` to create a result set object of class DBIResult. 2. Optionally, bind query parameters with `dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbColumnInfo()` to retrieve the structure of the result set without retrieving actual data. 4. Use `dbFetch()` to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. 5. Use `dbHasCompleted()` to tell when you're done. This method returns `TRUE` if no more rows are available for fetching. 6. Repeat the last four steps as necessary. 7. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### Failure modes An attempt to fetch from a closed result set raises an error. If the `n` argument is not an atomic whole number greater or equal to -1 or Inf, an error is raised, but a subsequent call to `dbFetch()` with proper `n` argument succeeds. Calling `dbFetch()` on a result set from a data manipulation query created by `dbSendStatement()` can be fetched and return an empty data frame, with a warning. ### Specification Fetching multi-row queries with one or more columns by default returns the entire result. Multi-row queries can also be fetched progressively by passing a whole number (integer or numeric) as the `n` argument. A value of Inf for the `n` argument is supported and also returns the full result. If more rows than available are fetched, the result is returned in full without warning. If fewer rows than requested are returned, further fetches will return a data frame with zero rows. If zero rows are fetched, the columns of the data frame are still fully typed. Fetching fewer rows than available is permitted, no warning is issued when clearing the result set. A column named `row_names` is treated like any other column. The column types of the returned data frame depend on the data returned: - integer (or coercible to an integer) for integer values between -2^31 and 2^31 - 1, with NA for SQL `NULL` values - numeric for numbers with a fractional component, with NA for SQL `NULL` values - logical for Boolean values (some backends may return an integer); with NA for SQL `NULL` values - character for text, with NA for SQL `NULL` values - lists of raw for blobs with NULL entries for SQL NULL values - coercible using `as.Date()` for dates, with NA for SQL `NULL` values (also applies to the return value of the SQL function `current_date`) - coercible using `hms::as_hms()` for times, with NA for SQL `NULL` values (also applies to the return value of the SQL function `current_time`) - coercible using `as.POSIXct()` for timestamps, with NA for SQL `NULL` values (also applies to the return value of the SQL function `current_timestamp`) If dates and timestamps are supported by the backend, the following R types are used: - Date for dates (also applies to the return value of the SQL function `current_date`) - POSIXct for timestamps (also applies to the return value of the SQL function `current_timestamp`) R has no built-in type with lossless support for the full range of 64-bit or larger integers. If 64-bit integers are returned from a query, the following rules apply: - Values are returned in a container with support for the full range of valid 64-bit values (such as the `integer64` class of the bit64 package) - Coercion to numeric always returns a number that is as close as possible to the true value - Loss of precision when converting to numeric gives a warning - Conversion to character always returns a lossless decimal representation of the data ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) # Fetch all results rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4") dbFetch(rs) dbClearResult(rs) # Fetch in chunks rs <- dbSendQuery(con, "SELECT * FROM mtcars") while (!dbHasCompleted(rs)) { chunk <- dbFetch(rs, 10) print(nrow(chunk)) } dbClearResult(rs) dbDisconnect(con) ``` ## Clear a result set This section describes the behavior of the following method: ``` r dbClearResult(res, ...) ``` ### Description Frees all resources (local and remote) associated with a result set. This step is mandatory for all objects obtained by calling `dbSendQuery()` or `dbSendStatement()`. ### Arguments | | | |-------|---------------------------------------| | `res` | An object inheriting from DBIResult. | | `...` | Other arguments passed on to methods. | ### Value `dbClearResult()` returns `TRUE`, invisibly, for result sets obtained from `dbSendQuery()`, `dbSendStatement()`, or `dbSendQueryArrow()`, ### The data retrieval flow This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of `dbBind()` or `dbBindArrow()`, is implemented by `dbGetQuery()`, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendQuery()` to create a result set object of class DBIResult. 2. Optionally, bind query parameters with `dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbColumnInfo()` to retrieve the structure of the result set without retrieving actual data. 4. Use `dbFetch()` to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. 5. Use `dbHasCompleted()` to tell when you're done. This method returns `TRUE` if no more rows are available for fetching. 6. Repeat the last four steps as necessary. 7. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### The command execution flow This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of `dbBindArrow()`, is implemented by `dbExecute()`, which should be sufficient for non-parameterized queries. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendStatement()` to create a result set object of class DBIResult. For some queries you need to pass `immediate = TRUE`. 2. Optionally, bind query parameters with`dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbGetRowsAffected()` to retrieve the number of rows affected by the query. 4. Repeat the last two steps as necessary. 5. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### Failure modes An attempt to close an already closed result set issues a warning for `dbSendQuery()`, `dbSendStatement()`, and `dbSendQueryArrow()`, ### Specification `dbClearResult()` frees all resources associated with retrieving the result of a query or update operation. The DBI backend can expect a call to `dbClearResult()` for each `dbSendQuery()` or `dbSendStatement()` call. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") rs <- dbSendQuery(con, "SELECT 1") print(dbFetch(rs)) dbClearResult(rs) dbDisconnect(con) ``` ## Bind values to a parameterized/prepared statement This section describes the behavior of the following methods: ``` r dbBind(res, params, ...) dbBindArrow(res, params, ...) ``` ### Description For parametrized or prepared statements, the `dbSendQuery()`, `dbSendQueryArrow()`, and `dbSendStatement()` functions can be called with statements that contain placeholders for values. The `dbBind()` and `dbBindArrow()` functions bind these placeholders to actual values, and are intended to be called on the result set before calling `dbFetch()` or `dbFetchArrow()`. The values are passed to `dbBind()` as lists or data frames, and to `dbBindArrow()` as a stream created by `nanoarrow::as_nanoarrow_array_stream()`. [![\[Experimental\]](https://dbi.r-dbi.org/reference/figures/lifecycle-experimental.svg)](https://lifecycle.r-lib.org/articles/stages.html#experimental) `dbBindArrow()` is experimental, as are the other `⁠*Arrow⁠` functions. `dbSendQuery()` is compatible with `dbBindArrow()`, and `dbSendQueryArrow()` is compatible with `dbBind()`. ### Arguments | | | |----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `res` | An object inheriting from DBIResult. | | `params` | For `dbBind()`, a list of values, named or unnamed, or a data frame, with one element/column per query parameter. For `dbBindArrow()`, values as a nanoarrow stream, with one column per query parameter. | | `...` | Other arguments passed on to methods. | ### Details DBI supports parametrized (or prepared) queries and statements via the `dbBind()` and `dbBindArrow()` generics. Parametrized queries are different from normal queries in that they allow an arbitrary number of placeholders, which are later substituted by actual values. Parametrized queries (and statements) serve two purposes: - The same query can be executed more than once with different values. The DBMS may cache intermediate information for the query, such as the execution plan, and execute it faster. - Separation of query syntax and parameters protects against SQL injection. The placeholder format is currently not specified by DBI; in the future, a uniform placeholder syntax may be supported. Consult the backend documentation for the supported formats. For automated testing, backend authors specify the placeholder syntax with the `placeholder_pattern` tweak. Known examples are: - `⁠?⁠` (positional matching in order of appearance) in RMariaDB and RSQLite - `⁠\$1⁠` (positional matching by index) in RPostgres and RSQLite - `⁠:name⁠` and `⁠\$name⁠` (named matching) in RSQLite ### Value `dbBind()` returns the result set, invisibly, for queries issued by `dbSendQuery()` or `dbSendQueryArrow()` and also for data manipulation statements issued by `dbSendStatement()`. ### The data retrieval flow This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of `dbBind()` or `dbBindArrow()`, is implemented by `dbGetQuery()`, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendQuery()` to create a result set object of class DBIResult. 2. Optionally, bind query parameters with `dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbColumnInfo()` to retrieve the structure of the result set without retrieving actual data. 4. Use `dbFetch()` to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. 5. Use `dbHasCompleted()` to tell when you're done. This method returns `TRUE` if no more rows are available for fetching. 6. Repeat the last four steps as necessary. 7. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### The data retrieval flow for Arrow streams This section gives a complete overview over the flow for the execution of queries that return tabular data as an Arrow stream. Most of this flow, except repeated calling of `dbBindArrow()` or `dbBind()`, is implemented by `dbGetQueryArrow()`, which should be sufficient unless you have a parameterized query that you want to reuse. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendQueryArrow()` to create a result set object of class DBIResultArrow. 2. Optionally, bind query parameters with `dbBindArrow()` or `dbBind()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Use `dbFetchArrow()` to get a data stream. 4. Repeat the last two steps as necessary. 5. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### The command execution flow This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of `dbBindArrow()`, is implemented by `dbExecute()`, which should be sufficient for non-parameterized queries. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendStatement()` to create a result set object of class DBIResult. For some queries you need to pass `immediate = TRUE`. 2. Optionally, bind query parameters with`dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbGetRowsAffected()` to retrieve the number of rows affected by the query. 4. Repeat the last two steps as necessary. 5. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### Failure modes Calling `dbBind()` for a query without parameters raises an error. Binding too many or not enough values, or parameters with wrong names or unequal length, also raises an error. If the placeholders in the query are named, all parameter values must have names (which must not be empty or `NA`), and vice versa, otherwise an error is raised. The behavior for mixing placeholders of different types (in particular mixing positional and named placeholders) is not specified. Calling `dbBind()` on a result set already cleared by `dbClearResult()` also raises an error. ### Specification DBI clients execute parametrized statements as follows: 1. Call `dbSendQuery()`, `dbSendQueryArrow()` or `dbSendStatement()` with a query or statement that contains placeholders, store the returned DBIResult object in a variable. Mixing placeholders (in particular, named and unnamed ones) is not recommended. It is good practice to register a call to `dbClearResult()` via `on.exit()` right after calling `dbSendQuery()` or `dbSendStatement()` (see the last enumeration item). Until `dbBind()` or `dbBindArrow()` have been called, the returned result set object has the following behavior: - `dbFetch()` raises an error (for `dbSendQuery()` and `dbSendQueryArrow()`) - `dbGetRowCount()` returns zero (for `dbSendQuery()` and `dbSendQueryArrow()`) - `dbGetRowsAffected()` returns an integer `NA` (for `dbSendStatement()`) - `dbIsValid()` returns `TRUE` - `dbHasCompleted()` returns `FALSE` 2. Call `dbBind()` or `dbBindArrow()`: - For `dbBind()`, the `params` argument must be a list where all elements have the same lengths and contain values supported by the backend. A data.frame is internally stored as such a list. - For `dbBindArrow()`, the `params` argument must be a nanoarrow array stream, with one column per query parameter. 3. Retrieve the data or the number of affected rows from the `DBIResult` object. - For queries issued by `dbSendQuery()` or `dbSendQueryArrow()`, call `dbFetch()`. - For statements issued by `dbSendStatements()`, call `dbGetRowsAffected()`. (Execution begins immediately after the `dbBind()` call, the statement is processed entirely before the function returns.) 4. Repeat 2. and 3. as necessary. 5. Close the result set via `dbClearResult()`. The elements of the `params` argument do not need to be scalars, vectors of arbitrary length (including length 0) are supported. For queries, calling `dbFetch()` binding such parameters returns concatenated results, equivalent to binding and fetching for each set of values and connecting via `rbind()`. For data manipulation statements, `dbGetRowsAffected()` returns the total number of rows affected if binding non-scalar parameters. `dbBind()` also accepts repeated calls on the same result set for both queries and data manipulation statements, even if no results are fetched between calls to `dbBind()`, for both queries and data manipulation statements. If the placeholders in the query are named, their order in the `params` argument is not important. At least the following data types are accepted on input (including NA): - integer - numeric - logical for Boolean values - character (also with special characters such as spaces, newlines, quotes, and backslashes) - factor (bound as character, with warning) - Date (also when stored internally as integer) - POSIXct timestamps - POSIXlt timestamps - difftime values (also with units other than seconds and with the value stored as integer) - lists of raw for blobs (with `NULL` entries for SQL NULL values) - objects of type blob::blob ### Examples ``` r # Data frame flow: con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "iris", iris) # Using the same query for different values iris_result <- dbSendQuery(con, "SELECT * FROM iris WHERE [Petal.Width] > ?") dbBind(iris_result, list(2.3)) dbFetch(iris_result) dbBind(iris_result, list(3)) dbFetch(iris_result) dbClearResult(iris_result) # Executing the same statement with different values at once iris_result <- dbSendStatement(con, "DELETE FROM iris WHERE [Species] = \$species") dbBind(iris_result, list(species = c("setosa", "versicolor", "unknown"))) dbGetRowsAffected(iris_result) dbClearResult(iris_result) nrow(dbReadTable(con, "iris")) dbDisconnect(con) # Arrow flow: con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "iris", iris) # Using the same query for different values iris_result <- dbSendQueryArrow(con, "SELECT * FROM iris WHERE [Petal.Width] > ?") dbBindArrow( iris_result, nanoarrow::as_nanoarrow_array_stream(data.frame(2.3, fix.empty.names = FALSE)) ) as.data.frame(dbFetchArrow(iris_result)) dbBindArrow( iris_result, nanoarrow::as_nanoarrow_array_stream(data.frame(3, fix.empty.names = FALSE)) ) as.data.frame(dbFetchArrow(iris_result)) dbClearResult(iris_result) # Executing the same statement with different values at once iris_result <- dbSendStatement(con, "DELETE FROM iris WHERE [Species] = \$species") dbBindArrow(iris_result, nanoarrow::as_nanoarrow_array_stream(data.frame( species = c("setosa", "versicolor", "unknown") ))) dbGetRowsAffected(iris_result) dbClearResult(iris_result) nrow(dbReadTable(con, "iris")) dbDisconnect(con) ``` ## Retrieve results from a query This section describes the behavior of the following method: ``` r dbGetQuery(conn, statement, ...) ``` ### Description Returns the result of a query as a data frame. `dbGetQuery()` comes with a default implementation (which should work with most backends) that calls `dbSendQuery()`, then `dbFetch()`, ensuring that the result is always freed by `dbClearResult()`. For retrieving chunked/paged results or for passing query parameters, see `dbSendQuery()`, in particular the "The data retrieval flow" section. For retrieving results as an Arrow object, see `dbGetQueryArrow()`. ### Arguments | | | |-------------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `statement` | a character string containing SQL. | | `...` | Other parameters passed on to methods. | ### Additional arguments The following arguments are not part of the `dbGetQuery()` generic (to improve compatibility across backends) but are part of the DBI specification: - `n` (default: -1) - `params` (default: `NULL`) - `immediate` (default: `NULL`) They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage. ### Specification A column named `row_names` is treated like any other column. The `n` argument specifies the number of rows to be fetched. If omitted, fetching multi-row queries with one or more columns returns the entire result. A value of Inf for the `n` argument is supported and also returns the full result. If more rows than available are fetched (by passing a too large value for `n`), the result is returned in full without warning. If zero rows are requested, the columns of the data frame are still fully typed. Fetching fewer rows than available is permitted, no warning is issued. The `param` argument allows passing query parameters, see `dbBind()` for details. ### Specification for the `immediate` argument The `immediate` argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing `immediate = TRUE` leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default `NULL` means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct `immediate` argument. Examples for possible behaviors: 1. DBI backend defaults to `immediate = TRUE` internally 1. A query without parameters is passed: query is executed 2. A query with parameters is passed: 1. `params` not given: rejected immediately by the database because of a syntax error in the query, the backend tries `immediate = FALSE` (and gives a message) 2. `params` given: query is executed using `immediate = FALSE` 2. DBI backend defaults to `immediate = FALSE` internally 1. A query without parameters is passed: 1. simple query: query is executed 2. "special" query (such as setting a config options): fails, the backend tries `immediate = TRUE` (and gives a message) 2. A query with parameters is passed: 1. `params` not given: waiting for parameters via `dbBind()` 2. `params` given: query is executed ### Details This method is for `SELECT` queries only (incl. other SQL statements that return a `SELECT`-alike result, e.g., execution of a stored procedure or data manipulation queries like `⁠INSERT INTO ... RETURNING ...⁠`). To execute a stored procedure that does not return a result set, use `dbExecute()`. Some backends may support data manipulation statements through this method for compatibility reasons. However, callers are strongly advised to use `dbExecute()` for data manipulation statements. ### Value `dbGetQuery()` always returns a data.frame, with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows. ### Implementation notes Subclasses should override this method only if they provide some sort of performance optimization. ### Failure modes An error is raised when issuing a query over a closed or invalid connection, if the syntax of the query is invalid, or if the query is not a non-`NA` string. If the `n` argument is not an atomic whole number greater or equal to -1 or Inf, an error is raised, but a subsequent call to `dbGetQuery()` with proper `n` argument succeeds. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) dbGetQuery(con, "SELECT * FROM mtcars") dbGetQuery(con, "SELECT * FROM mtcars", n = 6) # Pass values using the param argument: # (This query runs eight times, once for each different # parameter. The resulting rows are combined into a single # data frame.) dbGetQuery( con, "SELECT COUNT(*) FROM mtcars WHERE cyl = ?", params = list(1:8) ) dbDisconnect(con) ``` ## Execute a data manipulation statement on a given database connection This section describes the behavior of the following method: ``` r dbSendStatement(conn, statement, ...) ``` ### Description The `dbSendStatement()` method only submits and synchronously executes the SQL data manipulation statement (e.g., `UPDATE`, `DELETE`, `⁠INSERT INTO⁠`, `⁠DROP TABLE⁠`, ...) to the database engine. To query the number of affected rows, call `dbGetRowsAffected()` on the returned result object. You must also call `dbClearResult()` after that. For interactive use, you should almost always prefer `dbExecute()`. ### Arguments | | | |-------------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `statement` | a character string containing SQL. | | `...` | Other parameters passed on to methods. | ### Additional arguments The following arguments are not part of the `dbSendStatement()` generic (to improve compatibility across backends) but are part of the DBI specification: - `params` (default: `NULL`) - `immediate` (default: `NULL`) They must be provided as named arguments. See the "Specification" sections for details on their usage. ### Specification No warnings occur under normal conditions. When done, the DBIResult object must be cleared with a call to `dbClearResult()`. Failure to clear the result set leads to a warning when the connection is closed. If the backend supports only one open result set per connection, issuing a second query invalidates an already open result set and raises a warning. The newly opened result set is valid and must be cleared with `dbClearResult()`. The `param` argument allows passing query parameters, see `dbBind()` for details. ### Specification for the `immediate` argument The `immediate` argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing `immediate = TRUE` leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default `NULL` means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct `immediate` argument. Examples for possible behaviors: 1. DBI backend defaults to `immediate = TRUE` internally 1. A query without parameters is passed: query is executed 2. A query with parameters is passed: 1. `params` not given: rejected immediately by the database because of a syntax error in the query, the backend tries `immediate = FALSE` (and gives a message) 2. `params` given: query is executed using `immediate = FALSE` 2. DBI backend defaults to `immediate = FALSE` internally 1. A query without parameters is passed: 1. simple query: query is executed 2. "special" query (such as setting a config options): fails, the backend tries `immediate = TRUE` (and gives a message) 2. A query with parameters is passed: 1. `params` not given: waiting for parameters via `dbBind()` 2. `params` given: query is executed ### Details `dbSendStatement()` comes with a default implementation that simply forwards to `dbSendQuery()`, to support backends that only implement the latter. ### Value `dbSendStatement()` returns an S4 object that inherits from DBIResult. The result set can be used with `dbGetRowsAffected()` to determine the number of rows affected by the query. Once you have finished using a result, make sure to clear it with `dbClearResult()`. ### The command execution flow This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of `dbBindArrow()`, is implemented by `dbExecute()`, which should be sufficient for non-parameterized queries. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendStatement()` to create a result set object of class DBIResult. For some queries you need to pass `immediate = TRUE`. 2. Optionally, bind query parameters with`dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbGetRowsAffected()` to retrieve the number of rows affected by the query. 4. Repeat the last two steps as necessary. 5. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### Failure modes An error is raised when issuing a statement over a closed or invalid connection, or if the statement is not a non-`NA` string. An error is also raised if the syntax of the query is invalid and all query parameters are given (by passing the `params` argument) or the `immediate` argument is set to `TRUE`. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cars", head(cars, 3)) rs <- dbSendStatement( con, "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" ) dbHasCompleted(rs) dbGetRowsAffected(rs) dbClearResult(rs) dbReadTable(con, "cars") # there are now 6 rows # Pass one set of values directly using the param argument: rs <- dbSendStatement( con, "INSERT INTO cars (speed, dist) VALUES (?, ?)", params = list(4L, 5L) ) dbClearResult(rs) # Pass multiple sets of values using dbBind(): rs <- dbSendStatement( con, "INSERT INTO cars (speed, dist) VALUES (?, ?)" ) dbBind(rs, list(5:6, 6:7)) dbBind(rs, list(7L, 8L)) dbClearResult(rs) dbReadTable(con, "cars") # there are now 10 rows dbDisconnect(con) ``` ## Change database state This section describes the behavior of the following method: ``` r dbExecute(conn, statement, ...) ``` ### Description Executes a statement and returns the number of rows affected. `dbExecute()` comes with a default implementation (which should work with most backends) that calls `dbSendStatement()`, then `dbGetRowsAffected()`, ensuring that the result is always freed by `dbClearResult()`. For passing query parameters, see `dbBind()`, in particular the "The command execution flow" section. ### Arguments | | | |-------------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `statement` | a character string containing SQL. | | `...` | Other parameters passed on to methods. | ### Additional arguments The following arguments are not part of the `dbExecute()` generic (to improve compatibility across backends) but are part of the DBI specification: - `params` (default: `NULL`) - `immediate` (default: `NULL`) They must be provided as named arguments. See the "Specification" sections for details on their usage. ### Specification The `param` argument allows passing query parameters, see `dbBind()` for details. ### Specification for the `immediate` argument The `immediate` argument supports distinguishing between "direct" and "prepared" APIs offered by many database drivers. Passing `immediate = TRUE` leads to immediate execution of the query or statement, via the "direct" API (if supported by the driver). The default `NULL` means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct `immediate` argument. Examples for possible behaviors: 1. DBI backend defaults to `immediate = TRUE` internally 1. A query without parameters is passed: query is executed 2. A query with parameters is passed: 1. `params` not given: rejected immediately by the database because of a syntax error in the query, the backend tries `immediate = FALSE` (and gives a message) 2. `params` given: query is executed using `immediate = FALSE` 2. DBI backend defaults to `immediate = FALSE` internally 1. A query without parameters is passed: 1. simple query: query is executed 2. "special" query (such as setting a config options): fails, the backend tries `immediate = TRUE` (and gives a message) 2. A query with parameters is passed: 1. `params` not given: waiting for parameters via `dbBind()` 2. `params` given: query is executed ### Details You can also use `dbExecute()` to call a stored procedure that performs data manipulation or other actions that do not return a result set. To execute a stored procedure that returns a result set, or a data manipulation query that also returns a result set such as `⁠INSERT INTO ... RETURNING ...⁠`, use `dbGetQuery()` instead. ### Value `dbExecute()` always returns a scalar numeric that specifies the number of rows affected by the statement. ### Implementation notes Subclasses should override this method only if they provide some sort of performance optimization. ### Failure modes An error is raised when issuing a statement over a closed or invalid connection, if the syntax of the statement is invalid, or if the statement is not a non-`NA` string. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cars", head(cars, 3)) dbReadTable(con, "cars") # there are 3 rows dbExecute( con, "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" ) dbReadTable(con, "cars") # there are now 6 rows # Pass values using the param argument: dbExecute( con, "INSERT INTO cars (speed, dist) VALUES (?, ?)", params = list(4:7, 5:8) ) dbReadTable(con, "cars") # there are now 10 rows dbDisconnect(con) ``` ## Quote literal strings This section describes the behavior of the following method: ``` r dbQuoteString(conn, x, ...) ``` ### Description Call this method to generate a string that is suitable for use in a query as a string literal, to make sure that you generate valid SQL and protect against SQL injection attacks. ### Arguments | | | |--------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `x` | A character vector to quote as string. | | `...` | Other arguments passed on to methods. | ### Value `dbQuoteString()` returns an object that can be coerced to character, of the same length as the input. For an empty character vector this function returns a length-0 object. When passing the returned object again to `dbQuoteString()` as `x` argument, it is returned unchanged. Passing objects of class SQL should also return them unchanged. (For backends it may be most convenient to return SQL objects to achieve this behavior, but this is not required.) ### Failure modes Passing a numeric, integer, logical, or raw vector, or a list for the `x` argument raises an error. ### Specification The returned expression can be used in a `⁠SELECT ...⁠` query, and for any scalar character `x` the value of `dbGetQuery(paste0("SELECT ", dbQuoteString(x)))[[1]]` must be identical to `x`, even if `x` contains spaces, tabs, quotes (single or double), backticks, or newlines (in any combination) or is itself the result of a `dbQuoteString()` call coerced back to character (even repeatedly). If `x` is `NA`, the result must merely satisfy `is.na()`. The strings `"NA"` or `"NULL"` are not treated specially. `NA` should be translated to an unquoted SQL `NULL`, so that the query `⁠SELECT * FROM (SELECT 1) a WHERE ... IS NULL⁠` returns one row. ### Examples ``` r # Quoting ensures that arbitrary input is safe for use in a query name <- "Robert'); DROP TABLE Students;--" dbQuoteString(ANSI(), name) # NAs become NULL dbQuoteString(ANSI(), c("x", NA)) # SQL vectors are always passed through as is var_name <- SQL("select") var_name dbQuoteString(ANSI(), var_name) # This mechanism is used to prevent double escaping dbQuoteString(ANSI(), dbQuoteString(ANSI(), name)) ``` ## Quote identifiers This section describes the behavior of the following method: ``` r dbQuoteIdentifier(conn, x, ...) ``` ### Description Call this method to generate a string that is suitable for use in a query as a column or table name, to make sure that you generate valid SQL and protect against SQL injection attacks. The inverse operation is `dbUnquoteIdentifier()`. ### Arguments | | | |--------|--------------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `x` | A character vector, SQL or Id object to quote as identifier. | | `...` | Other arguments passed on to methods. | ### Value `dbQuoteIdentifier()` returns an object that can be coerced to character, of the same length as the input. For an empty character vector this function returns a length-0 object. The names of the input argument are preserved in the output. When passing the returned object again to `dbQuoteIdentifier()` as `x` argument, it is returned unchanged. Passing objects of class SQL should also return them unchanged. (For backends it may be most convenient to return SQL objects to achieve this behavior, but this is not required.) ### Failure modes An error is raised if the input contains `NA`, but not for an empty string. ### Specification Calling `dbGetQuery()` for a query of the format `⁠SELECT 1 AS ...⁠` returns a data frame with the identifier, unquoted, as column name. Quoted identifiers can be used as table and column names in SQL queries, in particular in queries like `⁠SELECT 1 AS ...⁠` and `⁠SELECT * FROM (SELECT 1) ...⁠`. The method must use a quoting mechanism that is unambiguously different from the quoting mechanism used for strings, so that a query like `⁠SELECT ... FROM (SELECT 1 AS ...)⁠` throws an error if the column names do not match. The method can quote column names that contain special characters such as a space, a dot, a comma, or quotes used to mark strings or identifiers, if the database supports this. In any case, checking the validity of the identifier should be performed only when executing a query, and not by `dbQuoteIdentifier()`. ### Examples ``` r # Quoting ensures that arbitrary input is safe for use in a query name <- "Robert'); DROP TABLE Students;--" dbQuoteIdentifier(ANSI(), name) # Use Id() to specify other components such as the schema id_name <- Id(schema = "schema_name", table = "table_name") id_name dbQuoteIdentifier(ANSI(), id_name) # SQL vectors are always passed through as is var_name <- SQL("select") var_name dbQuoteIdentifier(ANSI(), var_name) # This mechanism is used to prevent double escaping dbQuoteIdentifier(ANSI(), dbQuoteIdentifier(ANSI(), name)) ``` ## Read database tables as data frames This section describes the behavior of the following method: ``` r dbReadTable(conn, name, ...) ``` ### Description Reads a database table to a data frame, optionally converting a column to row names and converting the column names to valid R identifiers. Use `dbReadTableArrow()` instead to obtain an Arrow object. ### Arguments
conn

A DBIConnection object, as returned by dbConnect().
name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. "table_name",

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = "my_schema", table = "table_name")

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL('"my_schema"."table_name"')
...

Other parameters passed on to methods.
### Additional arguments The following arguments are not part of the `dbReadTable()` generic (to improve compatibility across backends) but are part of the DBI specification: - `row.names` (default: `FALSE`) - `check.names` They must be provided as named arguments. See the "Value" section 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: `dbReadTable()` will do the quoting, perhaps by calling `dbQuoteIdentifier(conn, x = name)` - If the result of a call to `dbQuoteIdentifier()`: no more quoting is done ### Details This function returns a data frame. Use `dbReadTableArrow()` to obtain an Arrow object. ### Value `dbReadTable()` returns a data frame that contains the complete data from the remote table, effectively the result of calling `dbGetQuery()` with `⁠SELECT * FROM ⁠`. An empty table is returned as a data frame with zero rows. The presence of rownames depends on the `row.names` argument, see `sqlColumnToRownames()` for details: - If `FALSE` or `NULL`, the returned data frame doesn't have row names. - If `TRUE`, a column named "row_names" is converted to row names. - If `NA`, a column named "row_names" is converted to row names if it exists, otherwise no translation occurs. - If a string, this specifies the name of the column in the remote table that contains the row names. The default is `row.names = FALSE`. If the database supports identifiers with special characters, the columns in the returned data frame are converted to valid R identifiers if the `check.names` argument is `TRUE`, If `check.names = FALSE`, the returned table has non-syntactic column names without quotes. ### Failure modes An error is raised if the table does not exist. An error is raised if `row.names` is `TRUE` and no "row_names" column exists, An error is raised if `row.names` is set to a string and no corresponding column exists. An error is raised when calling this method for a closed or invalid connection. An error is raised if `name` cannot be processed with `dbQuoteIdentifier()` or if this results in a non-scalar. Unsupported values for `row.names` and `check.names` (non-scalars, unsupported data types, `NA` for `check.names`) also raise an error. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars[1:10, ]) dbReadTable(con, "mtcars") dbDisconnect(con) ``` ## Copy data frames to database tables This section describes the behavior of the following method: ``` r dbWriteTable(conn, name, value, ...) ``` ### Description Writes, overwrites or appends a data frame to a database table, optionally converting row names to a column and specifying SQL data types for fields. ### Arguments
conn

A DBIConnection object, as returned by dbConnect().
name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. "table_name",

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = "my_schema", table = "table_name")

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL('"my_schema"."table_name"')
value

A data.frame (or coercible to data.frame).
...

Other parameters passed on to methods.
### Additional arguments The following arguments are not part of the `dbWriteTable()` generic (to improve compatibility across backends) but are part of the DBI specification: - `row.names` (default: `FALSE`) - `overwrite` (default: `FALSE`) - `append` (default: `FALSE`) - `field.types` (default: `NULL`) - `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: `dbWriteTable()` will do the quoting, perhaps by calling `dbQuoteIdentifier(conn, x = name)` - If the result of a call to `dbQuoteIdentifier()`: no more quoting is done The `value` argument must be a data frame with a subset of the columns of the existing table if `append = TRUE`. The order of the columns does not matter with `append = TRUE`. If the `overwrite` argument is `TRUE`, an existing table of the same name will be overwritten. This argument doesn't change behavior if the table does not exist yet. If the `append` argument is `TRUE`, the rows in an existing table are preserved, and the new data are appended. If the table doesn't exist yet, it is created. 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, spaces, and other special characters such as newlines and tabs, can also be used in the data, and, if the database supports non-syntactic identifiers, also for table names and column names. The following data types must be supported at least, and be read identically with `dbReadTable()`: - integer - numeric (the behavior for `Inf` and `NaN` is not specified) - logical - `NA` as NULL - 64-bit values (using `"bigint"` as field type); the result can be - converted to a numeric, which may lose precision, - converted a character vector, which gives the full decimal representation - written to another table and read again unchanged - character (in both UTF-8 and native encodings), supporting empty strings before and after a non-empty string - factor (returned as character) - list of raw (if supported by the database) - objects of type blob::blob (if supported by the database) - date (if supported by the database; returned as `Date`), also for dates prior to 1970 or 1900 or after 2038 - time (if supported by the database; returned as objects that inherit from `difftime`) - timestamp (if supported by the database; returned as `POSIXct` respecting the time zone but not necessarily preserving the input time zone), also for timestamps prior to 1970 or 1900 or after 2038 respecting the time zone but not necessarily preserving the input time zone) Mixing column types in the same table is supported. The `field.types` argument must be a named character vector with at most one entry for each column. It indicates the SQL data type to be used for a new column. If a column is missed from `field.types`, the type is inferred from the input data with `dbDataType()`. The interpretation of rownames depends on the `row.names` argument, see `sqlRownamesToColumn()` for details: - If `FALSE` or `NULL`, row names are ignored. - If `TRUE`, row names are converted to a column named "row_names", even if the input data frame only has natural row names from 1 to `nrow(...)`. - If `NA`, a column named "row_names" is created if the data has custom row names, no extra column is created in the case of natural row names. - If a string, this specifies the name of the column in the remote table that contains the row names, even if the input data frame only has natural row names. The default is `row.names = FALSE`. ### Details This function expects a data frame. Use `dbWriteTableArrow()` to write an Arrow object. This function is useful if you want to create and load a table at the same time. Use `dbAppendTable()` or `dbAppendTableArrow()` for appending data to an existing table, `dbCreateTable()` or `dbCreateTableArrow()` for creating a table, and `dbExistsTable()` and `dbRemoveTable()` for overwriting tables. DBI only standardizes writing data frames with `dbWriteTable()`. Some backends might implement methods that can consume CSV files or other data formats. For details, see the documentation for the individual methods. ### Value `dbWriteTable()` returns `TRUE`, invisibly. ### Failure modes If the table exists, and both `append` and `overwrite` arguments are unset, or `append = TRUE` and the data frame with the new data has different column names, 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 `dbQuoteIdentifier()` or if this results in a non-scalar. Invalid values for the additional arguments `row.names`, `overwrite`, `append`, `field.types`, and `temporary` (non-scalars, unsupported data types, `NA`, incompatible values, duplicate or missing names, incompatible columns) also raise an error. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars[1:5, ]) dbReadTable(con, "mtcars") dbWriteTable(con, "mtcars", mtcars[6:10, ], append = TRUE) dbReadTable(con, "mtcars") dbWriteTable(con, "mtcars", mtcars[1:10, ], overwrite = TRUE) dbReadTable(con, "mtcars") # No row names dbWriteTable(con, "mtcars", mtcars[1:10, ], overwrite = TRUE, row.names = FALSE) dbReadTable(con, "mtcars") ``` ## List remote tables This section describes the behavior of the following method: ``` r dbListTables(conn, ...) ``` ### Description Returns the unquoted names of remote tables accessible through this connection. This should include views and temporary objects, but not all database backends (in particular RMariaDB and RMySQL) support this. ### Arguments | | | |--------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `...` | Other parameters passed on to methods. | ### Value `dbListTables()` returns a character vector that enumerates all tables and views in the database. Tables added with `dbWriteTable()` are part of the list. As soon a table is removed from the database, it is also removed from the list of database tables. The same applies to temporary tables if supported by the database. The returned names are suitable for quoting with `dbQuoteIdentifier()`. ### Failure modes An error is raised when calling this method for a closed or invalid connection. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbListTables(con) dbWriteTable(con, "mtcars", mtcars) dbListTables(con) dbDisconnect(con) ``` ## Does a table exist? This section describes the behavior of the following method: ``` r dbExistsTable(conn, name, ...) ``` ### Description Returns if a table given by name exists in the database. ### Arguments
conn

A DBIConnection object, as returned by dbConnect().
name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. "table_name",

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = "my_schema", table = "table_name")

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL('"my_schema"."table_name"')
...

Other parameters passed on to methods.
### Value `dbExistsTable()` returns a logical scalar, `TRUE` if the table or view specified by the `name` argument exists, `FALSE` otherwise. This includes temporary tables if supported by the database. ### Failure modes 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 `dbQuoteIdentifier()` or if this results in a non-scalar. ### 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: `dbExistsTable()` will do the quoting, perhaps by calling `dbQuoteIdentifier(conn, x = name)` - If the result of a call to `dbQuoteIdentifier()`: no more quoting is done For all tables listed by `dbListTables()`, `dbExistsTable()` returns `TRUE`. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbExistsTable(con, "iris") dbWriteTable(con, "iris", iris) dbExistsTable(con, "iris") dbDisconnect(con) ``` ## Remove a table from the database This section describes the behavior of the following method: ``` r dbRemoveTable(conn, name, ...) ``` ### Description Remove a remote table (e.g., created by `dbWriteTable()`) from the database. ### Arguments
conn

A DBIConnection object, as returned by dbConnect().
name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. "table_name",

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = "my_schema", table = "table_name")

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL('"my_schema"."table_name"')
...

Other parameters passed on to methods.
### Additional arguments The following arguments are not part of the `dbRemoveTable()` generic (to improve compatibility across backends) but are part of the DBI specification: - `temporary` (default: `FALSE`) - `fail_if_missing` (default: `TRUE`) These arguments must be provided as named arguments. If `temporary` is `TRUE`, the call to `dbRemoveTable()` will consider only temporary tables. Not all backends support this argument. In particular, permanent tables of the same name are left untouched. If `fail_if_missing` is `FALSE`, the call to `dbRemoveTable()` succeeds if the table does not exist. ### Specification A table removed by `dbRemoveTable()` doesn't appear in the list of tables returned by `dbListTables()`, and `dbExistsTable()` returns `FALSE`. The removal propagates immediately to other connections to the same database. This function can also be used to remove a temporary table. 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: `dbRemoveTable()` will do the quoting, perhaps by calling `dbQuoteIdentifier(conn, x = name)` - If the result of a call to `dbQuoteIdentifier()`: no more quoting is done ### Value `dbRemoveTable()` returns `TRUE`, invisibly. ### Failure modes If the table does not exist, an error is raised. An attempt to remove a view with this function may result in an error. 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 `dbQuoteIdentifier()` or if this results in a non-scalar. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbExistsTable(con, "iris") dbWriteTable(con, "iris", iris) dbExistsTable(con, "iris") dbRemoveTable(con, "iris") dbExistsTable(con, "iris") dbDisconnect(con) ``` ## List field names of a remote table This section describes the behavior of the following method: ``` r dbListFields(conn, name, ...) ``` ### Description Returns the field names of a remote table as a character vector. ### Arguments
conn

A DBIConnection object, as returned by dbConnect().
name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. "table_name",

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = "my_schema", table = "table_name")

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL('"my_schema"."table_name"')
...

Other parameters passed on to methods.
### Value `dbListFields()` returns a character vector that enumerates all fields in the table in the correct order. This also works for temporary tables if supported by the database. The returned names are suitable for quoting with `dbQuoteIdentifier()`. ### Failure modes If the table does not exist, an error is raised. Invalid types for the `name` argument (e.g., `character` of length not equal to one, or numeric) lead to an error. An error is also raised when calling this method for a closed or invalid connection. ### Specification The `name` argument can be - a string - the return value of `dbQuoteIdentifier()` - a value from the `table` column from the return value of `dbListObjects()` where `is_prefix` is `FALSE` A column named `row_names` is treated like any other column. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) dbListFields(con, "mtcars") dbDisconnect(con) ``` ## Is this DBMS object still valid? This section describes the behavior of the following method: ``` r dbIsValid(dbObj, ...) ``` ### Description This generic tests whether a database object is still valid (i.e. it hasn't been disconnected or cleared). ### Arguments | | | |---------|------------------------------------------------------------------------------------| | `dbObj` | An object inheriting from DBIObject, i.e. DBIDriver, DBIConnection, or a DBIResult | | `...` | Other arguments to methods. | ### Value `dbIsValid()` returns a logical scalar, `TRUE` if the object specified by `dbObj` is valid, `FALSE` otherwise. A DBIConnection object is initially valid, and becomes invalid after disconnecting with `dbDisconnect()`. For an invalid connection object (e.g., for some drivers if the object is saved to a file and then restored), the method also returns `FALSE`. A DBIResult object is valid after a call to `dbSendQuery()`, and stays valid even after all rows have been fetched; only clearing it with `dbClearResult()` invalidates it. A DBIResult object is also valid after a call to `dbSendStatement()`, and stays valid after querying the number of rows affected; only clearing it with `dbClearResult()` invalidates it. If the connection to the database system is dropped (e.g., due to connectivity problems, server failure, etc.), `dbIsValid()` should return `FALSE`. This is not tested automatically. ### Examples ``` r dbIsValid(RSQLite::SQLite()) con <- dbConnect(RSQLite::SQLite(), ":memory:") dbIsValid(con) rs <- dbSendQuery(con, "SELECT 1") dbIsValid(rs) dbClearResult(rs) dbIsValid(rs) dbDisconnect(con) dbIsValid(con) ``` ## Completion status This section describes the behavior of the following method: ``` r dbHasCompleted(res, ...) ``` ### Description This method returns if the operation has completed. A `SELECT` query is completed if all rows have been fetched. A data manipulation statement is always completed. ### Arguments | | | |-------|---------------------------------------| | `res` | An object inheriting from DBIResult. | | `...` | Other arguments passed on to methods. | ### Value `dbHasCompleted()` returns a logical scalar. For a query initiated by `dbSendQuery()` with non-empty result set, `dbHasCompleted()` returns `FALSE` initially and `TRUE` after calling `dbFetch()` without limit. For a query initiated by `dbSendStatement()`, `dbHasCompleted()` always returns `TRUE`. ### The data retrieval flow This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of `dbBind()` or `dbBindArrow()`, is implemented by `dbGetQuery()`, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendQuery()` to create a result set object of class DBIResult. 2. Optionally, bind query parameters with `dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbColumnInfo()` to retrieve the structure of the result set without retrieving actual data. 4. Use `dbFetch()` to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. 5. Use `dbHasCompleted()` to tell when you're done. This method returns `TRUE` if no more rows are available for fetching. 6. Repeat the last four steps as necessary. 7. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### Failure modes Attempting to query completion status for a result set cleared with `dbClearResult()` gives an error. ### Specification The completion status for a query is only guaranteed to be set to `FALSE` after attempting to fetch past the end of the entire result. Therefore, for a query with an empty result set, the initial return value is unspecified, but the result value is `TRUE` after trying to fetch only one row. Similarly, for a query with a result set of length n, the return value is unspecified after fetching n rows, but the result value is `TRUE` after trying to fetch only one more row. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQuery(con, "SELECT * FROM mtcars") dbHasCompleted(rs) ret1 <- dbFetch(rs, 10) dbHasCompleted(rs) ret2 <- dbFetch(rs) dbHasCompleted(rs) dbClearResult(rs) dbDisconnect(con) ``` ## Get the statement associated with a result set This section describes the behavior of the following method: ``` r dbGetStatement(res, ...) ``` ### Description Returns the statement that was passed to `dbSendQuery()` or `dbSendStatement()`. ### Arguments | | | |-------|---------------------------------------| | `res` | An object inheriting from DBIResult. | | `...` | Other arguments passed on to methods. | ### Value `dbGetStatement()` returns a string, the query used in either `dbSendQuery()` or `dbSendStatement()`. ### Failure modes Attempting to query the statement for a result set cleared with `dbClearResult()` gives an error. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQuery(con, "SELECT * FROM mtcars") dbGetStatement(rs) dbClearResult(rs) dbDisconnect(con) ``` ## The number of rows fetched so far This section describes the behavior of the following method: ``` r dbGetRowCount(res, ...) ``` ### Description Returns the total number of rows actually fetched with calls to `dbFetch()` for this result set. ### Arguments | | | |-------|---------------------------------------| | `res` | An object inheriting from DBIResult. | | `...` | Other arguments passed on to methods. | ### Value `dbGetRowCount()` returns a scalar number (integer or numeric), the number of rows fetched so far. After calling `dbSendQuery()`, the row count is initially zero. After a call to `dbFetch()` without limit, the row count matches the total number of rows returned. Fetching a limited number of rows increases the number of rows by the number of rows returned, even if fetching past the end of the result set. For queries with an empty result set, zero is returned even after fetching. For data manipulation statements issued with `dbSendStatement()`, zero is returned before and after calling `dbFetch()`. ### Failure modes Attempting to get the row count for a result set cleared with `dbClearResult()` gives an error. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendQuery(con, "SELECT * FROM mtcars") dbGetRowCount(rs) ret1 <- dbFetch(rs, 10) dbGetRowCount(rs) ret2 <- dbFetch(rs) dbGetRowCount(rs) nrow(ret1) + nrow(ret2) dbClearResult(rs) dbDisconnect(con) ``` ## The number of rows affected This section describes the behavior of the following method: ``` r dbGetRowsAffected(res, ...) ``` ### Description This method returns the number of rows that were added, deleted, or updated by a data manipulation statement. ### Arguments | | | |-------|---------------------------------------| | `res` | An object inheriting from DBIResult. | | `...` | Other arguments passed on to methods. | ### Value `dbGetRowsAffected()` returns a scalar number (integer or numeric), the number of rows affected by a data manipulation statement issued with `dbSendStatement()`. The value is available directly after the call and does not change after calling `dbFetch()`. `NA_integer_` or `NA_numeric_` are allowed if the number of rows affected is not known. For queries issued with `dbSendQuery()`, zero is returned before and after the call to `dbFetch()`. `NA` values are not allowed. ### The command execution flow This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of `dbBindArrow()`, is implemented by `dbExecute()`, which should be sufficient for non-parameterized queries. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendStatement()` to create a result set object of class DBIResult. For some queries you need to pass `immediate = TRUE`. 2. Optionally, bind query parameters with`dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbGetRowsAffected()` to retrieve the number of rows affected by the query. 4. Repeat the last two steps as necessary. 5. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### Failure modes Attempting to get the rows affected for a result set cleared with `dbClearResult()` gives an error. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "mtcars", mtcars) rs <- dbSendStatement(con, "DELETE FROM mtcars") dbGetRowsAffected(rs) nrow(mtcars) dbClearResult(rs) dbDisconnect(con) ``` ## Information about result types This section describes the behavior of the following method: ``` r dbColumnInfo(res, ...) ``` ### Description Produces a data.frame that describes the output of a query. The data.frame should have as many rows as there are output fields in the result set, and each column in the data.frame describes an aspect of the result set field (field name, type, etc.) ### Arguments | | | |-------|---------------------------------------| | `res` | An object inheriting from DBIResult. | | `...` | Other arguments passed on to methods. | ### Value `dbColumnInfo()` returns a data frame with at least two columns `"name"` and `"type"` (in that order) (and optional columns that start with a dot). The `"name"` and `"type"` columns contain the names and types of the R columns of the data frame that is returned from `dbFetch()`. The `"type"` column is of type `character` and only for information. Do not compute on the `"type"` column, instead use `dbFetch(res, n = 0)` to create a zero-row data frame initialized with the correct data types. ### The data retrieval flow This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames. Most of this flow, except repeated calling of `dbBind()` or `dbBindArrow()`, is implemented by `dbGetQuery()`, which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by `dbConnect()`. See also `vignette("dbi-advanced")` for a walkthrough. 1. Use `dbSendQuery()` to create a result set object of class DBIResult. 2. Optionally, bind query parameters with `dbBind()` or `dbBindArrow()`. This is required only if the query contains placeholders such as `⁠?⁠` or `⁠\$1⁠`, depending on the database backend. 3. Optionally, use `dbColumnInfo()` to retrieve the structure of the result set without retrieving actual data. 4. Use `dbFetch()` to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards. 5. Use `dbHasCompleted()` to tell when you're done. This method returns `TRUE` if no more rows are available for fetching. 6. Repeat the last four steps as necessary. 7. Use `dbClearResult()` to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use `on.exit()` or `withr::defer()` to ensure that this step is always executed. ### Failure modes An attempt to query columns for a closed result set raises an error. ### Specification A column named `row_names` is treated like any other column. The column names are always consistent with the data returned by `dbFetch()`. If the query returns unnamed columns, non-empty and non-`NA` names are assigned. Column names that correspond to SQL or R keywords are left unchanged. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") rs <- dbSendQuery(con, "SELECT 1 AS a, 2 AS b") dbColumnInfo(rs) dbFetch(rs) dbClearResult(rs) dbDisconnect(con) ``` ## Begin/commit/rollback SQL transactions This section describes the behavior of the following methods: ``` r dbBegin(conn, ...) dbCommit(conn, ...) dbRollback(conn, ...) ``` ### Description A transaction encapsulates several SQL statements in an atomic unit. It is initiated with `dbBegin()` and either made persistent with `dbCommit()` or undone with `dbRollback()`. In any case, the DBMS guarantees that either all or none of the statements have a permanent effect. This helps ensuring consistency of write operations to multiple tables. ### Arguments | | | |--------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `...` | Other parameters passed on to methods. | ### Details Not all database engines implement transaction management, in which case these methods should not be implemented for the specific DBIConnection subclass. ### Value `dbBegin()`, `dbCommit()` and `dbRollback()` return `TRUE`, invisibly. ### Failure modes The implementations are expected to raise an error in case of failure, but this is not tested. In any way, all generics throw an error with a closed or invalid connection. In addition, a call to `dbCommit()` or `dbRollback()` without a prior call to `dbBegin()` raises an error. Nested transactions are not supported by DBI, an attempt to call `dbBegin()` twice yields an error. ### Specification Actual support for transactions may vary between backends. A transaction is initiated by a call to `dbBegin()` and committed by a call to `dbCommit()`. Data written in a transaction must persist after the transaction is committed. For example, a record that is missing when the transaction is started but is created during the transaction must exist both during and after the transaction, and also in a new connection. A transaction can also be aborted with `dbRollback()`. All data written in such a transaction must be removed after the transaction is rolled back. For example, a record that is missing when the transaction is started but is created during the transaction must not exist anymore after the rollback. Disconnection from a connection with an open transaction effectively rolls back the transaction. All data written in such a transaction must be removed after the transaction is rolled back. The behavior is not specified if other arguments are passed to these functions. In particular, RSQLite issues named transactions with support for nesting if the `name` argument is set. The transaction isolation level is not specified by DBI. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cash", data.frame(amount = 100)) dbWriteTable(con, "account", data.frame(amount = 2000)) # All operations are carried out as logical unit: dbBegin(con) withdrawal <- 300 dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) dbCommit(con) dbReadTable(con, "cash") dbReadTable(con, "account") # Rolling back after detecting negative value on account: dbBegin(con) withdrawal <- 5000 dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) if (dbReadTable(con, "account")\$amount >= 0) { dbCommit(con) } else { dbRollback(con) } dbReadTable(con, "cash") dbReadTable(con, "account") dbDisconnect(con) ``` ## Self-contained SQL transactions This section describes the behavior of the following methods: ``` r dbWithTransaction(conn, code, ...) dbBreak() ``` ### Description Given that transactions are implemented, this function allows you to pass in code that is run in a transaction. The default method of `dbWithTransaction()` calls `dbBegin()` before executing the code, and `dbCommit()` after successful completion, or `dbRollback()` in case of an error. The advantage is that you don't have to remember to do `dbBegin()` and `dbCommit()` or `dbRollback()` – that is all taken care of. The special function `dbBreak()` allows an early exit with rollback, it can be called only inside `dbWithTransaction()`. ### Arguments | | | |--------|-------------------------------------------------------| | `conn` | A DBIConnection object, as returned by `dbConnect()`. | | `code` | An arbitrary block of R code. | | `...` | Other parameters passed on to methods. | ### Details DBI implements `dbWithTransaction()`, backends should need to override this generic only if they implement specialized handling. ### Value `dbWithTransaction()` returns the value of the executed code. ### Failure modes Failure to initiate the transaction (e.g., if the connection is closed or invalid of if `dbBegin()` has been called already) gives an error. ### Specification `dbWithTransaction()` initiates a transaction with `dbBegin()`, executes the code given in the `code` argument, and commits the transaction with `dbCommit()`. If the code raises an error, the transaction is instead aborted with `dbRollback()`, and the error is propagated. If the code calls `dbBreak()`, execution of the code stops and the transaction is silently aborted. All side effects caused by the code (such as the creation of new variables) propagate to the calling environment. ### Examples ``` r con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cash", data.frame(amount = 100)) dbWriteTable(con, "account", data.frame(amount = 2000)) # All operations are carried out as logical unit: dbWithTransaction( con, { withdrawal <- 300 dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) } ) # The code is executed as if in the curent environment: withdrawal # The changes are committed to the database after successful execution: dbReadTable(con, "cash") dbReadTable(con, "account") # Rolling back with dbBreak(): dbWithTransaction( con, { withdrawal <- 5000 dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) if (dbReadTable(con, "account")\$amount < 0) { dbBreak() } } ) # These changes were not committed to the database: dbReadTable(con, "cash") dbReadTable(con, "account") dbDisconnect(con) ``` DBI/vignettes/DBI-proposal.Rmd0000644000176200001440000006640614552712323015577 0ustar liggesusers--- title: "A Common Interface to Relational Databases from R and S -- A Proposal" author: "David James" date: "March 16, 2000" output: rmarkdown::html_vignette bibliography: biblio.bib vignette: > %\VignetteIndexEntry{A Common Interface to Relational Databases from R and S -- A Proposal} %\VignetteEngine{knitr::rmarkdown} --- For too long S and similar data analysis environments have lacked good interfaces to relational database systems (RDBMS). For the last twenty years or so these RDBMS have evolved into highly optimized client-server systems for data storage and manipulation, and currently they serve as repositories for most of the business, industrial, and research “raw” data that analysts work with. Other analysis packages, such as SAS, have traditionally provided good data connectivity, but S and GNU R have relied on intermediate text files as means of importing data (but see @R.imp-exp and @R-dbms.) Although this simple approach works well for relatively modest amounts of mostly static data, it does not scale up to larger amounts of data distributed over machines and locations, nor does it scale up to data that is highly dynamic – situations that are becoming increasingly common. We want to propose a common interface between R/S and RDBMS that would allow users to access data stored on database servers in a uniform and predictable manner irrespective of the database engine. The interface defines a small set of classes and methods similar in spirit to Python’s DB-API, Java’s JDBC, Microsoft’s ODBC, Perl’s DBI, etc., but it conforms to the “whole-object” philosophy so natural in S and R. # Computing with Distributed Data {#sec:distr} As data analysts, we are increasingly faced with the challenge of larger data sources distributed over machines and locations; most of these data sources reside in relational database management systems (RDBMS). These relational databases represent a mature client-server distributed technology that we as analysts could be exploiting more that we’ve done in the past. The relational technology provides a well-defined standard, the ANSI SQL-92 @sql92, both for defining and manipulating data in a highly optimized fashion from virtually any application. In contrast, S and Splus have provided somewhat limited tools for coping with the challenges of larger and distributed data sets (Splus does provide an `import` function to import from databases, but it is quite limited in terms of SQL facilities). The R community has been more resourceful and has developed a number of good libraries for connecting to mSQL, MySQL, PostgreSQL, and ODBC; each library, however, has defined its own interface to each database engine a bit differently. We think it would be to everybody’s advantage to coordinate the definition of a common interface, an effort not unlike those taken in the Python and Perl communities. The goal of a common, seamless access to distributed data is a modest one in our evolution towards a fully distributed computing environment. We recognize the greater goal of distributed computing as the means to fully integrate diverse systems – not just databases – into a truly flexible analysis environment. Good connectivity to databases, however, is of immediate necessity both in practical terms and as a means to help us transition from monolithic, self-contained systems to those in which computations, not only the data, can be carried out in parallel over a wide number of computers and/or systems @duncan2000. Issues of reliability, security, location transparency, persistence, etc., will be new to most of us and working with distributed data may provide a more gradual change to ease in the ultimate goal of full distributed computing. # A Common Interface {#sec:rs-dbi} We believe that a common interface to databases can help users easily access data stored in RDBMS. A common interface would describe, in a uniform way, how to connect to RDBMS, extract meta-data (such as list of available databases, tables, etc.) as well as a uniform way to execute SQL statements and import their output into R and S. The current emphasis is on querying databases and not so much in a full low-level interface for database development as in JDBC or ODBC, but unlike these, we want to approach the interface from the “whole-object” perspective @S4 so natural to R/S and Python – for instance, by fetching all fields and records simultaneously into a single object. The basic idea is to split the interface into a front-end consisting of a few classes and generic functions that users invoke and a back-end set of database-specific classes and methods that implement the actual communication. (This is a very well-known pattern in software engineering, and another good verbatim is the device-independent graphics in R/S where graphics functions produce similar output on a variety of different devices, such X displays, Postscript, etc.) The following verbatim shows the front-end: ``` > mgr <- dbManager("Oracle") > con <- dbConnect(mgr, user = "user", passwd = "passwd") > rs <- dbExecStatement(con, "select fld1, fld2, fld3 from MY_TABLE") > tbls <- fetch(rs, n = 100) > hasCompleted(rs) [1] T > close(rs) > rs <- dbExecStatement(con, "select id_name, q25, q50 from liv2") > res <- fetch(rs) > getRowCount(rs) [1] 73 > close(con) ``` Such scripts should work with other RDBMS (say, MySQL) by replacing the first line with ``` > mgr <- dbManager("MySQL") ``` ## Interface Classes {#sec:rs-dbi-classes} The following are the main RS-DBI classes. They need to be extended by individual database back-ends (MySQL, Oracle, etc.) `dbManager` : Virtual class[^2] extended by actual database managers, e.g., Oracle, MySQL, Informix. `dbConnection` : Virtual class that captures a connection to a database instance[^3]. `dbResult` : Virtual class that describes the result of an SQL statement. `dbResultSet` : Virtual class, extends `dbResult` to fully describe the output of those statements that produce output records, i.e., `SELECT` (or `SELECT`-like) SQL statement. All these classes should implement the methods `show`, `describe`, and `getInfo`: `show` : (`print` in R) prints a one-line identification of the object. `describe` : prints a short summary of the meta-data of the specified object (like `summary` in R/S). `getInfo` : takes an object of one of the above classes and a string specifying a meta-data item, and it returns the corresponding information (`NULL` if unavailable). > mgr <- dbManager("MySQL") > getInfo(mgr, "version") > con <- dbConnect(mgr, ...) > getInfo(con, "type") The reason we implement the meta-data through `getInfo` in this way is to simplify the writing of database back-ends. We don’t want to overwhelm the developers of drivers (ourselves, most likely) with hundreds of methods as in the case of JDBC. In addition, the following methods should also be implemented: `getDatabases` : lists all available databases known to the `dbManager`. `getTables` : lists tables in a database. `getTableFields` : lists the fields in a table in a database. `getTableIndices` : lists the indices defined for a table in a database. These methods may be implemented using the appropriate `getInfo` method above. In the next few sections we describe in detail each of these classes and their methods. ### Class `dbManager` {#sec:dbManager} This class identifies the relational database management system. It needs to be extended by individual back-ends (Oracle, PostgreSQL, etc.) The `dbManager` class defines the following methods: `load` : initializes the driver code. We suggest having the generator, `dbManager(driver)`, automatically load the driver. `unload` : releases whatever resources the driver is using. `getVersion` : returns the version of the RS-DBI currently implemented, plus any other relevant information about the implementation itself and the RDBMS being used. ### Class `dbConnection` {#sec:dbConnection} This virtual class captures a connection to a RDBMS, and it provides access to dynamic SQL, result sets, RDBMS session management (transactions), etc. Note that the `dbManager` may or may not allow multiple simultaneous connections. The methods it defines include: `dbConnect` : opens a connection to the database `dbname`. Other likely arguments include `host`, `user`, and `password`. It returns an object that extends `dbConnection` in a driver-specific manner (e.g., the MySQL implementation creates a connection of class `MySQLConnection` that extends `dbConnection`). Note that we could separate the steps of connecting to a RDBMS and opening a database there (i.e., opening an *instance*). For simplicity we do the 2 steps in this method. If the user needs to open another instance in the same RDBMS, just open a new connection. `close` : closes the connection and discards all pending work. `dbExecStatement` : submits one SQL statement. It returns a `dbResult` object, and in the case of a `SELECT` statement, the object also inherits from `dbResultSet`. This `dbResultSet` object is needed for fetching the output rows of `SELECT` statements. The result of a non-`SELECT` statement (e.g., `UPDATE, DELETE, CREATE, ALTER`, ...) is defined as the number of rows affected (this seems to be common among RDBMS). `commit` : commits pending transaction (optional). `rollback` : undoes current transaction (optional). `callProc` : invokes a stored procedure in the RDBMS (tentative). Stored procedures are *not* part of the ANSI SQL-92 standard and possibly vary substantially from one RDBMS to another. For instance, Oracle seems to have a fairly decent implementation of stored procedures, but MySQL currently does not support them. `dbExec` : submit an SQL “script” (multiple statements). May be implemented by looping with `dbExecStatement`. `dbNextResultSet` : When running SQL scripts (multiple statements), it closes the current result set in the `dbConnection`, executes the next statement and returns its result set. ### Class `dbResult` {#sec:dbResult} This virtual class describes the result of an SQL statement (any statement) and the state of the operation. Non-query statements (e.g., `CREATE`, `UPDATE`, `DELETE`) set the “completed” state to 1, while `SELECT` statements to 0. Error conditions set this slot to a negative number. The `dbResult` class defines the following methods: `getStatement` : returns the SQL statement associated with the result set. `getDBConnection` : returns the `dbConnection` associated with the result set. `getRowsAffected` : returns the number of rows affected by the operation. `hasCompleted` : was the operation completed? `SELECT`’s, for instance, are not completed until their output rows are all fetched. `getException` : returns the status of the last SQL statement on a given connection as a list with two members, status code and status description. ### Class `dbResultSet` {#sec:dbResultSet} This virtual class extends `dbResult`, and it describes additional information from the result of a `SELECT` statement and the state of the operation. The `completed` state is set to 0 so long as there are pending rows to fetch. The `dbResultSet` class defines the following additional methods: `getRowCount` : returns the number of rows fetched so far. `getNullOk` : returns a logical vector with as many elements as there are fields in the result set, each element describing whether the corresponding field accepts `NULL` values. `getFields` : describes the `SELECT`ed fields. The description includes field names, RDBMS internal data types, internal length, internal precision and scale, null flag (i.e., column allows `NULL`’s), and corresponding S classes (which can be over-ridden with user-provided classes). The current MySQL and Oracle implementations define a `dbResultSet` as a named list with the following elements: `connection`: : the connection object associated with this result set; `statement`: : a string with the SQL statement being processed; `description`: : a field description `data.frame` with as many rows as there are fields in the `SELECT` output, and columns specifying the `name`, `type`, `length`, `precision`, `scale`, `Sclass` of the corresponding output field. `rowsAffected`: : the number of rows that were affected; `rowCount`: : the number of rows so far fetched; `completed`: : a logical value describing whether the operation has completed or not. `nullOk`: : a logical vector specifying whether the corresponding column may take NULL values. The methods above are implemented as accessor functions to this list in the obvious way. `setDataMappings` : defines a conversion between internal RDBMS data types and R/S classes. We expect the default mappings to be by far the most common ones, but users that need more control may specify a class generator for individual fields in the result set. (See Section [sec:mappings] for details.) `close` : closes the result set and frees resources both in R/S and the RDBMS. `fetch` : extracts the next `max.rec` records (-1 means all). ## Data Type Mappings {#sec:mappings} The data types supported by databases are slightly different than the data types in R and S, but the mapping between them is straightforward: Any of the many fixed and varying length character types are mapped to R/S `character`. Fixed-precision (non-IEEE) numbers are mapped into either doubles (`numeric`) or long (`integer`). Dates are mapped to character using the appropriate `TO_CHAR` function in the RDBMS (which should take care of any locale information). Some RDBMS support the type `CURRENCY` or `MONEY` which should be mapped to `numeric`. Large objects (character, binary, file, etc.) also need to be mapped. User-defined functions may be specified to do the actual conversion as follows: 1. run the query (either with `dbExec` or `dbExecStatement`): > rs <- dbExecStatement(con, "select whatever-You-need") 2. extract the output field definitions > flds <- getFields(rs) 3. replace the class generator in the, say 3rd field, by the user own generator: > flds[3, "Sclass"] # default mapping [1] "character" by > flds[3, "Sclass"] <- "myOwnGeneratorFunction" 4. set the new data mapping prior to fetching > setDataMappings(resutlSet, flds) 5. fetch the rows and store in a `data.frame` > data <- fetch(resultSet) ## Open Issues {#sec:open-issues} We may need to provide some additional utilities, for instance to convert dates, to escape characters such as quotes and slashes in query strings, to strip excessive blanks from some character fields, etc. We need to decide whether we provide hooks so these conversions are done at the C level, or do all the post-processing in R or S. Another issue is what kind of data object is the output of an SQL query. Currently the MySQL and Oracle implementations return data as a `data.frame`; data frames have the slight inconvenience that they automatically re-label the fields according to R/S syntax, changing the actual RDBMS labels of the variables; the issue of non-numeric data being coerced into factors automatically “at the drop of a hat” (as someone in s-news wrote) is also annoying. The execution of SQL scripts is not fully described. The method that executes scripts could run individual statements without returning until it encounters a query (`SELECT`-like) statement. At that point it could return that one result set. The application is then responsible for fetching these rows, and then for invoking `dbNextResultSet` on the opened `dbConnection` object to repeat the `dbExec`/`fetch` loop until it encounters the next `dbResultSet`. And so on. Another (potentially very expensive) alternative would be to run all statements sequentially and return a list of `data.frame`s, each element of the list storing the result of each statement. Binary objects and large objects present some challenges both to R and S. It is becoming more common to store images, sounds, and other data types as binary objects in RDBMS, some of which can be in principle quite large. The SQL-92 ANSI standard allows up to 2 gigabytes for some of these objects. We need to carefully plan how to deal with binary objects – perhaps tentatively not in full generality. Large objects could be fetched by repeatedly invoking a specified R/S function that takes as argument chunks of a specified number of raw bytes. In the case of S4 (and Splus5.x) the RS-DBI implementation can write into an opened connection for which the user has defined a reader (but can we guarantee that we won’t overflow the connection?). In the case of R it is not clear what data type binary large objects (BLOB) should be mapped into. ## Limitations {#sec:limitations} These are some of the limitations of the current interface definition: - we only allow one SQL statement at a time, forcing users to split SQL scripts into individual statements; - transaction management is not fully described; - the interface is heavily biased towards queries, as opposed to general purpose database development. In particular we made no attempt to define “bind variables”; this is a mechanism by which the contents of S objects are implicitly moved to the database during SQL execution. For instance, the following embedded SQL statement /* SQL */ SELECT * from emp_table where emp_id = :sampleEmployee would take the vector `sampleEmployee` and iterate over each of its elements to get the result. Perhaps RS-DBI could at some point in the future implement this feature. # Other Approaches The high-level, front-end description of RS-DBI is the more critical aspect of the interface. Details on how to actually implement this interface may change over time. The approach described in this document based on one back-end driver per RDBMS is reasonable, but not the only approach – we simply felt that a simpler approach based on well-understood and self-contained tools (R, S, and C API’s) would be a better start. Nevertheless we want to briefly mention a few alternatives that we considered and tentatively decided against, but may quite possibly re-visit in the near future. ## Open Database Connectivity (ODBC) {#sec:odbc} The ODBC protocol was developed by Microsoft to allow connectivity among C/C++ applications and RDBMS. As you would expect, originally implementations of the ODBC were only available under Windows environments. There are various effort to create a Unix implementation (see [the Unix ODBC](https://www.unixodbc.org/) web-site and @odbc.lj). This approach looks promising because it allows us to write only one back-end, instead of one per RDBMS. Since most RDBMS already provide ODBC drivers, this could greatly simplify development. Unfortunately, the Unix implementation of ODBC was not mature enough at the time we looked at it, a situation we expect will change in the next year or so. At that point we will need to re-evaluate it to make sure that such an ODBC interface does not penalize the interface in terms of performance, ease of use, portability among the various Unix versions, etc. ## Java Database Connectivity (JDBC) {#sec:jdbc} Another protocol, the Java database connectivity, is very well-done and supported by just about every RDBMS. The issue with JDBC is that as of today neither S nor R (which are written in C) interfaces cleanly with Java. There are several efforts (some in a quite fairly advanced state) to allow S and R to invoke Java methods. Once this interface is widely available in Splus5x and R we will need to re-visit this issue again and study the performance, usability, etc., of JDBC as a common back-end to the RS-DBI. ## CORBA and a 3-tier Architecture {#sec:corba} Yet another approach is to move the interface to RDBMS out of R and S altogether into a separate system or server that would serve as a proxy between R/S and databases. The communication to this middle-layer proxy could be done through CORBA [@s-corba.98, @corba:siegel.96], Java’s RMI, or some other similar technology. Such a design could be very flexible, but the CORBA facilities both in R and S are not widely available yet, and we do not know whether this will be made available to Splus5 users from MathSoft. Also, my experience with this technology is rather limited. On the other hand, this 3-tier architecture seem to offer the most flexibility to cope with very large distributed databases, not necessarily relational. # Resources {#sec:resources} The latest documentation and software on the RS-DBI was available at www.omegahat.net (link dead now: `https://www.omegahat.net/contrib/RS-DBI/index.html`). The R community has developed interfaces to some databases: [RmSQL](https://cran.r-project.org/src/contrib/Archive/RmSQL/) is an interface to the [mSQL](https://www.hughes.com.au/) database written by Torsten Hothorn; [RPgSQL](https://sites.cns.utexas.edu/keittlab/software-0) is an interface to [PostgreSQL](https://www.postgreSQL.org) and was written by Timothy H. Keitt; [RODBC](https://www.stats.ox.ac.uk/pub/bdr/) is an interface to ODBC, and it was written by [Michael Lapsley](mailto:mlapsley@sthelier.sghms.ac.uk). (For more details on all these see @R.imp-exp.) The are R and S-Plus interfaces to [MySQL](https://dev.mysql.com/) that follow the propose RS-DBI API described here; also, there’s an S-Plus interface SOracle @RS-Oracle to Oracle (we expect to have an R implementation soon.) The idea of a common interface to databases has been successfully implemented in Java’s Database Connectivity (JDBC) ([www.javasoft.com](https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/)), in C through the Open Database Connectivity (ODBC) ([www.unixodbc.org](https://www.unixodbc.org/)), in Python’s Database Application Programming Interface ([www.python.org](https://www.python.org)), and in Perl’s Database Interface ([www.cpan.org](https://www.cpan.org)). # Acknowledgements The R/S database interface came about from suggestions, comments, and discussions with [John M. Chambers](mailto:jmc@research.bell-labs.com) and [Duncan Temple Lang](mailto:duncan@research.bell-labs.com) in the context of the Omega Project for Statistical Computing. [Doug Bates](mailto:bates@stat.wisc.edu) and [Saikat DebRoy](mailto:saikat@stat.wisc.edu) ported (and greatly improved) the first MySQL implementation to R. # The S Version 4 Definitions The following code is meant to serve as a detailed description of the R/S to database interface. We decided to use S4 (instead of R or S version 3) because its clean syntax help us to describe easily the classes and methods that form the RS-DBI, and also to convey the inter-class relationships. ```R ## Define all the classes and methods to be used by an ## implementation of the RS-DataBase Interface. Mostly, ## these classes are virtual and each driver should extend ## them to provide the actual implementation. ## Class: dbManager ## This class identifies the DataBase Management System ## (Oracle, MySQL, Informix, PostgreSQL, etc.) setClass("dbManager", VIRTUAL) setGeneric("load", def = function(dbMgr,...) standardGeneric("load") ) setGeneric("unload", def = function(dbMgr,...) standardGeneric("unload") ) setGeneric("getVersion", def = function(dbMgr,...) standardGeneric("getVersion") ) ## Class: dbConnections ## This class captures a connection to a database instance. setClass("dbConnection", VIRTUAL) setGeneric("dbConnection", def = function(dbMgr, ...) standardGeneric("dbConnection") ) setGeneric("dbConnect", def = function(dbMgr, ...) standardGeneric("dbConnect") ) setGeneric("dbExecStatement", def = function(con, statement, ...) standardGeneric("dbExecStatement") ) setGeneric("dbExec", def = function(con, statement, ...) standardGeneric("dbExec") ) setGeneric("getResultSet", def = function(con, ..) standardGeneric("getResultSet") ) setGeneric("commit", def = function(con, ...) standardGeneric("commit") ) setGeneric("rollback", def = function(con, ...) standardGeneric("rollback") ) setGeneric("callProc", def = function(con, ...) standardGeneric("callProc") ) setMethod("close", signature = list(con="dbConnection", type="missing"), def = function(con, type) NULL ) ## Class: dbResult ## This is a base class for arbitrary results from the RDBMS ## (INSERT, UPDATE, DELETE). SELECTs (and SELECT-like) ## statements produce "dbResultSet" objects, which extend ## dbResult. setClass("dbResult", VIRTUAL) setMethod("close", signature = list(con="dbResult", type="missing"), def = function(con, type) NULL ) ## Class: dbResultSet ## Note that we define a resultSet as the result of a ## SELECT SQL statement. setClass("dbResultSet", "dbResult") setGeneric("fetch", def = function(resultSet,n,...) standardGeneric("fetch") ) setGeneric("hasCompleted", def = function(object, ...) standardGeneric("hasCompleted") ) setGeneric("getException", def = function(object, ...) standardGeneric("getException") ) setGeneric("getDBconnection", def = function(object, ...) standardGeneric("getDBconnection") ) setGeneric("setDataMappings", def = function(resultSet, ...) standardGeneric("setDataMappings") ) setGeneric("getFields", def = function(object, table, dbname, ...) standardGeneric("getFields") ) setGeneric("getStatement", def = function(object, ...) standardGeneric("getStatement") ) setGeneric("getRowsAffected", def = function(object, ...) standardGeneric("getRowsAffected") ) setGeneric("getRowCount", def = function(object, ...) standardGeneric("getRowCount") ) setGeneric("getNullOk", def = function(object, ...) standardGeneric("getNullOk") ) ## Meta-data: setGeneric("getInfo", def = function(object, ...) standardGeneric("getInfo") ) setGeneric("describe", def = function(object, verbose=F, ...) standardGeneric("describe") ) setGeneric("getCurrentDatabase", def = function(object, ...) standardGeneric("getCurrentDatabase") ) setGeneric("getDatabases", def = function(object, ...) standardGeneric("getDatabases") ) setGeneric("getTables", def = function(object, dbname, ...) standardGeneric("getTables") ) setGeneric("getTableFields", def = function(object, table, dbname, ...) standardGeneric("getTableFields") ) setGeneric("getTableIndices", def = function(object, table, dbname, ...) standardGeneric("getTableIndices") ) ``` [^2]: A virtual class allows us to group classes that share some common functionality, e.g., the virtual class “`dbConnection`” groups all the connection implementations by Informix, Ingres, DB/2, Oracle, etc. Although the details will vary from one RDBMS to another, the defining characteristic of these objects is what a virtual class captures. R and S version 3 do not explicitly define virtual classes, but they can easily implement the idea through inheritance. [^3]: The term “database” is sometimes (confusingly) used both to denote the RDBMS, such as Oracle, MySQL, and also to denote a particular database instance under a RDBMS, such as “opto” or “sales” databases under the same RDBMS. DBI/vignettes/biblio.bib0000644000176200001440000001772214350241735014613 0ustar liggesusers@string{jcgs="Journal of Computational and Graphical Statistics"} @inproceedings{s-corba.98, author = "Chambers, John M. and Hansen, Mark H. and James, David A. and Temple Lang, Duncan", title = "Distributed Computing with Data: A CORBA-based Approach", booktitle = "Computing Science and Statistics", year = 1998, organization = "Inteface Foundation of North America" } @book{S.88, author = "Becker, R. A. and Chambers, J. M. and Wilks, A. R", year = "1988", title = "The New S Language", publisher = "Wadsworth", address = "Pacific Grove, California" } @book{S.92, editor = "Chambers, J. M. and Hastie, T.", year = 1992, title = "Statistical Models in S", publisher = "Wadsworth", address = "Pacific Grove, California" } @book{S4, author = "Chambers, J. M.", title = "Programming with Data: A Guide to the S Language", publisher = "Springer", address = "New York", year = 1998 } @article{R.96, author = "Ihaka, Ross and Gentleman, Robert", title = "R: A Language for Data Analysis and Graphics", journal = jcgs, volume = 5, number = 3, year = 1996, pages = "299-314" } @book{corba:siegel.96, author = "Siegel, Jon", title = "CORBA Fundamentals and Programming", publisher = "Wiley", address = "New York", year = 1996 } @book{pvm, title = "PVM: Parallel Virtual Machine. A User's Guide and Tutorial for Networked Parallel Computing", author="Geist, A. and Beguelin, A. and Dongarra, J. and Jiang, W. and Mancheck, R. and Sunderam, V.", year = 1994, publisher = "MIT Press", address = "Cambridge, MA" } @manual{splus, title = "S-PLUS Software Documentation", key = "S-PLUS", organization = "StatSci Division of MathSoft Inc.", note = "Version 3.3", year = 1995, address = "Seattle, WA", } @book{tierney.90, author = "Tierney, Luke", year = 1990, title = "LISP-STAT: An Object-Oriented Environment for Statistical Computing and Dynamic Graphics", publisher = "Wiley", address = "New York" } @article{tierney.96, author = "Tierney, Luke", title = "Recent Development and Future Directions in {LispStat}", journal = jcgs, volume = 5, number = 3, year = 1996, pages = "250-262" } @article{odbc.lj, author = "Harvey, Peter", title = "{Open Database Connectivity}", journal = "{Linux Journal}", year = 1999, volume = "Nov.", number = 67, pages = "68-72" } @article{duncan2000, author = "Temple Lang, Duncan", title = "{The Omegahat Environment: New Possibilities for Statistical Computing}", journal = jcgs, volume = "to appear", year = 2000, number = "" } @manual{sql92, title = "{X/Open CAE Specification: SQL and RDA}", organization = "X/Open Company Ltd.", address = "Reading, UK", year = 1994 } @book{MySQL, author = "DuBois, Paul", title = "{MySQL}", publisher = "New Riders Publishing", year = 2000 } @manual{R.ext, title = "Writing {R} Extensions", organization = "{R} Development Core Team", note = "Version 1.2.1 (2001-01-15)", year = 2001 } @manual{R.imp-exp, title = "{R} Data Import/Export", organization = "R-Development Core Team", note = "Version 1.2.1 (2001-01-15)", year = 2001 } @manual{R-dbms, title = "Using Relational Database Systems with {R}", organization = "R-Developemt Core Team", note = "Draft", year = 2000 } @manual{bates.mysql, title = "Using Relational Database Systems with {R}", organization = "R-Developemt Core Team", note = "Draft", year = 2000 } @techreport{proxyDBMS, author = "James, David A.", title = "Proxy Database Object in the S Language", institution = "Bell Labs, Lucent Technologies", year = "In preparation" } @techreport{RS-DBI, author = "James, David A.", title = "A Common Interface to Relational Database Management Sysmtems from {R} and {S} --- A Proposal", institution = "Bell Labs, Lucent Technologies", year = "2000", address = "www.omegahat.org" } @techreport{RS-MySQL, author = "James, David A.", title = "An {R}/{S} Interface to the {MySQL} Database", institution = "Bell Labs, Lucent Technologies", year = "2001", address = "www.omegahat.org" } @techreport{RS-Oracle, author = "James, David A.", title = "An {R}/{S} Interface to the {Oracle} Database", institution = "Bell Labs, Lucent Technologies", year = "In preparation", address = "www.omegahat.org" } @manual{r-data-imp:2001, author = {R Development Core Team}, title = {R Data Import/Export}, year = {2001}, address = {\url{https://www.r-project.org}} } @manual{mysql:2000, author = "Axmark, David and Widenius, Michael and Cole, Jeremy and DuBois, Paul", title = {MySQL Reference Manual}, year = {2001}, address = {\url{https://www.mysql.com/documentation/mysql}} } @manual{jdbc:2000, author = "Ellis, Jon and Ho, Linda and Fisher, Maydene", title = {JDBC 3.0 Specification}, organization = {Sun Microsystems, Inc}, year = {2000}, address = {\url{https://java.sun.com/Download4}} } @article{using-data:2001, author = "Ripley, Brian D.", title = {Using Databases with {R}}, journal = {R {N}ews}, year = {2001}, month = {January}, volume = {1}, number = {1}, pages = {18--20}, address = {\url{https://www.r-project.org/doc/Rnews/}} } @Manual{odbc:2001, title = {Microsoft {ODBC}}, organization = {Microsoft Inc}, address = {\url{https://www.microsoft.com/data/odbc/}}, year = 2001 } @Book{PerlDBI:2000, author = "Descartes, Alligator and Bunce, Tim", title = {Programming the {P}erl {DBI}}, publisher = {O'Reilly}, year = 2000 } @Book{Reese:2000, author = "Reese, George", title = {Database Programming with {JDBC} and {J}ava}, publisher = {O'Reilly}, year = 2000, edition = {second} } @book{Xopen-sql, author = {X/Open Company Ltd.}, title = {X/Open SQL and RDA Specification}, publisher = {X/Open Company Ltd.}, year = 1994 } @book{mysql-dubois, author = "DuBois, Paul", title = {MySQL}, publisher = {New Riders}, year = 2000 } @techreport{data-management:1991, author = "Chambers, John M.", title = {Data Management in {S}}, institution = {Bell Labs, Lucent Technologies}, year = 1991 } @techreport{database-classes:1999, author = "Chambers, John M.", title = {Database Classes}, institution = {Bell Labs, Lucent Technologies}, year = 1998 } @inproceedings{R-dcom, author = "Neuwirth, Erich and Baier, Thomas", title = {Embedding {R} in Standard Software, and the other way around}, organization = {Vienna University of Technology}, year = 2001, booktitle = {Proceedings of the Distributed Statistical Computing 2001 Workshop}, address = {\url{http://www.ci.tuwien.ac.at/Conferences/DSC-2001}} } @inproceedings{R-tcltk, author = "Dalgaard, Peter", title = {The {R}-{T}cl/{T}k Interface}, organization = {Vienna University of Technology}, year = 2001, booktitle = {Proceedings of the Distributed Statistical Computing 2001 Workshop}, address = {\url{http://www.ci.tuwien.ac.at/Conferences/DSC-2001}} } @inproceedings{duncan-dsc2001, author = "Temple Lang, Duncan", title = {Embedding {S} in Other Languages and Environments}, organization = {Vienna University of Technology}, year = 2001, booktitle = {Proceedings of the Distributed Statistical Computing 2001 Workshop}, address = {\url{http://www.ci.tuwien.ac.at/Conferences/DSC-2001}} } @inproceedings{BDR-RMR, author = "Ripley, B. D. and Ripley, R. M.", title = {Applications of {R} Clients and Servers}, organization = {Vienna University of Technology}, year = 2001, booktitle = {Proceedings of the Distributed Statistical Computing 2001 Workshop}, address = {\url{http://www.ci.tuwien.ac.at/Conferences/DSC-2001}} } @inproceedings{rsdbi-dsc2001, author = "Hothorn, Torsten and James, David A. and Ripley, Brian D.", title = {{R}/{S} Interfaces to Databases}, organization = {Vienna University of Technology}, year = 2001, booktitle = {Proceedings of the Distributed Statistical Computing 2001 Workshop}, address = {\url{http://www.ci.tuwien.ac.at/Conferences/DSC-2001}} } DBI/vignettes/DBI-arrow.Rmd0000644000176200001440000001517214552712323015064 0ustar liggesusers--- title: "Using DBI with Arrow" author: "Kirill Müller" date: "25/12/2023" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{Using DBI with Arrow} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r setup, include=FALSE} library(knitr) opts_chunk$set(echo = TRUE) knitr::opts_chunk$set(error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5")) knit_print.data.frame <- function(x, ...) { print(head(x, 6)) if (nrow(x) > 6) { cat("Showing 6 out of", nrow(x), "rows.\n") } invisible(x) } registerS3method("knit_print", "data.frame", "knit_print.data.frame") ``` ## Who this tutorial is for This tutorial is for you if you want to leverage [Apache Arrow](https://arrow.apache.org/) for accessing and manipulating data on databases. See `vignette("DBI", package = "DBI")` and `vignette("DBI-advanced", package = "DBI")` for tutorials on accessing data using R's data frames instead of Arrow's structures. ## Rationale Apache Arrow is > a cross-language development platform for in-memory analytics, suitable for large and huge data, with support for out-of-memory operation. Arrow is also a data exchange format, the data types covered by Arrow align well with the data types supported by SQL databases. DBI 1.2.0 introduced support for Arrow as a format for exchanging data between R and databases. The aim is to: - accelerate data retrieval and loading, by using fewer costly data conversions; - better support reading and summarizing data from a database that is larger than memory; - provide better type fidelity with workflows centered around Arrow. This allows existing code to be used with Arrow, and it allows new code to be written that is more efficient and more flexible than code that uses R's data frames. The interface is built around the {nanoarrow} R package, with `nanoarrow::as_nanoarrow_array` and `nanoarrow::as_nanoarrow_array_stream` as fundamental data structures. ## New classes and generics DBI 1.2.0 introduces new classes and generics for working with Arrow data: - `dbReadTableArrow()` - `dbWriteTableArrow()` - `dbCreateTableArrow()` - `dbAppendTableArrow()` - `dbGetQueryArrow()` - `dbSendQueryArrow()` - `dbBindArrow()` - `dbFetchArrow()` - `dbFetchArrowChunk()` - `DBIResultArrow-class` - `DBIResultArrowDefault-class` Compatibility is important for DBI, and implementing new generics and classes greatly reduces the risk of breaking existing code. The DBI package comes with a fully functional fallback implementation for all existing DBI backends. The fallback is not improving performance, but it allows existing code to be used with Arrow before switching to a backend with native Arrow support. Backends with native support, like the [adbi](https://adbi.r-dbi.org/) package, implement the new generics and classes for direct support and improved performance. In the remainder of this tutorial, we will demonstrate the new generics and classes using the RSQLite package. SQLite is an in-memory database, this code does not need a database server to be installed and running. ## Prepare We start by setting up a database connection and creating a table with some data, using the original `dbWriteTable()` method. ```{r} library(DBI) con <- dbConnect(RSQLite::SQLite()) data <- data.frame( a = 1:3, b = 4.5, c = "five" ) dbWriteTable(con, "tbl", data) ``` ## Read all rows from a table The `dbReadTableArrow()` method reads all rows from a table into an Arrow stream, similarly to `dbReadTable()`. Arrow objects implement the `as.data.frame()` method, so we can convert the stream to a data frame. ```{r} stream <- dbReadTableArrow(con, "tbl") stream as.data.frame(stream) ``` ## Run queries The `dbGetQueryArrow()` method runs a query and returns the result as an Arrow stream. This stream can be turned into an `arrow::RecordBatchReader` object and processed further, without bringing it into R. ```{r} stream <- dbGetQueryArrow(con, "SELECT COUNT(*) AS n FROM tbl WHERE a < 3") stream path <- tempfile(fileext = ".parquet") arrow::write_parquet(arrow::as_record_batch_reader(stream), path) arrow::read_parquet(path) ``` ## Prepared queries The `dbGetQueryArrow()` method supports prepared queries, using the `params` argument which accepts a data frame or a list. ```{r} params <- data.frame(a = 3L) stream <- dbGetQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a", params = params) as.data.frame(stream) params <- data.frame(a = c(2L, 4L)) # Equivalent to dbBind() stream <- dbGetQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a", params = params) as.data.frame(stream) ``` ## Manual flow For the manual flow, use `dbSendQueryArrow()` to send a query to the database, and `dbFetchArrow()` to fetch the result. This also allows using the new `dbBindArrow()` method to bind data in Arrow format to a prepared query. Result objects must be cleared with `dbClearResult()`. ```{r} rs <- dbSendQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a") in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 1L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 2L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 3L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 1:4L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) dbClearResult(rs) ``` ## Writing data Streams returned by `dbGetQueryArrow()` and `dbReadTableArrow()` can be written to a table using `dbWriteTableArrow()`. ```{r} stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a < 3") dbWriteTableArrow(con, "tbl_new", stream) dbReadTable(con, "tbl_new") ``` ## Appending data For more control over the writing process, use `dbCreateTableArrow()` and `dbAppendTableArrow()`. ```{r} stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a < 3") dbCreateTableArrow(con, "tbl_split", stream) dbAppendTableArrow(con, "tbl_split", stream) stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a >= 3") dbAppendTableArrow(con, "tbl_split", stream) dbReadTable(con, "tbl_split") ``` ## Conclusion Do not forget to disconnect from the database when done. ```{r} dbDisconnect(con) ``` That concludes the major features of DBI's new Arrow interface. For more details on the library functions covered in this tutorial see the DBI specification at `vignette("spec", package = "DBI")`. See the [adbi](https://adbi.r-dbi.org/) package for a backend with native Arrow support, and [nanoarrow](https://github.com/apache/arrow-nanoarrow) and [arrow](https://arrow.apache.org/docs/r/) for packages to work with the Arrow format. DBI/vignettes/backend.Rmd0000644000176200001440000002414014350241735014720 0ustar liggesusers --- title: "Implementing a new backend" author: "Hadley Wickham, Kirill Müller" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{Implementing a new backend} %\VignetteEngine{knitr::rmarkdown} \usepackage[utf8]{inputenc} --- ```{r, echo = FALSE} library(DBI) knitr::opts_chunk$set(collapse = TRUE, comment = "#>") ``` The goal of this document is to help you implement a new backend for DBI. If you are writing a package that connects a database to R, I highly recommend that you make it DBI compatible because it makes your life easier by spelling out exactly what you need to do. The consistent interface provided by DBI makes it easier for you to implement the package (because you have fewer arbitrary choices to make), and easier for your users (because it follows a familiar pattern). In addition, the `DBItest` package provides test cases which you can easily incorporate in your package. I'll illustrate the process using a fictional database called Kazam. ## Getting started Start by creating a package. It's up to you what to call the package, but following the existing pattern of `RSQLite`, `RMySQL`, `RPostgres` and `ROracle` will make it easier for people to find it. For this example, I'll call my package `RKazam`. A ready-to-use template package is available at https://github.com/r-dbi/RKazam/. You can start by creating a new GitHub repository from this template, or by copying the package code. Rename "Kazam" to your desired name everywhere. The template package already contains dummy implementations for all classes and methods. If you chose to create the package manually, make sure to include in your `DESCRIPTION`: ```yaml Imports: DBI (>= 0.3.0), methods Suggests: DBItest, testthat ``` Importing `DBI` is fine, because your users are not supposed to *attach* your package anyway; the preferred method is to attach `DBI` and use explicit qualification via `::` to access the driver in your package (which needs to be done only once). ## Testing Why testing at this early stage? Because testing should be an integral part of the software development cycle. Test right from the start, add automated tests as you go, finish faster (because tests are automated) while maintaining superb code quality (because tests also check corner cases that you might not be aware of). Don't worry: if some test cases are difficult or impossible to satisfy, or take too long to run, you can just turn them off. Take the time now to head over to the `DBItest` vignette at `vignette("test", package = "DBItest")`. You will find a vast amount of ready-to-use test cases that will help you in the process of implementing your new DBI backend. Add custom tests that are not covered by `DBItest` at your discretion, or enhance `DBItest` and file a pull request if the test is generic enough to be useful for many DBI backends. ## Driver Start by making a driver class which inherits from `DBIDriver`. This class doesn't need to do anything, it's just used to dispatch other generics to the right method. Users don't need to know about this, so you can remove it from the default help listing with `@keywords internal`: ```{r} #' Driver for Kazam database. #' #' @keywords internal #' @export #' @import DBI #' @import methods setClass("KazamDriver", contains = "DBIDriver") ``` The driver class was more important in older versions of DBI, so you should also provide a dummy `dbUnloadDriver()` method. ```{r} #' @export #' @rdname Kazam-class setMethod("dbUnloadDriver", "KazamDriver", function(drv, ...) { TRUE }) ``` If your package needs global setup or tear down, do this in the `.onLoad()` and `.onUnload()` functions. You might also want to add a show method so the object prints nicely: ```{r} setMethod("show", "KazamDriver", function(object) { cat("\n") }) ``` Next create `Kazam()` which instantiates this class. ```{r} #' @export Kazam <- function() { new("KazamDriver") } Kazam() ``` ## Connection Next create a connection class that inherits from `DBIConnection`. This should store all the information needed to connect to the database. If you're talking to a C api, this will include a slot that holds an external pointer. ```{r} #' Kazam connection class. #' #' @export #' @keywords internal setClass("KazamConnection", contains = "DBIConnection", slots = list( host = "character", username = "character", # and so on ptr = "externalptr" ) ) ``` Now you have some of the boilerplate out of the way, you can start work on the connection. The most important method here is `dbConnect()` which allows you to connect to a specified instance of the database. Note the use of `@rdname Kazam`. This ensures that `Kazam()` and the connect method are documented together. ```{r} #' @param drv An object created by \code{Kazam()} #' @rdname Kazam #' @export #' @examples #' \dontrun{ #' db <- dbConnect(RKazam::Kazam()) #' dbWriteTable(db, "mtcars", mtcars) #' dbGetQuery(db, "SELECT * FROM mtcars WHERE cyl == 4") #' } setMethod("dbConnect", "KazamDriver", function(drv, ...) { # ... new("KazamConnection", host = host, ...) }) ``` * Replace `...` with the arguments needed to connect to your database. You'll always need to include `...` in the arguments, even if you don't use it, for compatibility with the generic. * This is likely to be where people first come for help, so the examples should show how to connect to the database, and how to query it. (Obviously these examples won't work yet.) Ideally, include examples that can be run right away (perhaps relying on a publicly hosted database), but failing that surround in `\dontrun{}` so people can at least see the code. Next, implement `show()` and `dbDisconnect()` methods. ## Results Finally, you're ready to implement the meat of the system: fetching results of a query into a data frame. First define a results class: ```{r} #' Kazam results class. #' #' @keywords internal #' @export setClass("KazamResult", contains = "DBIResult", slots = list(ptr = "externalptr") ) ``` Then write a `dbSendQuery()` method. This takes a connection and SQL string as arguments, and returns a result object. Again `...` is needed for compatibility with the generic, but you can add other arguments if you need them. ```{r} #' Send a query to Kazam. #' #' @export #' @examples #' # This is another good place to put examples setMethod("dbSendQuery", "KazamConnection", function(conn, statement, ...) { # some code new("KazamResult", ...) }) ``` Next, implement `dbClearResult()`, which should close the result set and free all resources associated with it: ```{r} #' @export setMethod("dbClearResult", "KazamResult", function(res, ...) { # free resources TRUE }) ``` The hardest part of every DBI package is writing the `dbFetch()` method. This needs to take a result set and (optionally) number of records to return, and create a dataframe. Mapping R's data types to those of your database may require a custom implementation of the `dbDataType()` method for your connection class: ```{r} #' Retrieve records from Kazam query #' @export setMethod("dbFetch", "KazamResult", function(res, n = -1, ...) { ... }) # (optionally) #' Find the database data type associated with an R object #' @export setMethod("dbDataType", "KazamConnection", function(dbObj, obj, ...) { ... }) ``` Next, implement `dbHasCompleted()` which should return a `logical` indicating if there are any rows remaining to be fetched. ```{r} #' @export setMethod("dbHasCompleted", "KazamResult", function(res, ...) { }) ``` With these four methods in place, you can now use the default `dbGetQuery()` to send a query to the database, retrieve results if available and then clean up. Spend some time now making sure this works with an existing database, or relax and let the `DBItest` package do the work for you. ## SQL methods You're now on the home stretch, and can make your wrapper substantially more useful by implementing methods that wrap around variations in SQL across databases: * `dbQuoteString()` and `dbQuoteIdentifer()` are used to safely quote strings and identifiers to avoid SQL injection attacks. Note that the former must be vectorized, but not the latter. * `dbWriteTable()` creates a database table given an R dataframe. I'd recommend using the functions prefixed with `sql` in this package to generate the SQL. These functions are still a work in progress so please let me know if you have problems. * `dbReadTable()`: a simple wrapper around `SELECT * FROM table`. Use `dbQuoteIdentifer()` to safely quote the table name and prevent mismatches between the names allowed by R and the database. * `dbListTables()` and `dbExistsTable()` let you determine what tables are available. If not provided by your database's API, you may need to generate sql that inspects the system tables. * `dbListFields()` shows which fields are available in a given table. * `dbRemoveTable()` wraps around `DROP TABLE`. Start with `SQL::sqlTableDrop()`. * `dbBegin()`, `dbCommit()` and `dbRollback()`: implement these three functions to provide basic transaction support. This functionality is currently not tested in the `DBItest` package. ## Metadata methods There are a lot of extra metadata methods for result sets (and one for the connection) that you might want to implement. They are described in the following. * `dbIsValid()` returns if a connection or a result set is open (`TRUE`) or closed (`FALSE`). All further methods in this section are valid for result sets only. * `dbGetStatement()` returns the issued query as a character value. * `dbColumnInfo()` lists the names and types of the result set's columns. * `dbGetRowCount()` and `dbGetRowsAffected()` returns the number of rows returned or altered in a `SELECT` or `INSERT`/`UPDATE` query, respectively. * `dbBind()` allows using parametrised queries. Take a look at `sqlInterpolate()` and `sqlParseVariables()` if your SQL engine doesn't offer native parametrised queries. ## Full DBI compliance By now, your package should implement all methods defined in the DBI specification. If you want to walk the extra mile, offer a read-only mode that allows your users to be sure that their valuable data doesn't get destroyed inadvertently. DBI/vignettes/spec.Rmd0000644000176200001440000000177114561335140014266 0ustar liggesusers--- title: "DBI specification" author: "Kirill Müller" output: rmarkdown::html_vignette abstract: > The DBI package defines the generic DataBase Interface for R. The connection to individual DBMS is provided by other packages that import DBI (so-called *DBI backends*). This document formalizes the behavior expected by the methods declared in DBI and implemented by the individual backends. To ensure maximum portability and exchangeability, and to reduce the effort for implementing a new DBI backend, the DBItest package defines a comprehensive set of test cases that test conformance to the DBI specification. This document is derived from comments in the test definitions of the DBItest package. Any extensions or updates to the tests will be reflected in this document. vignette: > %\VignetteIndexEntry{DBI specification} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r echo = FALSE} knitr::asis_output(paste(readLines("spec.md"), collapse = "\n")) ``` DBI/vignettes/DBI-history.Rmd0000644000176200001440000001221414552712157015432 0ustar liggesusers--- title: "History of DBI" author: "David James" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{History of DBI} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- The following history of DBI was contributed by David James, the driving force behind the development of DBI, and many of the packages that implement it. The idea/work of interfacing S (originally S3 and S4) to RDBMS goes back to the mid- and late 1990's in Bell Labs. The first toy interface I did was to implement John Chamber's early concept of "Data Management in S" (1991). The implementation followed that interface pretty closely and immediately showed some of the limitations when dealing with very large databases; if my memory serves me, the issue was the instance-based of the language back then, e.g., if you attached an RDBMS to the `search()` path and then needed to resolve a symbol "foo", you effectively had to bring all the objects in the database to check their mode/class, i.e., the instance object had the metadata in itself as attributes. The experiment showed that the S3 implementation of "data management" was not really suitable to large external RDBMS (probably it was never intended to do that anyway). (Note however, that since then, John and Duncan Temple Lang generalized the data management in S4 a lot, including Duncan's implementation in his RObjectTables package where he considered a lot of synchronization/caching issues relevant to DBI and, more generally, to most external interfaces). Back then we were working very closely with Lucent's microelectronics manufacturing --- our colleagues there had huge Oracle (mostly) databases that we needed to constantly query via [SQL*Plus](https://en.wikipedia.org/wiki/SQL*Plus). My colleague Jake Luciani was developing advanced applications in C and SQL, and the two of us came up with the first implementation of S3 directly connecting with Oracle. What I remember is that the Linux [PRO*C](https://en.wikipedia.org/wiki/Pro*C) pre-compiler (that embedded SQL in C code) was very buggy --- we spent a lot of time looking for workarounds and tricks until we got the C interface running. At the time, other projects within Bell Labs began using MySQL, and we moved to MySQL (with the help of Doug Bates' student Saikat DebRoy, then a summer intern) with no intentions of looking back at the very difficult Oracle interface. It was at this time that I moved all the code from S3 methods to S4 classes and methods and begun reaching out to the S/R community for suggestions, ideas, etc. All (most) of this work was on Bell Labs versions of S3 and S4, but I made sure it worked with S-Plus. At some point around 2000 (I don't remember exactly when), I ported all the code to R regressing to S3 methods, and later on (once S4 classes and methods were available in R) I re-implemented everything back to S4 classes and methods in R (a painful back-and-forth). It was at this point that I decided to drop S-Plus altogether. Around that time, I came across a very early implementation of SQLite and I was quite interested and thought it was a very nice RDBMS that could be used for all kinds of experimentation, etc., so it was pretty easy to implement on top of the DBI. Within the R community, there were quite a number of people that showed interest on defining a common interface to databases, but only a few folks actually provided code/suggestions/etc. (Tim Keitt was most active with the dbi/PostgreSQL packages --- he also was considering what he called "proxy" objects, which was reminiscent of what Duncan had been doing). Kurt Hornick, Vincent Carey, Robert Gentleman, and others provided suggestions/comments/support for the DBI definition. By around 2003, the DBI was more or less implemented as it is today. I'm sure I'll forget some (most should be in the THANKS sections of the various packages), but the names that come to my mind at this moment are Jake Luciani (ROracle), Don MacQueen and other early ROracle users (super helpful), Doug Bates and his student Saikat DebRoy for RMySQL, Fei Chen (at the time a student of Prof. Ripley) also contributed to RMySQL, Tim Keitt (working on an early S3 interface to PostgrSQL), Torsten Hothorn (worked with mSQL and also MySQL), Prof. Ripley working/extending the RODBC package, in addition to John Chambers and Duncan Temple-Lang who provided very important comments and suggestions. Actually, the real impetus behind the DBI was always to do distributed statistical computing --- *not* to provide a yet-another import/export mechanism --- and this perspective was driven by John and Duncan's vision and work on inter-system computing, COM, CORBA, etc. I'm not sure many of us really appreciated (even now) the full extent of those ideas and concepts. Just like in other languages (C's ODBC, Java's JDBC, Perl's DBI/DBD, Python dbapi), R/S DBI was meant to unify the interfacing to RDBMS so that R/S applications could be developed on top of the DBI and not be hard coded to any one relation database. The interface I tried to follow the closest was the Python's DBAPI --- I haven't worked on this topic for a while, but I still feel Python's DBAPI is the cleanest and most relevant for the S language. DBI/vignettes/DBI.Rmd0000644000176200001440000001632614552712323013736 0ustar liggesusers--- title: "Introduction to DBI" author: "James Wondrasek, Katharina Brunner, Kirill Müller" date: "27 February 2020" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{Introduction to DBI} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r setup, include=FALSE} knitr::opts_chunk$set( echo = TRUE, error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5"), # FIXME: Bring back when relational.fit clone is up eval = FALSE ) ``` ## Who this tutorial is for This tutorial is for you if you want to access or manipulate data in a database that may be on your machine or on a different computer on the internet, and you have found libraries that use a higher level of abstraction, such as [dbplyr](https://dbplyr.tidyverse.org/), are not suitable for your purpose. Depending on what you want to achieve, you may find it useful to have an understanding of SQL before using DBI. The DBI (**D**ata**B**ase **I**nterface) package provides a simple, consistent interface between R and database management systems (DBMS). Each supported DBMS is supported by its own R package that implements the DBI specification in `vignette("spec", package = "DBI")`. DBI currently supports about 30 DBMS, including: * MySQL, using the R-package [RMySQL](https://github.com/r-dbi/RMySQL) * MariaDB, using the R-package [RMariaDB](https://github.com/r-dbi/RMariaDB) * Postgres, using the R-package [RPostgres](https://github.com/r-dbi/RPostgres) * SQLite, using the R-package [RSQLite](https://github.com/r-dbi/RSQLite) For a more complete list of supported DBMS visit [https://github.com/r-dbi/backends](https://github.com/r-dbi/backends#readme). You may need to install the package specific to your DBMS. The functionality currently supported for each of these DBMS's includes: - manage a connection to a database - list the tables in a database - list the column names in a table - read a table into a data frame For more advanced features, such as parameterized queries, transactions, and more see `vignette("DBI-advanced", package = "DBI")`. ## How to connect to a database using DBI The following code establishes a connection to the Sakila database hosted by the Relational Dataset Repository at `https://relational.fit.cvut.cz/dataset/Sakila`, lists all tables on the database, and closes the connection. The database represents a fictional movie rental business and includes tables describing films, actors, customers, stores, etc.: ```{r} library(DBI) con <- dbConnect( RMariaDB::MariaDB(), host = "relational.fit.cvut.cz", port = 3306, username = "guest", password = "relational", dbname = "sakila" ) dbListTables(con) dbDisconnect(con) ``` Connections to databases are created using the `dbConnect()` function. The first argument to the function is the driver for the DBMS you are connecting to. In the example above we are connecting to a MariaDB instance, so we use the `RMariaDB::MariaDB()` driver. The other arguments depend on the authentication required by the DBMS. In the example host, port, username, password, and dbname are required. See the documentation for the DBMS driver package that you are using for specifics. The function `dbListTables()` takes a database connection as its only argument and returns a character vector with all table and view names in the database. After completing a session with a DBMS, always release the connection with a call to `dbDisconnect()`. ### Secure password storage The above example contains the password in the code, which should be avoided for databases with secured access. One way to use the credentials securely is to store it in your system's credential store and then query it with the [keyring](https://github.com/r-lib/keyring#readme) package. The code to connect to the database could then look like this: ```{r eval = FALSE} con <- dbConnect( RMariaDB::MariaDB(), host = "relational.fit.cvut.cz", port = 3306, username = "guest", password = keyring::key_get("relational.fit.cvut.cz", "guest"), dbname = "sakila" ) ``` ## How to retrieve column names for a table We can list the column names for a table with the function `dbListFields()`. It takes as arguments a database connection and a table name and returns a character vector of the column names in order. ```{r} con <- dbConnect(RMariaDB::MariaDB(), username = "guest", password = "relational", host = "relational.fit.cvut.cz", port = 3306, dbname = "sakila") dbListFields(con, "film") ``` ## Read a table into a data frame The function `dbReadTable()` reads an entire table and returns it as a data frame. It is equivalent to the SQL query `SELECT * FROM `. The columns of the returned data frame share the same names as the columns in the table. DBI and the database backends do their best to coerce data to equivalent R data types. ```{r} df <- dbReadTable(con, "film") head(df, 3) ``` ## Read only selected rows and columns into a data frame To read a subset of the data in a table into a data frame, DBI provides functions to run custom SQL queries and manage the results. For small datasets where you do not need to manage the number of results being returned, the function `dbGetQuery()` takes a SQL `SELECT` query to execute and returns a data frame. Below is a basic query that specifies the columns we require (`film_id`, `title` and `description`) and which rows (records) we are interested in. Here we retrieve films released in the year 2006. ```{r} df <- dbGetQuery(con, "SELECT film_id, title, description FROM film WHERE release_year = 2006") head(df, 3) ``` We could also retrieve movies released in 2006 that are rated "G". Note that character strings must be quoted. As the query itself is contained within double quotes, we use single quotes around the rating. See `dbQuoteLiteral()` for programmatically converting arbitrary R values to SQL. This is covered in more detail in `vignette("DBI-advanced", package = "DBI")`. ```{r} df <- dbGetQuery(con, "SELECT film_id, title, description FROM film WHERE release_year = 2006 AND rating = 'G'") head(df, 3) ``` The equivalent operation using `dplyr` reconstructs the SQL query using three functions to specify the table (`tbl()`), the subset of the rows (`filter()`), and the columns we require (`select()`). Note that dplyr takes care of the quoting. ```{r message=FALSE} library(dplyr) lazy_df <- tbl(con, "film") %>% filter(release_year == 2006 & rating == "G") %>% select(film_id, title, description) head(lazy_df, 3) ``` If you want to perform other data manipulation queries such as `UPDATE`s and `DELETE`s, see `dbSendStatement()` in `vignette("DBI-advanced", package = "DBI")`. ## How to end a DBMS session When finished accessing the DBMS, always close the connection using `dbDisconnect()`. ```{r} dbDisconnect(con) ``` ## Conclusion This tutorial has given you the basic techniques for accessing data in any supported DBMS. If you need to work with databases that will not fit in memory, or want to run more complex queries, including parameterized queries, please see `vignette("DBI-advanced", package = "DBI")`. ## Further Reading * An overview on [working with databases in R on Rstudio.com](https://db.rstudio.com/) * The DBI specification: `vignette("spec", package = "DBI")` * [List of supported DBMS](https://github.com/r-dbi/backends#readme) DBI/R/0000755000176200001440000000000014561352220011051 5ustar liggesusersDBI/R/dbCanConnect.R0000644000176200001440000000173014552712201013515 0ustar liggesusers#' Check if a connection to a DBMS can be established #' #' Like [dbConnect()], but only checks validity without actually returning #' a connection object. The default implementation opens a connection #' and disconnects on success, but individual backends might implement #' a lighter-weight check. #' #' @template methods #' @templateVar method_name dbCanConnect #' #' @return A scalar logical. If `FALSE`, the `"reason"` attribute indicates #' a reason for failure. #' #' @inheritParams dbConnect #' @family DBIDriver generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' # SQLite only needs a path to the database. (Here, ":memory:" is a special #' # path that creates an in-memory database.) Other database drivers #' # will require more details (like user, password, host, port, etc.) #' dbCanConnect(RSQLite::SQLite(), ":memory:") setGeneric("dbCanConnect", def = function(drv, ...) standardGeneric("dbCanConnect"), valueClass = "logical" ) DBI/R/dbListFields_DBIConnection_character.R0000644000176200001440000000042714350241735020265 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbListFields_DBIConnection_character <- function(conn, name, ...) { list_fields(conn, name) } #' @rdname hidden_aliases #' @export setMethod("dbListFields", signature("DBIConnection", "character"), dbListFields_DBIConnection_character) DBI/R/11-dbAppendTable.R0000644000176200001440000000323114552712323014103 0ustar liggesusers#' Insert rows into a table #' #' The `dbAppendTable()` method assumes that the table has been created #' beforehand, e.g. with [dbCreateTable()]. #' The default implementation calls [sqlAppendTableTemplate()] and then #' [dbExecute()] with the `param` argument. #' Use [dbAppendTableArrow()] to append data from an Arrow stream. #' #' Backends compliant to #' ANSI SQL 99 which use `?` as a placeholder for prepared queries don't need #' to override it. Backends with a different SQL syntax which use `?` #' as a placeholder for prepared queries can override [sqlAppendTable()]. #' Other backends (with different placeholders or with entirely different #' ways to create tables) need to override the `dbAppendTable()` method. #' #' The `row.names` argument is not supported by this method. #' Process the values with [sqlRownamesToColumn()] before calling this method. #' #' @inheritParams dbReadTable #' @param value A [data.frame] (or coercible to data.frame). #' @param row.names Must be `NULL`. #' @inheritParams sqlAppendTableTemplate #' #' @template methods #' @templateVar method_name dbAppendTable #' #' @inherit DBItest::spec_sql_append_table return #' @inheritSection DBItest::spec_sql_append_table Failure modes #' @inheritSection DBItest::spec_sql_append_table Specification #' #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' dbCreateTable(con, "iris", iris) #' dbAppendTable(con, "iris", iris) #' dbReadTable(con, "iris") #' dbDisconnect(con) setGeneric("dbAppendTable", def = function(conn, name, value, ..., row.names = NULL) standardGeneric("dbAppendTable") ) DBI/R/dbWithTransaction_DBIConnection.R0000644000176200001440000000247114350241735017331 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbWithTransaction_DBIConnection <- function(conn, code) { ## needs to be a closure, because it accesses conn rollback_because <- function(e) { call <- dbRollback(conn) if (identical(call, FALSE)) { stop( paste( "Failed to rollback transaction.", "Tried to roll back because an error", "occurred:", conditionMessage(e) ), call. = FALSE ) } if (inherits(e, "error")) { stop(e) } } ## check if each operation is successful call <- dbBegin(conn) if (identical(call, FALSE)) { stop("Failed to begin transaction", call. = FALSE) } tryCatch( { res <- force(code) call <- dbCommit(conn) if (identical(call, FALSE)) { stop("Failed to commit transaction", call. = FALSE) } res }, dbi_abort = rollback_because, error = rollback_because ) } #' @rdname hidden_aliases #' @export setMethod("dbWithTransaction", signature("DBIConnection"), dbWithTransaction_DBIConnection) #' @export #' @rdname dbWithTransaction dbBreak <- function() { signalCondition( structure( list(message = "Aborting DBI processing", call = NULL), class = c("dbi_abort", "condition") ) ) stop("Invalid usage of dbBreak().", call. = FALSE) } DBI/R/show_DBIConnector.R0000644000176200001440000000051114350241735014506 0ustar liggesusers#' @rdname hidden_aliases #' @param object Object to display #' @usage NULL show_DBIConnector <- function(object) { cat("") show(object@.drv) cat("Arguments:\n") show(object@.conn_args) invisible(NULL) } #' @rdname hidden_aliases #' @export setMethod("show", signature("DBIConnector"), show_DBIConnector) DBI/R/transactions.R0000644000176200001440000000370014552712201013703 0ustar liggesusers#' Begin/commit/rollback SQL transactions #' #' A transaction encapsulates several SQL statements in an atomic unit. #' It is initiated with `dbBegin()` and either made persistent with `dbCommit()` #' or undone with `dbRollback()`. #' In any case, the DBMS guarantees that either all or none of the statements #' have a permanent effect. #' This helps ensuring consistency of write operations to multiple tables. #' #' Not all database engines implement transaction management, in which case #' these methods should not be implemented for the specific #' [DBIConnection-class] subclass. #' #' @template methods #' @templateVar method_name transactions #' #' @inherit DBItest::spec_transaction_begin_commit_rollback return #' @inheritSection DBItest::spec_transaction_begin_commit_rollback Failure modes #' @inheritSection DBItest::spec_transaction_begin_commit_rollback Specification #' #' @inheritParams dbGetQuery #' @seealso Self-contained transactions: [dbWithTransaction()] #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "cash", data.frame(amount = 100)) #' dbWriteTable(con, "account", data.frame(amount = 2000)) #' #' # All operations are carried out as logical unit: #' dbBegin(con) #' withdrawal <- 300 #' dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) #' dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) #' dbCommit(con) #' #' dbReadTable(con, "cash") #' dbReadTable(con, "account") #' #' # Rolling back after detecting negative value on account: #' dbBegin(con) #' withdrawal <- 5000 #' dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) #' dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) #' if (dbReadTable(con, "account")$amount >= 0) { #' dbCommit(con) #' } else { #' dbRollback(con) #' } #' #' dbReadTable(con, "cash") #' dbReadTable(con, "account") #' #' dbDisconnect(con) NULL DBI/R/dbDisconnect.R0000644000176200001440000000117114552712201013572 0ustar liggesusers#' Disconnect (close) a connection #' #' This closes the connection, discards all pending work, and frees #' resources (e.g., memory, sockets). #' #' @template methods #' @templateVar method_name dbDisconnect #' #' @inherit DBItest::spec_connection_disconnect return #' @inheritSection DBItest::spec_connection_disconnect Failure modes #' #' @inheritParams dbGetQuery #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' dbDisconnect(con) setGeneric("dbDisconnect", def = function(conn, ...) standardGeneric("dbDisconnect") ) DBI/R/rownames.R0000644000176200001440000000526114350241735013037 0ustar liggesusers#' Convert row names back and forth between columns #' #' These functions provide a reasonably automatic way of preserving the row #' names of data frame during back-and-forth translation to an SQL table. #' By default, row names will be converted to an explicit column #' called "row_names", and any query returning a column called "row_names" #' will have those automatically set as row names. #' These methods are mostly useful for backend implementers. #' #' @param df A data frame #' @param row.names Either `TRUE`, `FALSE`, `NA` or a string. #' #' If `TRUE`, always translate row names to a column called "row_names". #' If `FALSE`, never translate row names. If `NA`, translate #' rownames only if they're a character vector. #' #' A string is equivalent to `TRUE`, but allows you to override the #' default name. #' #' For backward compatibility, `NULL` is equivalent to `FALSE`. #' @name rownames #' @examples #' # If have row names #' sqlRownamesToColumn(head(mtcars)) #' sqlRownamesToColumn(head(mtcars), FALSE) #' sqlRownamesToColumn(head(mtcars), "ROWNAMES") #' #' # If don't have #' sqlRownamesToColumn(head(iris)) #' sqlRownamesToColumn(head(iris), TRUE) #' sqlRownamesToColumn(head(iris), "ROWNAMES") NULL #' @export #' @rdname rownames sqlRownamesToColumn <- function(df, row.names = NA) { name <- guessRowName(df, row.names) if (is.null(name)) { rownames(df) <- NULL return(df) } rn <- stats::setNames(list(row.names(df)), name) df <- c(rn, df) class(df) <- "data.frame" attr(df, "row.names") <- .set_row_names(length(rn[[1]])) df } #' @export #' @rdname rownames sqlColumnToRownames <- function(df, row.names = NA) { name <- guessColName(df, row.names) if (is.null(name)) return(df) if (!(name %in% names(df))) { stop("Column ", name, " not present in output", call. = FALSE) } row.names(df) <- df[[name]] df[[name]] <- NULL df } guessRowName <- function(df, row.names) { if (identical(row.names, TRUE)) { "row_names" } else if (identical(row.names, FALSE) || is.null(row.names)) { NULL } else if (identical(row.names, NA)) { is_char <- is.character(attr(df, "row.names")) if (is_char) { "row_names" } else { NULL } } else if (is.character(row.names)) { row.names[1] } else { stop("Unknown input") } } guessColName <- function(df, row.names) { if (identical(row.names, TRUE)) { "row_names" } else if (identical(row.names, FALSE) || is.null(row.names)) { NULL } else if (identical(row.names, NA)) { if ("row_names" %in% names(df)) { "row_names" } else { NULL } } else if (is.character(row.names)) { row.names[1] } else { stop("Unknown input") } } DBI/R/dbiDataType_character.R0000644000176200001440000000030614350241735015405 0ustar liggesusersdbiDataType_character <- function(x) { "TEXT" } setMethod("dbiDataType", signature("character"), dbiDataType_character) setMethod("dbiDataType", signature("factor"), dbiDataType_character) DBI/R/01-DBIObject.R0000644000176200001440000000273214552712201013142 0ustar liggesusersNULL #' DBIObject class #' #' Base class for all other DBI classes (e.g., drivers, connections). This #' is a virtual Class: No objects may be created from it. #' #' More generally, the DBI defines a very small set of classes and generics that #' allows users and applications access DBMS with a common interface. The #' virtual classes are `DBIDriver` that individual drivers extend, #' `DBIConnection` that represent instances of DBMS connections, and #' `DBIResult` that represent the result of a DBMS statement. These three #' classes extend the basic class of `DBIObject`, which serves as the root #' or parent of the class hierarchy. #' #' @section Implementation notes: #' An implementation MUST provide methods for the following generics: #' #' \itemize{ #' \item [dbGetInfo()]. #' } #' #' It MAY also provide methods for: #' #' \itemize{ #' \item [summary()]. Print a concise description of the #' object. The default method invokes `dbGetInfo(dbObj)` and prints #' the name-value pairs one per line. Individual implementations may #' tailor this appropriately. #' } #' #' @docType class #' @family DBI classes #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' drv <- RSQLite::SQLite() #' con <- dbConnect(drv) #' #' rs <- dbSendQuery(con, "SELECT 1") #' is(drv, "DBIObject") ## True #' is(con, "DBIObject") ## True #' is(rs, "DBIObject") #' #' dbClearResult(rs) #' dbDisconnect(con) #' @export #' @name DBIObject-class setClass("DBIObject", "VIRTUAL") DBI/R/dbFetch_DBIResult.R0000644000176200001440000000033314350241735014413 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbFetch_DBIResult <- function(res, n = -1, ...) { fetch(res, n = n, ...) } #' @rdname hidden_aliases #' @export setMethod("dbFetch", signature("DBIResult"), dbFetch_DBIResult) DBI/R/dbDriver.R0000644000176200001440000000332414552712201012736 0ustar liggesusers#' Load and unload database drivers #' #' @description #' These methods are deprecated, please consult the documentation of the #' individual backends for the construction of driver instances. #' #' `dbDriver()` is a helper method used to create an new driver object #' given the name of a database or the corresponding R package. It works #' through convention: all DBI-extending packages should provide an exported #' object with the same name as the package. `dbDriver()` just looks for #' this object in the right places: if you know what database you are connecting #' to, you should call the function directly. #' #' @details #' The client part of the database communication is #' initialized (typically dynamically loading C code, etc.) but note that #' connecting to the database engine itself needs to be done through calls to #' `dbConnect`. #' #' @param drvName character name of the driver to instantiate. #' @param drv an object that inherits from `DBIDriver` as created by #' `dbDriver`. #' @param ... any other arguments are passed to the driver `drvName`. #' @return In the case of `dbDriver`, an driver object whose class extends #' `DBIDriver`. This object may be used to create connections to the #' actual DBMS engine. #' #' In the case of `dbUnloadDriver`, a logical indicating whether the #' operation succeeded or not. #' @import methods #' @family DBIDriver generics #' @export #' @keywords internal #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' # Create a RSQLite driver with a string #' d <- dbDriver("SQLite") #' d #' #' # But better, access the object directly #' RSQLite::SQLite() setGeneric("dbDriver", def = function(drvName, ...) standardGeneric("dbDriver"), valueClass = "DBIDriver" ) DBI/R/dbIsReadOnly_DBIObject.R0000644000176200001440000000027514350241735015330 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbIsReadOnly_DBIObject <- function(dbObj, ...) { FALSE } #' @rdname hidden_aliases setMethod("dbIsReadOnly", "DBIObject", dbIsReadOnly_DBIObject) DBI/R/dbDriver_character.R0000644000176200001440000000032114350241735014751 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbDriver_character <- function(drvName, ...) { findDriver(drvName)(...) } #' @rdname hidden_aliases setMethod("dbDriver", signature("character"), dbDriver_character) DBI/R/show_DBIDriver.R0000644000176200001440000000061114350241735014010 0ustar liggesusers#' @rdname hidden_aliases #' @param object Object to display #' @usage NULL show_DBIDriver <- function(object) { tryCatch( # to protect drivers that fail to implement the required methods (e.g., # RPostgreSQL) show_driver(object), error = function(e) NULL ) invisible(NULL) } #' @rdname hidden_aliases #' @export setMethod("show", signature("DBIDriver"), show_DBIDriver) DBI/R/dbGetInfo_DBIResult.R0000644000176200001440000000055014350241735014716 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbGetInfo_DBIResult <- function(dbObj, ...) { list( statement = dbGetStatement(dbObj), row.count = dbGetRowCount(dbObj), rows.affected = dbGetRowsAffected(dbObj), has.completed = dbHasCompleted(dbObj) ) } #' @rdname hidden_aliases setMethod("dbGetInfo", signature("DBIResult"), dbGetInfo_DBIResult) DBI/R/show_DBIConnection.R0000644000176200001440000000061214350241735014655 0ustar liggesusers#' @rdname hidden_aliases #' @param object Object to display #' @usage NULL show_DBIConnection <- function(object) { # to protect drivers that fail to implement the required methods (e.g., # RPostgreSQL) tryCatch( show_connection(object), error = function(e) NULL ) invisible(NULL) } #' @rdname hidden_aliases #' @export setMethod("show", "DBIConnection", show_DBIConnection) DBI/R/dbiDataType_list.R0000644000176200001440000000037514350241735014432 0ustar liggesusersdbiDataType_list <- function(x) { is_raw <- vapply(x, is.raw, logical(1)) if (!all(is_raw)) { stop("Only lists of raw vectors are currently supported", call. = FALSE) } "BLOB" } setMethod("dbiDataType", signature("list"), dbiDataType_list) DBI/R/dbFetch_DBIResultArrow.R0000644000176200001440000000057414552712156015441 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbFetch_DBIResultArrow <- function(res, n = -1, ...) { if (is.infinite(n)) { n <- -1 } if (n != -1) { stop("Cannot dbFetch() an Arrow result unless n = -1") } as.data.frame( dbFetchArrow(res, ...) ) } #' @rdname hidden_aliases #' @export setMethod("dbFetch", signature("DBIResultArrow"), dbFetch_DBIResultArrow) DBI/R/dbReadTableArrow.R0000644000176200001440000000222214552712323014342 0ustar liggesusers#' Read database tables as Arrow objects #' #' @description #' `r lifecycle::badge('experimental')` #' #' Reads a database table as an Arrow object. #' Use [dbReadTable()] instead to obtain a data frame. #' #' @details #' This function returns an Arrow object. #' Convert it to a data frame with [as.data.frame()] or #' use [dbReadTable()] to obtain a data frame. #' #' @template methods #' @templateVar method_name dbReadTableArrow #' #' @inherit DBItest::spec_arrow_read_table_arrow return #' @inheritSection DBItest::spec_arrow_read_table_arrow Failure modes #' @inheritSection DBItest::spec_arrow_read_table_arrow Specification #' #' @inheritParams dbGetQuery #' @inheritParams dbReadTable #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' # Read data as Arrow table #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars[1:10, ]) #' dbReadTableArrow(con, "mtcars") #' #' dbDisconnect(con) setGeneric("dbReadTableArrow", def = function(conn, name, ...) { require_arrow() standardGeneric("dbReadTableArrow") } ) DBI/R/dbSendQueryArrow_DBIConnection.R0000644000176200001440000000055414552712323017142 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbSendQueryArrow_DBIConnection <- function(conn, statement, params = NULL, ...) { result <- dbSendQuery(conn, statement, params = params, ...) new("DBIResultArrowDefault", result = result) } #' @rdname hidden_aliases #' @export setMethod("dbSendQueryArrow", signature("DBIConnection"), dbSendQueryArrow_DBIConnection) DBI/R/dbListTables.R0000644000176200001440000000152214552712201013547 0ustar liggesusers#' List remote tables #' #' Returns the unquoted names of remote tables accessible through this #' connection. #' This should include views and temporary objects, but not all database backends #' (in particular \pkg{RMariaDB} and \pkg{RMySQL}) support this. #' #' @template methods #' @templateVar method_name dbListTables #' #' @inherit DBItest::spec_sql_list_tables return #' @inheritSection DBItest::spec_sql_list_tables Failure modes #' #' @inheritParams dbGetQuery #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbListTables(con) #' dbWriteTable(con, "mtcars", mtcars) #' dbListTables(con) #' #' dbDisconnect(con) setGeneric("dbListTables", def = function(conn, ...) standardGeneric("dbListTables"), valueClass = "character" ) DBI/R/dbUnquoteIdentifier_DBIConnection.R0000644000176200001440000000167314552712323017656 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbUnquoteIdentifier_DBIConnection <- function(conn, x, ...) { # Determine quoting character quote_char <- substr(dbQuoteIdentifier(conn, ""), 1, 1) if (is(x, "SQL") || is.character(x)) { if (is.character(x)) { stopifnot(!anyNA(x)) } x <- lapply(x, unquote, quote_char = quote_char) lapply(x, Id) } else if (is(x, "Id")) { list(x) } else { stop("x must be SQL, Id, or character", call. = FALSE) } } unquote <- function(x, quote_char) { # replace doubled quotes with escaped quote gsub <- gsub( pattern = paste0(quote_char, quote_char), replacement = paste0("\\", quote_char), x ) scan( text = x, what = character(), quote = quote_char, quiet = TRUE, na.strings = character(), sep = "." ) } #' @rdname hidden_aliases #' @export setMethod("dbUnquoteIdentifier", signature("DBIConnection"), dbUnquoteIdentifier_DBIConnection) DBI/R/dbListFields_DBIConnection_Id.R0000644000176200001440000000040214350241735016656 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbListFields_DBIConnection_Id <- function(conn, name, ...) { list_fields(conn, name) } #' @rdname hidden_aliases #' @export setMethod("dbListFields", signature("DBIConnection", "Id"), dbListFields_DBIConnection_Id) DBI/R/dbColumnInfo.R0000644000176200001440000000201514552712201013550 0ustar liggesusers#' Information about result types #' #' Produces a data.frame that describes the output of a query. The data.frame #' should have as many rows as there are output fields in the result set, and #' each column in the data.frame describes an aspect of the result set #' field (field name, type, etc.) #' #' @inheritSection dbBind The data retrieval flow #' #' @inheritParams dbClearResult #' #' @template methods #' @templateVar method_name dbColumnInfo #' #' @inherit DBItest::spec_meta_column_info return #' @inheritSection DBItest::spec_meta_column_info Failure modes #' @inheritSection DBItest::spec_meta_column_info Specification #' #' @family DBIResult generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' rs <- dbSendQuery(con, "SELECT 1 AS a, 2 AS b") #' dbColumnInfo(rs) #' dbFetch(rs) #' #' dbClearResult(rs) #' dbDisconnect(con) setGeneric("dbColumnInfo", def = function(res, ...) standardGeneric("dbColumnInfo"), valueClass = "data.frame" ) DBI/R/dbFetchArrow_DBIResultArrow.R0000644000176200001440000000145314552712323016445 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbFetchArrow_DBIResultArrow <- function(res, ...) { chunk <- dbFetchArrowChunk_DBIResultArrow(res) # Corner case: add empty chunk only for zero rows, for schema if (chunk$length == 0) { return(nanoarrow::basic_array_stream( list(), schema = nanoarrow::infer_nanoarrow_schema(chunk), validate = FALSE )) } out <- list(chunk) repeat { chunk <- dbFetchArrowChunk_DBIResultArrow(res) if (chunk$length == 0) { return(nanoarrow::basic_array_stream( out, schema = nanoarrow::infer_nanoarrow_schema(out[[1]]), validate = FALSE )) } out <- c(out, list(chunk)) } } #' @rdname hidden_aliases #' @export setMethod("dbFetchArrow", signature("DBIResultArrow"), dbFetchArrow_DBIResultArrow) DBI/R/dbSendStatement.R0000644000176200001440000000457614552712201014273 0ustar liggesusers#' Execute a data manipulation statement on a given database connection #' #' The `dbSendStatement()` method only submits and synchronously executes the #' SQL data manipulation statement (e.g., `UPDATE`, `DELETE`, #' `INSERT INTO`, `DROP TABLE`, ...) to the database engine. To query #' the number of affected rows, call [dbGetRowsAffected()] on the #' returned result object. You must also call [dbClearResult()] after #' that. For interactive use, you should almost always prefer #' [dbExecute()]. #' #' [dbSendStatement()] comes with a default implementation that simply #' forwards to [dbSendQuery()], to support backends that only #' implement the latter. #' #' @inheritSection dbBind The command execution flow #' #' @template methods #' @templateVar method_name dbSendStatement #' #' @inherit DBItest::spec_result_send_statement return #' @inheritSection DBItest::spec_result_send_statement Failure modes #' @inheritSection DBItest::spec_result_send_statement Additional arguments #' @inheritSection DBItest::spec_result_send_statement Specification #' @inheritSection DBItest::spec_result_send_statement Specification for the `immediate` argument #' #' @inheritParams dbGetQuery #' @param statement a character string containing SQL. #' #' @family DBIConnection generics #' @family command execution generics #' #' @seealso For queries: [dbSendQuery()] and [dbGetQuery()]. #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "cars", head(cars, 3)) #' #' rs <- dbSendStatement( #' con, #' "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" #' ) #' dbHasCompleted(rs) #' dbGetRowsAffected(rs) #' dbClearResult(rs) #' dbReadTable(con, "cars") # there are now 6 rows #' #' # Pass one set of values directly using the param argument: #' rs <- dbSendStatement( #' con, #' "INSERT INTO cars (speed, dist) VALUES (?, ?)", #' params = list(4L, 5L) #' ) #' dbClearResult(rs) #' #' # Pass multiple sets of values using dbBind(): #' rs <- dbSendStatement( #' con, #' "INSERT INTO cars (speed, dist) VALUES (?, ?)" #' ) #' dbBind(rs, list(5:6, 6:7)) #' dbBind(rs, list(7L, 8L)) #' dbClearResult(rs) #' dbReadTable(con, "cars") # there are now 10 rows #' #' dbDisconnect(con) #' @export setGeneric("dbSendStatement", def = function(conn, statement, ...) standardGeneric("dbSendStatement"), valueClass = "DBIResult" ) DBI/R/dbSendStatement_DBIConnection_character.R0000644000176200001440000000045714350241735021004 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbSendStatement_DBIConnection_character <- function(conn, statement, ...) { dbSendQuery(conn, statement, ...) } #' @rdname hidden_aliases #' @export setMethod("dbSendStatement", signature("DBIConnection", "character"), dbSendStatement_DBIConnection_character) DBI/R/dbGetInfo.R0000644000176200001440000000114714350241735013044 0ustar liggesusers#' Get DBMS metadata #' #' Retrieves information on objects of class [DBIDriver-class], #' [DBIConnection-class] or [DBIResult-class]. #' #' @param dbObj An object inheriting from [DBIObject-class], #' i.e. [DBIDriver-class], [DBIConnection-class], #' or a [DBIResult-class] #' @param ... Other arguments to methods. #' #' @template methods #' @templateVar method_name dbGetInfo #' #' @family DBIDriver generics #' @family DBIConnection generics #' @family DBIResult generics #' @inherit DBItest::spec_get_info return #' @export setGeneric("dbGetInfo", def = function(dbObj, ...) standardGeneric("dbGetInfo") ) DBI/R/dbExistsTable_DBIConnection_Id.R0000644000176200001440000000044514350241735017052 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbExistsTable_DBIConnection_Id <- function(conn, name, ...) { dbExistsTable(conn, dbQuoteIdentifier(conn, name), ...) } #' @rdname hidden_aliases #' @export setMethod("dbExistsTable", signature("DBIConnection", "Id"), dbExistsTable_DBIConnection_Id) DBI/R/dbiDataType_POSIXct.R0000644000176200001440000000020314350241735014676 0ustar liggesusers#' @usage NULL dbiDataType_POSIXct <- function(x) "TIMESTAMP" setMethod("dbiDataType", signature("POSIXct"), dbiDataType_POSIXct) DBI/R/interpolate.R0000644000176200001440000000745114350241735013535 0ustar liggesusersNULL #' @export #' @rdname sqlParseVariables sqlCommentSpec <- function(start, end, endRequired) { list(start = start, end = end, endRequired = endRequired) } #' @export #' @rdname sqlParseVariables sqlQuoteSpec <- function(start, end, escape = "", doubleEscape = TRUE) { list(start = start, end = end, escape = escape, doubleEscape = doubleEscape) } #' @export #' @rdname sqlParseVariables #' @param sql SQL to parse (a character string) #' @param quotes A list of `QuoteSpec` calls defining the quoting #' specification. #' @param comments A list of `CommentSpec` calls defining the commenting #' specification. sqlParseVariablesImpl <- function(sql, quotes, comments) { str_to_vec <- function(s) strsplit(s, "", fixed = TRUE)[[1L]] sql_arr <- c(str_to_vec(as.character(sql)), " ") # characters valid in variable names var_chars <- c(LETTERS, letters, 0:9, "_") # return values var_pos_start <- integer() var_pos_end <- integer() # internal helper variables quote_spec_offset <- 0L comment_spec_offset <- 0L sql_variable_start <- 0L # prepare comments & quotes for quicker comparisions for (c in seq_along(comments)) { comments[[c]][["start"]] <- str_to_vec(comments[[c]][["start"]]) comments[[c]][["end"]] <- str_to_vec(comments[[c]][["end"]]) } for (q in seq_along(quotes)) { quotes[[q]][["hasEscape"]] <- nchar(quotes[[q]][["escape"]]) > 0L } state <- "default" i <- 0L while (i < length(sql_arr)) { i <- i + 1L switch(state, default = { # variable if (sql_arr[[i]] == "?") { sql_variable_start <- i state <- "variable" next } # starting quoted area for (q in seq_along(quotes)) { if (identical(sql_arr[[i]], quotes[[q]][["start"]])) { quote_spec_offset <- q state <- "quote" break } } # we can abort here if the state has changed if (state != "default") next # starting comment for (c in seq_along(comments)) { comment_start_arr <- comments[[c]][["start"]] comment_start_length <- length(comment_start_arr) if (identical(sql_arr[i:(i + comment_start_length - 1L)], comment_start_arr)) { comment_spec_offset <- c i <- i + comment_start_length state <- "comment" break } } }, variable = { if (!(sql_arr[[i]] %in% var_chars)) { # append current variable offsets to return vectors var_pos_start <- c(var_pos_start, sql_variable_start) # we have already read too much, go back i <- i - 1L var_pos_end <- c(var_pos_end, i) state <- "default" } }, quote = { # if we see backslash-like escapes, ignore next character if (quotes[[quote_spec_offset]][["hasEscape"]] && identical(sql_arr[[i]], quotes[[quote_spec_offset]][[3]])) { i <- i + 1L next } # end quoted area if (identical(sql_arr[[i]], quotes[[quote_spec_offset]][["end"]])) { quote_spec_offset <- 0L state <- "default" } }, comment = { # end commented area comment_end_arr <- comments[[comment_spec_offset]][["end"]] comment_end_length <- length(comment_end_arr) if (identical(sql_arr[i:(i + comment_end_length - 1L)], comment_end_arr)) { i <- i + (comment_end_length - 1) comment_spec_offset <- 0L state <- "default" } } ) # } # if (quote_spec_offset > 0L) { stop("Unterminated literal") } if (comment_spec_offset > 0L && comments[[comment_spec_offset]][["endRequired"]]) { stop("Unterminated comment") } list(start = var_pos_start, end = var_pos_end) } DBI/R/dbGetInfo_DBIResultArrow.R0000644000176200001440000000036014552712156015734 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbGetInfo_DBIResultArrow <- function(dbObj, ...) { dbGetInfo(dbObj@result, ...) } #' @rdname hidden_aliases #' @export setMethod("dbGetInfo", signature("DBIResultArrow"), dbGetInfo_DBIResultArrow) DBI/R/sqlCreateTable.R0000644000176200001440000000344514552712323014101 0ustar liggesusers#' Compose query to create a simple table #' #' Exposes an interface to simple `CREATE TABLE` commands. The default #' method is ANSI SQL 99 compliant. #' This method is mostly useful for backend implementers. #' #' The `row.names` argument must be passed explicitly in order to avoid #' a compatibility warning. The default will be changed in a later release. #' #' @param con A database connection. #' @param table The table name, passed on to [dbQuoteIdentifier()]. Options are: #' - a character string with the unquoted DBMS table name, #' e.g. `"table_name"`, #' - a call to [Id()] with components to the fully qualified table name, #' e.g. `Id(schema = "my_schema", table = "table_name")` #' - a call to [SQL()] with the quoted and fully qualified table name #' given verbatim, e.g. `SQL('"my_schema"."table_name"')` #' @param fields Either a character vector or a data frame. #' #' A named character vector: Names are column names, values are types. #' Names are escaped with [dbQuoteIdentifier()]. #' Field types are unescaped. #' #' A data frame: field types are generated using #' [dbDataType()]. #' @param temporary If `TRUE`, will generate a temporary table. #' @inheritParams rownames #' @param ... Other arguments used by individual methods. #' #' @template methods #' @templateVar method_name sqlCreateTable #' #' @export #' @examples #' sqlCreateTable(ANSI(), "my-table", c(a = "integer", b = "text")) #' sqlCreateTable(ANSI(), "my-table", iris) #' #' # By default, character row names are converted to a row_names colum #' sqlCreateTable(ANSI(), "mtcars", mtcars[, 1:5]) #' sqlCreateTable(ANSI(), "mtcars", mtcars[, 1:5], row.names = FALSE) setGeneric("sqlCreateTable", def = function(con, table, fields, row.names = NA, temporary = FALSE, ...) standardGeneric("sqlCreateTable") ) DBI/R/24-dbSendQueryArrow.R0000644000176200001440000000421614552712323014666 0ustar liggesusers#' Execute a query on a given database connection for retrieval via Arrow #' #' @description #' `r lifecycle::badge('experimental')` #' #' The `dbSendQueryArrow()` method only submits and synchronously executes the #' SQL query to the database engine. #' It does \emph{not} extract any #' records --- for that you need to use the [dbFetchArrow()] method, and #' then you must call [dbClearResult()] when you finish fetching the #' records you need. #' For interactive use, you should almost always prefer [dbGetQueryArrow()]. #' Use [dbSendQuery()] or [dbGetQuery()] instead to retrieve the results #' as a data frame. #' #' @details #' This method is for `SELECT` queries only. Some backends may #' support data manipulation queries through this method for compatibility #' reasons. However, callers are strongly encouraged to use #' [dbSendStatement()] for data manipulation statements. #' #' @inheritSection dbBindArrow The data retrieval flow for Arrow streams #' #' @template methods #' @templateVar method_name dbSendQueryArrow #' #' @inherit DBItest::spec_arrow_send_query_arrow return #' @inheritSection DBItest::spec_arrow_send_query_arrow Failure modes #' @inheritSection DBItest::spec_arrow_send_query_arrow Additional arguments #' @inheritSection DBItest::spec_arrow_send_query_arrow Specification #' @inheritSection DBItest::spec_arrow_send_query_arrow Specification for the `immediate` argument #' #' @inheritParams dbGetQueryArrow #' @param statement a character string containing SQL. #' #' @family DBIConnection generics #' @family data retrieval generics #' @seealso For updates: [dbSendStatement()] and [dbExecute()]. #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' # Retrieve data as arrow table #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' rs <- dbSendQueryArrow(con, "SELECT * FROM mtcars WHERE cyl = 4") #' dbFetchArrow(rs) #' dbClearResult(rs) #' #' dbDisconnect(con) setGeneric("dbSendQueryArrow", def = function(conn, statement, ...) { require_arrow() standardGeneric("dbSendQueryArrow") }, valueClass = "DBIResultArrow" ) DBI/R/summary_DBIObject.R0000644000176200001440000000063214350241735014503 0ustar liggesusers#' @usage NULL summary_DBIObject <- function(object, ...) { info <- dbGetInfo(dbObj = object, ...) cat(class(object), "\n") print_list_pairs(info) invisible(info) } setMethod("summary", "DBIObject", summary_DBIObject) print_list_pairs <- function(x, ...) { for (key in names(x)) { value <- format(x[[key]]) if (identical(value, "")) next cat(key, "=", value, "\n") } invisible(x) } DBI/R/dbIsValid_DBIResultArrowDefault.R0000644000176200001440000000040014552712323017230 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbIsValid_DBIResultArrowDefault <- function(dbObj, ...) { dbIsValid(dbObj@result) } #' @rdname hidden_aliases #' @export setMethod("dbIsValid", signature("DBIResultArrowDefault"), dbIsValid_DBIResultArrowDefault) DBI/R/dbDataType_DBIConnector.R0000644000176200001440000000036614350241735015557 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbDataType_DBIConnector <- function(dbObj, obj, ...) { dbDataType(dbObj@.drv, obj, ...) } #' @rdname hidden_aliases #' @export setMethod("dbDataType", signature("DBIConnector"), dbDataType_DBIConnector) DBI/R/25-dbBindArrow.R0000644000176200001440000000017314552712323013622 0ustar liggesusers#' @rdname dbBind #' @export setGeneric("dbBindArrow", def = function(res, params, ...) standardGeneric("dbBindArrow") ) DBI/R/deprecated.R0000644000176200001440000001050114552712323013275 0ustar liggesusersNULL ## produce legal SQL identifiers from strings in a character vector ## unique, in this function, means unique regardless of lower/upper case #' @rdname make.db.names #' @export make.db.names.default <- function(snames, keywords = .SQL92Keywords, unique = TRUE, allow.keywords = TRUE) { makeUnique <- function(x, sep = "_") { if (length(x) == 0) return(x) out <- x lc <- make.names(tolower(x), unique = FALSE) i <- duplicated(lc) lc <- make.names(lc, unique = TRUE) out[i] <- paste(out[i], substring(lc[i], first = nchar(out[i]) + 1), sep = sep) out } ## Note: SQL identifiers *can* be enclosed in double or single quotes ## when they are equal to reserverd keywords. fc <- substring(snames, 1, 1) lc <- substring(snames, nchar(snames)) i <- match(fc, c("'", '"'), 0) > 0 & match(lc, c("'", '"'), 0) > 0 snames[!i] <- make.names(snames[!i], unique = FALSE) if (unique) { snames[!i] <- makeUnique(snames[!i]) } if (!allow.keywords) { kwi <- match(keywords, toupper(snames), nomatch = 0L) snames[kwi] <- paste('"', snames[kwi], '"', sep = "") } gsub("\\.", "_", snames) } #' @rdname make.db.names #' @export isSQLKeyword.default <- function(name, keywords = .SQL92Keywords, case = c("lower", "upper", "any")[3]) { n <- pmatch(case, c("lower", "upper", "any"), nomatch = 0) if (n == 0) { stop('case must be one of "lower", "upper", or "any"') } kw <- switch(c("lower", "upper", "any")[n], lower = tolower(keywords), upper = toupper(keywords), any = toupper(keywords) ) if (n == 3) { name <- toupper(name) } match(name, keywords, nomatch = 0) > 0 } #' Keywords according to the SQL-92 standard #' #' A character vector of SQL-92 keywords, uppercase. #' #' @export #' @examples #' "SELECT" %in% .SQL92Keywords .SQL92Keywords <- c( "ABSOLUTE", "ADD", "ALL", "ALLOCATE", "ALTER", "AND", "ANY", "ARE", "AS", "ASC", "ASSERTION", "AT", "AUTHORIZATION", "AVG", "BEGIN", "BETWEEN", "BIT", "BIT_LENGTH", "BY", "CASCADE", "CASCADED", "CASE", "CAST", "CATALOG", "CHAR", "CHARACTER", "CHARACTER_LENGTH", "CHAR_LENGTH", "CHECK", "CLOSE", "COALESCE", "COLLATE", "COLLATION", "COLUMN", "COMMIT", "CONNECT", "CONNECTION", "CONSTRAINT", "CONSTRAINTS", "CONTINUE", "CONVERT", "CORRESPONDING", "COUNT", "CREATE", "CURRENT", "CURRENT_DATE", "CURRENT_TIMESTAMP", "CURRENT_TYPE", "CURSOR", "DATE", "DAY", "DEALLOCATE", "DEC", "DECIMAL", "DECLARE", "DEFAULT", "DEFERRABLE", "DEFERRED", "DELETE", "DESC", "DESCRIBE", "DESCRIPTOR", "DIAGNOSTICS", "DICONNECT", "DICTIONATRY", "DISPLACEMENT", "DISTINCT", "DOMAIN", "DOUBLE", "DROP", "ELSE", "END", "END-EXEC", "ESCAPE", "EXCEPT", "EXCEPTION", "EXEC", "EXECUTE", "EXISTS", "EXTERNAL", "EXTRACT", "FALSE", "FETCH", "FIRST", "FLOAT", "FOR", "FOREIGN", "FOUND", "FROM", "FULL", "GET", "GLOBAL", "GO", "GOTO", "GRANT", "GROUP", "HAVING", "HOUR", "IDENTITY", "IGNORE", "IMMEDIATE", "IN", "INCLUDE", "INDEX", "INDICATOR", "INITIALLY", "INNER", "INPUT", "INSENSITIVE", "INSERT", "INT", "INTEGER", "INTERSECT", "INTERVAL", "INTO", "IS", "ISOLATION", "JOIN", "KEY", "LANGUAGE", "LAST", "LEFT", "LEVEL", "LIKE", "LOCAL", "LOWER", "MATCH", "MAX", "MIN", "MINUTE", "MODULE", "MONTH", "NAMES", "NATIONAL", "NCHAR", "NEXT", "NOT", "NULL", "NULLIF", "NUMERIC", "OCTECT_LENGTH", "OF", "OFF", "ONLY", "OPEN", "OPTION", "OR", "ORDER", "OUTER", "OUTPUT", "OVERLAPS", "PARTIAL", "POSITION", "PRECISION", "PREPARE", "PRESERVE", "PRIMARY", "PRIOR", "PRIVILEGES", "PROCEDURE", "PUBLIC", "READ", "REAL", "REFERENCES", "RESTRICT", "REVOKE", "RIGHT", "ROLLBACK", "ROWS", "SCHEMA", "SCROLL", "SECOND", "SECTION", "SELECT", "SET", "SIZE", "SMALLINT", "SOME", "SQL", "SQLCA", "SQLCODE", "SQLERROR", "SQLSTATE", "SQLWARNING", "SUBSTRING", "SUM", "SYSTEM", "TABLE", "TEMPORARY", "THEN", "TIME", "TIMESTAMP", "TIMEZONE_HOUR", "TIMEZONE_MINUTE", "TO", "TRANSACTION", "TRANSLATE", "TRANSLATION", "TRUE", "UNION", "UNIQUE", "UNKNOWN", "UPDATE", "UPPER", "USAGE", "USER", "USING", "VALUE", "VALUES", "VARCHAR", "VARYING", "VIEW", "WHEN", "WHENEVER", "WHERE", "WITH", "WORK", "WRITE", "YEAR", "ZONE" ) #' Determine the current version of the package. #' #' @export #' @keywords internal dbGetDBIVersion <- function() { .Deprecated("packageVersion('DBI')") utils::packageVersion("DBI") } DBI/R/dbiDataType_Date.R0000644000176200001440000000016514350241735014331 0ustar liggesusers#' @usage NULL dbiDataType_Date <- function(x) "DATE" setMethod("dbiDataType", signature("Date"), dbiDataType_Date) DBI/R/dbAppendTableArrow_DBIConnection.R0000644000176200001440000000325714552712323017405 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbAppendTableArrow_DBIConnection <- function(conn, name, value, ...) { require_arrow() name <- dbQuoteIdentifier(conn, name) value <- nanoarrow::as_nanoarrow_array_stream(value) rows <- 0L while (TRUE) { # Append next batch (starting with the first or second, doesn't matter) tmp <- value$get_next() if (is.null(tmp)) { break } tmp_df <- as.data.frame(tmp) dbAppendTable(conn, name, stream_append_data(tmp_df), ...) rows <- rows + nrow(tmp_df) } value$release() rows } #' @rdname hidden_aliases #' @export setMethod("dbAppendTableArrow", signature("DBIConnection"), dbAppendTableArrow_DBIConnection) stream_append_data <- function(value) { value <- factor_to_string(value) value <- string_to_utf8(value) value } factor_to_string <- function(value, warn = FALSE) { is_factor <- vapply(value, is.factor, logical(1)) if (warn && any(is_factor)) { warning("Factors converted to character", call. = FALSE) } value[is_factor] <- lapply(value[is_factor], as.character) value } raw_to_string <- function(value) { is_raw <- vapply(value, is.raw, logical(1)) if (any(is_raw)) { warning("Creating a TEXT column from raw, use lists of raw to create BLOB columns", call. = FALSE) value[is_raw] <- lapply(value[is_raw], as.character) } value } quote_string <- function(value, conn) { is_character <- vapply(value, is.character, logical(1)) value[is_character] <- lapply(value[is_character], dbQuoteString, conn = conn) value } string_to_utf8 <- function(value) { is_char <- vapply(value, is.character, logical(1)) value[is_char] <- lapply(value[is_char], enc2utf8) value } DBI/R/dbGetConnectArgs_DBIConnector.R0000644000176200001440000000061414350241735016706 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbGetConnectArgs_DBIConnector <- function(drv, eval = TRUE, ...) { conn_args <- drv@.conn_args if (isTRUE(eval)) { conn_args <- lapply(conn_args, function(x) { if (is.function(x)) x() else x }) } conn_args } #' @rdname hidden_aliases #' @export setMethod("dbGetConnectArgs", signature("DBIConnector"), dbGetConnectArgs_DBIConnector) DBI/R/dbGetRowsAffected_DBIResultArrow.R0000644000176200001440000000041414552712156017415 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbGetRowsAffected_DBIResultArrow <- function(res, ...) { dbGetRowsAffected(res@result, ...) } #' @rdname hidden_aliases #' @export setMethod("dbGetRowsAffected", signature("DBIResultArrow"), dbGetRowsAffected_DBIResultArrow) DBI/R/sqlParseVariables_DBIConnection.R0000644000176200001440000000067414350241735017330 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL sqlParseVariables_DBIConnection <- function(conn, sql, ...) { sqlParseVariablesImpl( sql, list( sqlQuoteSpec('"', '"'), sqlQuoteSpec("'", "'") ), list( sqlCommentSpec("/*", "*/", TRUE), sqlCommentSpec("--", "\n", FALSE) ) ) } #' @rdname hidden_aliases #' @export setMethod("sqlParseVariables", signature("DBIConnection"), sqlParseVariables_DBIConnection) DBI/R/DBIConnector.R0000644000176200001440000000302614552712201013445 0ustar liggesusersNULL #' DBIConnector class #' #' Wraps objects of the [DBIDriver-class] class to include connection options. #' The purpose of this class is to store both the driver #' and the connection options. #' A database connection can be established #' with a call to [dbConnect()], passing only that object #' without additional arguments. #' #' To prevent leakage of passwords and other credentials, #' this class supports delayed evaluation. #' All arguments can optionally be a function (callable without arguments). #' In such a case, the function is evaluated transparently when connecting in #' [dbGetConnectArgs()]. #' # FIXME: Include this # Database backends can take advantage of this feature by returning an # instance of this class instead of `DBIDriver`. # See the implementation of [RSQLite::SQLite()] for an example. #' #' @docType class #' @name DBIConnector-class #' @family DBI classes #' @family DBIConnector generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' # Create a connector: #' cnr <- new("DBIConnector", #' .drv = RSQLite::SQLite(), #' .conn_args = list(dbname = ":memory:") #' ) #' cnr #' #' # Establish a connection through this connector: #' con <- dbConnect(cnr) #' con #' #' # Access the database through this connection: #' dbGetQuery(con, "SELECT 1 AS a") #' dbDisconnect(con) setClass("DBIConnector", slots = c(".drv" = "DBIDriver", ".conn_args" = "list"), contains = c("DBIObject") ) names2 <- function(x) { if (is.null(names(x))) { rep("", length(x)) } else { names(x) } } DBI/R/make.db.names_DBIObject_character.R0000644000176200001440000000057314350241735017431 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL make.db.names_DBIObject_character <- function(dbObj, snames, keywords, unique, allow.keywords, ...) { make.db.names.default(snames, keywords, unique, allow.keywords) } #' @rdname hidden_aliases setMethod("make.db.names", signature(dbObj = "DBIObject", snames = "character"), make.db.names_DBIObject_character, valueClass = "character") DBI/R/sqlParseVariables.R0000644000176200001440000000214014350241735014620 0ustar liggesusers#' Parse interpolated variables from SQL. #' #' If you're implementing a backend that uses non-ANSI quoting or commenting #' rules, you'll need to implement a method for `sqlParseVariables` that #' calls `sqlParseVariablesImpl` with the appropriate quote and #' comment specifications. #' #' #' @param start,end Start and end characters for quotes and comments #' @param endRequired Is the ending character of a comment required? #' @param doubleEscape Can quoting characters be escaped by doubling them? #' Defaults to `TRUE`. #' @param escape What character can be used to escape quoting characters? #' Defaults to `""`, i.e. nothing. #' @keywords internal #' @export #' @examples #' # Use [] for quoting and no comments #' sqlParseVariablesImpl("[?a]", #' list(sqlQuoteSpec("[", "]", "\\", FALSE)), #' list() #' ) #' #' # Standard quotes, use # for commenting #' sqlParseVariablesImpl("# ?a\n?b", #' list(sqlQuoteSpec("'", "'"), sqlQuoteSpec('"', '"')), #' list(sqlCommentSpec("#", "\n", FALSE)) #' ) setGeneric("sqlParseVariables", def = function(conn, sql, ...) standardGeneric("sqlParseVariables") ) DBI/R/sqlInterpolate.R0000644000176200001440000000607014350241735014211 0ustar liggesusers#' Safely interpolate values into an SQL string #' #' @description #' Accepts a query string with placeholders for values, and returns a string #' with the values embedded. #' The function is careful to quote all of its inputs with [dbQuoteLiteral()] #' to protect against SQL injection attacks. #' #' Placeholders can be specified with one of two syntaxes: #' #' - `?`: each occurrence of a standalone `?` is replaced with a value #' - `?name1`, `?name2`, ...: values are given as named arguments or a #' named list, the names are used to match the values #' #' Mixing `?` and `?name` syntaxes is an error. #' The number and names of values supplied must correspond to the placeholders #' used in the query. #' #' @section Backend authors: #' If you are implementing an SQL backend with non-ANSI quoting rules, you'll #' need to implement a method for [sqlParseVariables()]. Failure to #' do so does not expose you to SQL injection attacks, but will (rarely) result #' in errors matching supplied and interpolated variables. #' #' @inheritParams dbGetQuery #' @param sql A SQL string containing variables to interpolate. #' Variables must start with a question mark and can be any valid R #' identifier, i.e. it must start with a letter or `.`, and be followed #' by a letter, digit, `.` or `_`. #' @param ...,.dots Values (for `...`) or a list (for `.dots`) #' to interpolate into a string. #' Names are required if `sql` uses the `?name` syntax for placeholders. #' All values will be first escaped with [dbQuoteLiteral()] prior #' to interpolation to protect against SQL injection attacks. #' Arguments created by [SQL()] or [dbQuoteIdentifier()] remain unchanged. #' @return The `sql` query with the values from `...` and `.dots` safely #' embedded. #' #' @template methods #' @templateVar method_name sqlInterpolate #' #' @export #' @examples #' sql <- "SELECT * FROM X WHERE name = ?name" #' sqlInterpolate(ANSI(), sql, name = "Hadley") #' #' # This is safe because the single quote has been double escaped #' sqlInterpolate(ANSI(), sql, name = "H'); DROP TABLE--;") #' #' # Using paste0() could lead to dangerous SQL with carefully crafted inputs #' # (SQL injection) #' name <- "H'); DROP TABLE--;" #' paste0("SELECT * FROM X WHERE name = '", name, "'") #' #' # Use SQL() or dbQuoteIdentifier() to avoid escaping #' sql2 <- "SELECT * FROM ?table WHERE name in ?names" #' sqlInterpolate(ANSI(), sql2, #' table = dbQuoteIdentifier(ANSI(), "X"), #' names = SQL("('a', 'b')") #' ) #' #' # Don't use SQL() to escape identifiers to avoid SQL injection #' sqlInterpolate(ANSI(), sql2, #' table = SQL("X; DELETE FROM X; SELECT * FROM X"), #' names = SQL("('a', 'b')") #' ) #' #' # Use dbGetQuery() or dbExecute() to process these queries: #' if (requireNamespace("RSQLite", quietly = TRUE)) { #' con <- dbConnect(RSQLite::SQLite()) #' sql <- "SELECT ?value AS value" #' query <- sqlInterpolate(con, sql, value = 3) #' print(dbGetQuery(con, query)) #' dbDisconnect(con) #' } setGeneric("sqlInterpolate", def = function(conn, sql, ..., .dots = list()) standardGeneric("sqlInterpolate") ) DBI/R/dbReadTable_DBIConnection_character.R0000644000176200001440000000174114552712156020052 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbReadTable_DBIConnection_character <- function(conn, name, ..., row.names = FALSE, check.names = TRUE) { sql_name <- dbReadTable_toSqlName(conn, name, ...) if (!is.null(row.names)) { stopifnot(length(row.names) == 1L) stopifnot(is.logical(row.names) || is.character(row.names)) } stopifnot(length(check.names) == 1L) stopifnot(is.logical(check.names)) stopifnot(!is.na(check.names)) out <- dbGetQuery(conn, paste0("SELECT * FROM ", sql_name)) out <- sqlColumnToRownames(out, row.names) if (check.names) { names(out) <- make.names(names(out), unique = TRUE) } out } dbReadTable_toSqlName <- function(conn, name, ...) { sql_name <- dbQuoteIdentifier(conn, x = name, ...) if (length(sql_name) != 1L) { stop("Invalid name: ", format(name), call. = FALSE) } sql_name } #' @rdname hidden_aliases #' @export setMethod("dbReadTable", signature("DBIConnection", "character"), dbReadTable_DBIConnection_character) DBI/R/dbQuoteLiteral.R0000644000176200001440000000253714350241735014127 0ustar liggesusers#' Quote literal values #' #' @description #' Call these methods to generate a string that is suitable for #' use in a query as a literal value of the correct type, to make sure that you #' generate valid SQL and protect against SQL injection attacks. #' #' @inheritParams dbQuoteString #' @param x A vector to quote as string. #' #' @template methods #' @templateVar method_name dbQuoteLiteral #' #' @inherit DBItest::spec_sql_quote_literal return #' @inheritSection DBItest::spec_sql_quote_literal Failure modes #' @inheritSection DBItest::spec_sql_quote_literal Specification #' #' @family DBIResult generics #' @export #' @examples #' # Quoting ensures that arbitrary input is safe for use in a query #' name <- "Robert'); DROP TABLE Students;--" #' dbQuoteLiteral(ANSI(), name) #' #' # NAs become NULL #' dbQuoteLiteral(ANSI(), c(1:3, NA)) #' #' # Logicals become integers by default #' dbQuoteLiteral(ANSI(), c(TRUE, FALSE, NA)) #' #' # Raw vectors become hex strings by default #' dbQuoteLiteral(ANSI(), list(as.raw(1:3), NULL)) #' #' # SQL vectors are always passed through as is #' var_name <- SQL("select") #' var_name #' dbQuoteLiteral(ANSI(), var_name) #' #' # This mechanism is used to prevent double escaping #' dbQuoteLiteral(ANSI(), dbQuoteLiteral(ANSI(), name)) setGeneric("dbQuoteLiteral", def = function(conn, x, ...) standardGeneric("dbQuoteLiteral") ) DBI/R/22-dbCreateTableArrow.R0000644000176200001440000000274614552712323015126 0ustar liggesusers#' Create a table in the database based on an Arrow object #' #' @description #' `r lifecycle::badge('experimental')` #' #' The default `dbCreateTableArrow()` method determines the R data types #' of the Arrow schema associated with the Arrow object, #' and calls [dbCreateTable()]. #' Backends that implement [dbAppendTableArrow()] should typically #' also implement this generic. #' Use [dbCreateTable()] to create a table from the column types #' as defined in a data frame. #' #' @param value An object for which a schema can be determined via #' [nanoarrow::infer_nanoarrow_schema()]. #' @inheritParams dbReadTable #' @inheritParams sqlCreateTable #' #' @inherit DBItest::spec_arrow_create_table_arrow return #' @inheritSection DBItest::spec_arrow_create_table_arrow Failure modes #' @inheritSection DBItest::spec_arrow_create_table_arrow Additional arguments #' @inheritSection DBItest::spec_arrow_create_table_arrow Specification #' #' @template methods #' @templateVar method_name dbCreateTableArrow #' #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' ptype <- data.frame(a = numeric()) #' dbCreateTableArrow(con, "df", nanoarrow::infer_nanoarrow_schema(ptype)) #' dbReadTable(con, "df") #' dbDisconnect(con) setGeneric("dbCreateTableArrow", def = function(conn, name, value, ..., temporary = FALSE) standardGeneric("dbCreateTableArrow") ) DBI/R/07-DBIResultArrow.R0000644000176200001440000000145714552712323014243 0ustar liggesusers#' DBIResultArrow class #' #' @description #' `r lifecycle::badge('experimental')` #' #' This virtual class describes the result and state of execution of #' a DBMS statement (any statement, query or non-query) #' for returning data as an Arrow object. #' #' @section Implementation notes: #' Individual drivers are free to allow single or multiple #' active results per connection. #' #' The default show method displays a summary of the query using other #' DBI generics. #' #' @name DBIResultArrow-class #' @docType class #' @family DBI classes #' @family DBIResultArrow generics #' @export setClass("DBIResultArrow", contains = c("DBIObject", "VIRTUAL")) #' @rdname DBIResultArrow-class #' @export setClass("DBIResultArrowDefault", contains = "DBIResultArrow", slots = list( result = "DBIResult" ) ) DBI/R/dbHasCompleted.R0000644000176200001440000000215614552712323014062 0ustar liggesusers#' Completion status #' #' This method returns if the operation has completed. #' A `SELECT` query is completed if all rows have been fetched. #' A data manipulation statement is always completed. #' #' @inheritSection dbBind The data retrieval flow #' #' @template methods #' @templateVar method_name dbHasCompleted #' #' @inherit DBItest::spec_meta_has_completed return #' @inheritSection DBItest::spec_meta_has_completed Failure modes #' @inheritSection DBItest::spec_meta_has_completed Specification #' #' @inheritParams dbClearResult #' @family DBIResult generics #' @family DBIResultArrow generics #' @family data retrieval generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' rs <- dbSendQuery(con, "SELECT * FROM mtcars") #' #' dbHasCompleted(rs) #' ret1 <- dbFetch(rs, 10) #' dbHasCompleted(rs) #' ret2 <- dbFetch(rs) #' dbHasCompleted(rs) #' #' dbClearResult(rs) #' dbDisconnect(con) setGeneric("dbHasCompleted", def = function(res, ...) standardGeneric("dbHasCompleted"), valueClass = "logical" ) DBI/R/dbGetConnectArgs.R0000644000176200001440000000175414552712201014356 0ustar liggesusers#' Get connection arguments #' #' Returns the arguments stored in a [DBIConnector-class] object for inspection, #' optionally evaluating them. #' This function is called by [dbConnect()] #' and usually does not need to be called directly. #' #' @template methods #' @templateVar method_name dbGetConnectArgs #' #' @param drv A object inheriting from [DBIConnector-class]. #' @param eval Set to `FALSE` to return the functions that generate the argument #' instead of evaluating them. #' @param ... Other arguments passed on to methods. Not otherwise used. #' @family DBIConnector generics #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' cnr <- new("DBIConnector", #' .drv = RSQLite::SQLite(), #' .conn_args = list(dbname = ":memory:", password = function() "supersecret") #' ) #' dbGetConnectArgs(cnr) #' dbGetConnectArgs(cnr, eval = FALSE) #' @export setGeneric("dbGetConnectArgs", def = function(drv, eval = TRUE, ...) standardGeneric("dbGetConnectArgs"), valueClass = "list" ) DBI/R/dbiDataType.R0000644000176200001440000000012414350241735013367 0ustar liggesuserssetGeneric("dbiDataType", def = function(x, ...) standardGeneric("dbiDataType") ) DBI/R/12-dbCreateTable.R0000644000176200001440000000274014552712323014104 0ustar liggesusers#' Create a table in the database #' #' The default `dbCreateTable()` method calls [sqlCreateTable()] and #' [dbExecute()]. #' Use [dbCreateTableArrow()] to create a table from an Arrow schema. #' #' Backends compliant to ANSI SQL 99 don't need to override it. #' Backends with a different SQL syntax can override `sqlCreateTable()`, #' backends with entirely different ways to create tables need to #' override this method. #' #' The `row.names` argument is not supported by this method. #' Process the values with [sqlRownamesToColumn()] before calling this method. #' #' The argument order is different from the `sqlCreateTable()` method, the #' latter will be adapted in a later release of DBI. #' #' @inheritParams dbReadTable #' @param row.names Must be `NULL`. #' @inheritParams sqlCreateTable #' #' @inherit DBItest::spec_sql_create_table return #' @inheritSection DBItest::spec_sql_create_table Failure modes #' @inheritSection DBItest::spec_sql_create_table Additional arguments #' @inheritSection DBItest::spec_sql_create_table Specification #' #' @template methods #' @templateVar method_name dbCreateTable #' #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' dbCreateTable(con, "iris", iris) #' dbReadTable(con, "iris") #' dbDisconnect(con) setGeneric("dbCreateTable", def = function(conn, name, fields, ..., row.names = NULL, temporary = FALSE) standardGeneric("dbCreateTable") ) DBI/R/dbiDataType_difftime.R0000644000176200001440000000020114350241735015232 0ustar liggesusers#' @usage NULL dbiDataType_difftime <- function(x) "TIME" setMethod("dbiDataType", signature("difftime"), dbiDataType_difftime) DBI/R/DBI-package.R0000644000176200001440000000203014552712201013155 0ustar liggesusers#' @description #' DBI defines an interface for communication between R and relational database #' management systems. #' All classes in this package are virtual and need to be extended by #' the various R/DBMS implementations (so-called *DBI backends*). #' #' @inheritSection DBItest::spec_getting_started Definition #' @inheritSection DBItest::spec_compliance_methods DBI classes and methods #' @inheritSection DBItest::spec_driver_constructor Construction of the DBIDriver object #' #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' RSQLite::SQLite() #' @seealso #' Important generics: [dbConnect()], [dbGetQuery()], #' [dbReadTable()], [dbWriteTable()], [dbDisconnect()] #' #' Formal specification (currently work in progress and incomplete): #' `vignette("spec", package = "DBI")` "_PACKAGE" has_arrow <- function() { requireNamespace("nanoarrow", quietly = TRUE) } require_arrow <- function() { if (has_arrow()) { return(invisible(TRUE)) } stop("The nanoarrow package is required for this functionality.") } DBI/R/show_SQL.R0000644000176200001440000000033114350241735012674 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL show_SQL <- function(object) { cat(paste0(" ", object@.Data, collapse = "\n"), "\n", sep = "") } #' @rdname hidden_aliases #' @export setMethod("show", "SQL", show_SQL) DBI/R/dbDataType_DBIObject.R0000644000176200001440000000033514350241735015027 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbDataType_DBIObject <- function(dbObj, obj, ...) { dbiDataType(obj) } #' @rdname hidden_aliases #' @export setMethod("dbDataType", signature("DBIObject"), dbDataType_DBIObject) DBI/R/dbGetException.R0000644000176200001440000000073314350241735014107 0ustar liggesusers#' Get DBMS exceptions #' #' DEPRECATED. Backends should use R's condition system to signal errors and #' warnings. #' #' @inheritParams dbGetQuery #' @family DBIConnection generics #' @return a list with elements `errorNum` (an integer error number) and #' `errorMsg` (a character string) describing the last error in the #' connection `conn`. #' @export #' @keywords internal setGeneric("dbGetException", def = function(conn, ...) standardGeneric("dbGetException") ) DBI/R/dbCanConnect_DBIDriver.R0000644000176200001440000000062714350241735015360 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbCanConnect_DBIDriver <- function(drv, ...) { tryCatch( { con <- dbConnect(drv, ...) dbDisconnect(con) TRUE }, error = function(e) { structure( FALSE, reason = conditionMessage(e) ) } ) } #' @rdname hidden_aliases #' @export setMethod("dbCanConnect", signature("DBIDriver"), dbCanConnect_DBIDriver) DBI/R/00-Id.R0000644000176200001440000000414014561351510011745 0ustar liggesusersNULL #' @rdname Id setClass("Id", slots = list(name = "character")) #' Refer to a table nested in a hierarchy (e.g. within a schema) #' #' @description #' Objects of class `Id` have a single slot `name`, which is a character vector. #' The [dbQuoteIdentifier()] method converts `Id` objects to strings. #' Support for `Id` objects depends on the database backend. #' #' They can be used in the following methods as `name` or `table` argument: #' #' - [dbCreateTable()] #' - [dbAppendTable()] #' - [dbReadTable()] #' - [dbWriteTable()] #' - [dbExistsTable()] #' - [dbRemoveTable()] #' #' Objects of this class are also returned from [dbListObjects()]. #' #' @param ... Components of the hierarchy, e.g. `cluster`, #' `catalog`, `schema`, or `table`, depending on the database backend. For more #' on these concepts, see #' @export #' @examples #' # Identifies a table in a specific schema: #' Id("dbo", "Customer") #' # You can name the components if you want, but it's not needed #' Id(table = "Customer", schema = "dbo") #' #' # Create a SQL expression for an identifier: #' dbQuoteIdentifier(ANSI(), Id("nycflights13", "flights")) #' #' # Write a table in a specific schema: #' \dontrun{ #' dbWriteTable(con, Id("myschema", "mytable"), data.frame(a = 1)) #' } Id <- function(...) { components <- orderIdParams(...) if (!is.character(components)) { stop("All elements of `...` must be strings.", call. = FALSE) } new("Id", name = components) } #' @export toString.Id <- function(x, ...) { paste0(" ", dbQuoteIdentifier(ANSI(), x)) } dbQuoteIdentifier_DBIConnection_Id <- function(conn, x, ...) { SQL(paste0(dbQuoteIdentifier(conn, x@name), collapse = ".")) } orderIdParams <- function( ..., database = NULL, db = NULL, catalog = NULL, cluster = NULL, schema = NULL, table = NULL, column = NULL) { out <- c( database = database, db = db, cluster = cluster, catalog = catalog, schema = schema, ..., table = table, column = column ) if (all(names(out) == "")) { out <- unname(out) } out } DBI/R/dbDataType.R0000644000176200001440000000473114552712201013221 0ustar liggesusers#' Determine the SQL data type of an object #' #' Returns an SQL string that describes the SQL data type to be used for an #' object. #' The default implementation of this generic determines the SQL type of an #' R object according to the SQL 92 specification, which may serve as a starting #' point for driver implementations. DBI also provides an implementation #' for data.frame which will return a character vector giving the type for each #' column in the dataframe. #' #' The data types supported by databases are different than the data types in R, #' but the mapping between the primitive types is straightforward: #' - Any of the many fixed and varying length character types are mapped to #' character vectors #' - Fixed-precision (non-IEEE) numbers are mapped into either numeric or #' integer vectors. #' #' Notice that many DBMS do not follow IEEE arithmetic, so there are potential #' problems with under/overflows and loss of precision. #' #' @template methods #' @templateVar method_name dbDataType #' #' @inherit DBItest::spec_driver_data_type return #' @inheritSection DBItest::spec_driver_data_type Failure modes #' @inheritSection DBItest::spec_driver_data_type Specification #' @inheritSection DBItest::spec_result_create_table_with_data_type Specification #' #' @inheritParams dbListConnections #' @param dbObj A object inheriting from [DBIDriver-class] #' or [DBIConnection-class] #' @param obj An R object whose SQL type we want to determine. #' @family DBIDriver generics #' @family DBIConnection generics #' @family DBIConnector generics #' @examples #' dbDataType(ANSI(), 1:5) #' dbDataType(ANSI(), 1) #' dbDataType(ANSI(), TRUE) #' dbDataType(ANSI(), Sys.Date()) #' dbDataType(ANSI(), Sys.time()) #' dbDataType(ANSI(), Sys.time() - as.POSIXct(Sys.Date())) #' dbDataType(ANSI(), c("x", "abc")) #' dbDataType(ANSI(), list(raw(10), raw(20))) #' dbDataType(ANSI(), I(3)) #' #' dbDataType(ANSI(), iris) #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbDataType(con, 1:5) #' dbDataType(con, 1) #' dbDataType(con, TRUE) #' dbDataType(con, Sys.Date()) #' dbDataType(con, Sys.time()) #' dbDataType(con, Sys.time() - as.POSIXct(Sys.Date())) #' dbDataType(con, c("x", "abc")) #' dbDataType(con, list(raw(10), raw(20))) #' dbDataType(con, I(3)) #' #' dbDataType(con, iris) #' #' dbDisconnect(con) #' @export setGeneric("dbDataType", def = function(dbObj, obj, ...) standardGeneric("dbDataType"), valueClass = "character" ) DBI/R/dbFetchArrowChunk.R0000644000176200001440000000305114552712323014542 0ustar liggesusers#' Fetch the next batch of records from a previously executed query as an Arrow object #' #' @description #' `r lifecycle::badge('experimental')` #' #' Fetch the next chunk of the result set and return it as an Arrow object. #' The chunk size is implementation-specific. #' Use [dbFetchArrow()] to fetch all results. #' #' @inheritSection dbBind The data retrieval flow for Arrow streams #' #' @template methods #' @templateVar method_name dbFetchArrowChunk #' #' @inherit DBItest::spec_arrow_fetch_arrow_chunk return #' @inheritSection DBItest::spec_arrow_fetch_arrow_chunk Failure modes #' @inheritSection DBItest::spec_arrow_fetch_arrow_chunk Specification #' #' @param res An object inheriting from [DBIResultArrow-class], created by #' [dbSendQueryArrow()]. #' @param ... Other arguments passed on to methods. #' @seealso Close the result set with [dbClearResult()] as soon as you #' finish retrieving the records you want. #' @family DBIResultArrow generics #' @family data retrieval generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' #' # Fetch all results #' rs <- dbSendQueryArrow(con, "SELECT * FROM mtcars WHERE cyl = 4") #' dbHasCompleted(rs) #' as.data.frame(dbFetchArrowChunk(rs)) #' dbHasCompleted(rs) #' as.data.frame(dbFetchArrowChunk(rs)) #' dbClearResult(rs) #' #' dbDisconnect(con) setGeneric("dbFetchArrowChunk", def = function(res, ...) standardGeneric("dbFetchArrowChunk") ) DBI/R/dbClearResult_DBIResultArrow.R0000644000176200001440000000037414552712156016633 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbClearResult_DBIResultArrow <- function(res, ...) { dbClearResult(res@result, ...) } #' @rdname hidden_aliases #' @export setMethod("dbClearResult", signature("DBIResultArrow"), dbClearResult_DBIResultArrow) DBI/R/dbFetchArrowChunk_DBIResultArrow.R0000644000176200001440000000046214552712323017435 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbFetchArrowChunk_DBIResultArrow <- function(res, ...) { nanoarrow::as_nanoarrow_array( dbFetch(res@result, n = 256, ...) ) } #' @rdname hidden_aliases #' @export setMethod("dbFetchArrowChunk", signature("DBIResultArrow"), dbFetchArrowChunk_DBIResultArrow) DBI/R/dbHasCompleted_DBIResultArrow.R0000644000176200001440000000040014552712156016744 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbHasCompleted_DBIResultArrow <- function(res, ...) { dbHasCompleted(res@result, ...) } #' @rdname hidden_aliases #' @export setMethod("dbHasCompleted", signature("DBIResultArrow"), dbHasCompleted_DBIResultArrow) DBI/R/dbConnect_DBIConnector.R0000644000176200001440000000135514350241735015434 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbConnect_DBIConnector <- function(drv, ...) { dots_args <- list(...) has_name <- names2(dots_args) != "" # Unnamed dots come first (they are not picked up by modifyList()) unnamed_dots <- dots_args[!has_name] # Named dots come last, an extra drv argument is erased silently named_dots <- dots_args[has_name] named_dots$drv <- NULL # Named dots are supplemented with connector args extra_args <- utils::modifyList( dbGetConnectArgs(drv), named_dots ) all_args <- c( list(drv = drv@.drv), unnamed_dots, extra_args ) do.call(dbConnect, all_args) } #' @rdname hidden_aliases #' @export setMethod("dbConnect", signature("DBIConnector"), dbConnect_DBIConnector) DBI/R/dbSetDataMappings.R0000644000176200001440000000142214350241735014531 0ustar liggesusers#' Set data mappings between an DBMS and R. #' #' This generic is deprecated since no working implementation was ever produced. #' #' Sets one or more conversion functions to handle the translation of DBMS data #' types to R objects. This is only needed for non-primitive data, since all #' DBI drivers handle the common base types (integers, numeric, strings, etc.) #' #' The details on conversion functions (e.g., arguments, whether they can invoke #' initializers and/or destructors) have not been specified. #' #' @inheritParams dbClearResult #' @keywords internal #' @param flds a field description object as returned by `dbColumnInfo`. #' @export setGeneric("dbSetDataMappings", def = function(res, flds, ...) { .Deprecated() standardGeneric("dbSetDataMappings") } ) DBI/R/dbExistsTable.R0000644000176200001440000000137614552712201013737 0ustar liggesusers#' Does a table exist? #' #' Returns if a table given by name exists in the database. #' #' @template methods #' @templateVar method_name dbExistsTable #' #' @inherit DBItest::spec_sql_exists_table return #' @inheritSection DBItest::spec_sql_exists_table Failure modes #' @inheritSection DBItest::spec_sql_exists_table Specification #' #' @inheritParams dbReadTable #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbExistsTable(con, "iris") #' dbWriteTable(con, "iris", iris) #' dbExistsTable(con, "iris") #' #' dbDisconnect(con) setGeneric("dbExistsTable", def = function(conn, name, ...) standardGeneric("dbExistsTable"), valueClass = "logical" ) DBI/R/03-DBIConnection.R0000644000176200001440000000217714552712201014040 0ustar liggesusers#' DBIConnection class #' #' This virtual class encapsulates the connection to a DBMS, and it provides #' access to dynamic queries, result sets, DBMS session management #' (transactions), etc. #' #' @section Implementation note: #' Individual drivers are free to implement single or multiple simultaneous #' connections. #' #' @docType class #' @name DBIConnection-class #' @family DBI classes #' @family DBIConnection generics #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' con #' dbDisconnect(con) #' \dontrun{ #' con <- dbConnect(RPostgreSQL::PostgreSQL(), "username", "passsword") #' con #' dbDisconnect(con) #' } #' @export setClass("DBIConnection", contains = c("DBIObject", "VIRTUAL")) show_connection <- function(object) { cat("<", is(object)[1], ">\n", sep = "") if (!dbIsValid(object)) { cat(" DISCONNECTED\n") } } list_fields <- function(conn, name) { rs <- dbSendQuery( conn, paste( "SELECT * FROM ", dbQuoteIdentifier(conn, name), "LIMIT 0" ) ) on.exit(dbClearResult(rs)) names(dbFetch(rs, n = 0, row.names = FALSE)) } DBI/R/isSQLKeyword.R0000644000176200001440000000040514350241735013537 0ustar liggesusers#' @rdname make.db.names #' @export setGeneric("isSQLKeyword", def = function(dbObj, name, keywords = .SQL92Keywords, case = c("lower", "upper", "any")[3], ...) standardGeneric("isSQLKeyword"), signature = c("dbObj", "name"), valueClass = "logical" ) DBI/R/dbRemoveTable.R0000644000176200001440000000161314552712201013707 0ustar liggesusers#' Remove a table from the database #' #' Remove a remote table (e.g., created by [dbWriteTable()]) #' from the database. #' #' @template methods #' @templateVar method_name dbRemoveTable #' #' @inherit DBItest::spec_sql_remove_table return #' @inheritSection DBItest::spec_sql_remove_table Failure modes #' @inheritSection DBItest::spec_sql_remove_table Additional arguments #' @inheritSection DBItest::spec_sql_remove_table Specification #' #' @inheritParams dbReadTable #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbExistsTable(con, "iris") #' dbWriteTable(con, "iris", iris) #' dbExistsTable(con, "iris") #' dbRemoveTable(con, "iris") #' dbExistsTable(con, "iris") #' #' dbDisconnect(con) setGeneric("dbRemoveTable", def = function(conn, name, ...) standardGeneric("dbRemoveTable") ) DBI/R/dbBind_DBIResultArrow.R0000644000176200001440000000041214552712323015247 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbBind_DBIResultArrow <- function(res, params, ...) { dbBind(res@result, params = params, ...) invisible(res) } #' @rdname hidden_aliases #' @export setMethod("dbBind", signature("DBIResultArrow"), dbBind_DBIResultArrow) DBI/R/dbiDataType_default.R0000644000176200001440000000040114552712156015075 0ustar liggesusersdbiDataType_default <- function(x) { if (inherits(x, c("blob", "arrow_binary"))) { return("BLOB") } stop("SQL type unknown for objects of class ", paste(class(x), collapse = "/")) } setMethod("dbiDataType", signature("ANY"), dbiDataType_default) DBI/R/dbGetQueryArrow.R0000644000176200001440000000447614552712323014301 0ustar liggesusers#' Retrieve results from a query as an Arrow object #' #' @description #' `r lifecycle::badge('experimental')` #' #' Returns the result of a query as an Arrow object. #' `dbGetQueryArrow()` comes with a default implementation #' (which should work with most backends) that calls #' [dbSendQueryArrow()], then [dbFetchArrow()], ensuring that #' the result is always freed by [dbClearResult()]. #' For passing query parameters, #' see [dbSendQueryArrow()], in particular #' the "The data retrieval flow for Arrow streams" section. #' For retrieving results as a data frame, see [dbGetQuery()]. #' #' @details #' This method is for `SELECT` queries only #' (incl. other SQL statements that return a `SELECT`-alike result, #' e.g., execution of a stored procedure or data manipulation queries #' like `INSERT INTO ... RETURNING ...`). #' To execute a stored procedure that does not return a result set, #' use [dbExecute()]. #' #' Some backends may #' support data manipulation statements through this method. #' However, callers are strongly advised to use #' [dbExecute()] for data manipulation statements. #' #' @template methods #' @templateVar method_name dbGetQueryArrow #' #' @inherit DBItest::spec_arrow_get_query_arrow return #' @inheritSection DBItest::spec_arrow_get_query_arrow Failure modes #' @inheritSection DBItest::spec_arrow_get_query_arrow Additional arguments #' @inheritSection DBItest::spec_arrow_get_query_arrow Specification for the `immediate` argument #' #' @section Implementation notes: #' Subclasses should override this method only if they provide some sort of #' performance optimization. #' #' @param conn A [DBIConnection-class] object, as returned by #' [dbConnect()]. #' @param statement a character string containing SQL. #' @param ... Other parameters passed on to methods. #' @family DBIConnection generics #' @family data retrieval generics #' @seealso For updates: [dbSendStatement()] and [dbExecute()]. #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' # Retrieve data as arrow table #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' dbGetQueryArrow(con, "SELECT * FROM mtcars") #' #' dbDisconnect(con) setGeneric("dbGetQueryArrow", def = function(conn, statement, ...) standardGeneric("dbGetQueryArrow") ) DBI/R/data.R0000644000176200001440000000162214350241735012112 0ustar liggesusersNULL # Coercion rules --------------------------------------------------------------- coerce <- function(sqlvar, from, to) { list(from = from, to = to) } sqlDate <- function() { coerce( function(x) as.integer(x), function(x) { stopifnot(is.integer(x)) structure(x, class = "Date") } ) } sqlDateTime <- function() { coerce( function(x) as.numeric(x), function(x) { stopifnot(is.numeric(x)) structure(x, class = c("POSIXct", "POSIXt"), tzone = "UTC") } ) } sqlSerialize <- function() { coerce( function(x) { lapply(x, serialize, connection = NULL) }, function(x) { lapply(x, unserialize) } ) } sqlBoolean <- function() { coerce( function(x) as.integer(x), function(x) as.logical(x) ) } sqlFactor <- function(levels) { coerce( function(x) as.integer(x), function(x) factor(x, levels = levels) ) } DBI/R/15-dbBind.R0000644000176200001440000002170014552712323012605 0ustar liggesusers#' Bind values to a parameterized/prepared statement #' #' @description #' For parametrized or prepared statements, #' the [dbSendQuery()], [dbSendQueryArrow()], and [dbSendStatement()] functions #' can be called with statements that contain placeholders for values. #' The `dbBind()` and `dbBindArrow()` functions bind these placeholders #' to actual values, #' and are intended to be called on the result set #' before calling [dbFetch()] or [dbFetchArrow()]. #' The values are passed to `dbBind()` as lists or data frames, #' and to `dbBindArrow()` as a stream #' created by [nanoarrow::as_nanoarrow_array_stream()]. #' #' `r lifecycle::badge('experimental')` #' #' `dbBindArrow()` is experimental, as are the other `*Arrow` functions. #' `dbSendQuery()` is compatible with `dbBindArrow()`, and `dbSendQueryArrow()` #' is compatible with `dbBind()`. #' #' @details #' \pkg{DBI} supports parametrized (or prepared) queries and statements #' via the `dbBind()` and `dbBindArrow()` generics. #' Parametrized queries are different from normal queries #' in that they allow an arbitrary number of placeholders, #' which are later substituted by actual values. #' Parametrized queries (and statements) serve two purposes: #' #' - The same query can be executed more than once with different values. #' The DBMS may cache intermediate information for the query, #' such as the execution plan, and execute it faster. #' - Separation of query syntax and parameters protects against SQL injection. #' #' The placeholder format is currently not specified by \pkg{DBI}; #' in the future, a uniform placeholder syntax may be supported. #' Consult the backend documentation for the supported formats. #' For automated testing, backend authors specify the placeholder syntax with #' the `placeholder_pattern` tweak. #' Known examples are: #' #' - `?` (positional matching in order of appearance) in \pkg{RMariaDB} and \pkg{RSQLite} #' - `$1` (positional matching by index) in \pkg{RPostgres} and \pkg{RSQLite} #' - `:name` and `$name` (named matching) in \pkg{RSQLite} #' #' @section The data retrieval flow: #' #' This section gives a complete overview over the flow #' for the execution of queries that return tabular data as data frames. #' #' Most of this flow, except repeated calling of [dbBind()] or [dbBindArrow()], #' is implemented by [dbGetQuery()], which should be sufficient #' unless you want to access the results in a paged way #' or you have a parameterized query that you want to reuse. #' This flow requires an active connection established by [dbConnect()]. #' See also `vignette("dbi-advanced")` for a walkthrough. #' #' 1. Use [dbSendQuery()] to create a result set object of class #' [DBIResult-class]. #' 1. Optionally, bind query parameters with [dbBind()] or [dbBindArrow()]. #' This is required only if the query contains placeholders #' such as `?` or `$1`, depending on the database backend. #' 1. Optionally, use [dbColumnInfo()] to retrieve the structure of the result set #' without retrieving actual data. #' 1. Use [dbFetch()] to get the entire result set, a page of results, #' or the remaining rows. #' Fetching zero rows is also possible to retrieeve the structure of the result set #' as a data frame. #' This step can be called multiple times. #' Only forward paging is supported, you need to cache previous pages #' if you need to navigate backwards. #' 1. Use [dbHasCompleted()] to tell when you're done. #' This method returns `TRUE` if no more rows are available for fetching. #' 1. Repeat the last four steps as necessary. #' 1. Use [dbClearResult()] to clean up the result set object. #' This step is mandatory even if no rows have been fetched #' or if an error has occurred during the processing. #' It is good practice to use [on.exit()] or [withr::defer()] #' to ensure that this step is always executed. #' #' @section The data retrieval flow for Arrow streams: #' #' This section gives a complete overview over the flow #' for the execution of queries that return tabular data as an Arrow stream. #' #' Most of this flow, except repeated calling of [dbBindArrow()] or [dbBind()], #' is implemented by [dbGetQueryArrow()], #' which should be sufficient #' unless you have a parameterized query that you want to reuse. #' This flow requires an active connection established by [dbConnect()]. #' See also `vignette("dbi-advanced")` for a walkthrough. #' #' 1. Use [dbSendQueryArrow()] to create a result set object of class #' [DBIResultArrow-class]. #' 1. Optionally, bind query parameters with [dbBindArrow()] or [dbBind()]. #' This is required only if the query contains placeholders #' such as `?` or `$1`, depending on the database backend. #' 1. Use [dbFetchArrow()] to get a data stream. #' 1. Repeat the last two steps as necessary. #' 1. Use [dbClearResult()] to clean up the result set object. #' This step is mandatory even if no rows have been fetched #' or if an error has occurred during the processing. #' It is good practice to use [on.exit()] or [withr::defer()] #' to ensure that this step is always executed. #' #' @section The command execution flow: #' #' This section gives a complete overview over the flow #' for the execution of SQL statements that have side effects #' such as stored procedures, inserting or deleting data, #' or setting database or connection options. #' Most of this flow, except repeated calling of [dbBindArrow()], #' is implemented by [dbExecute()], which should be sufficient #' for non-parameterized queries. #' This flow requires an active connection established by [dbConnect()]. #' See also `vignette("dbi-advanced")` for a walkthrough. #' #' 1. Use [dbSendStatement()] to create a result set object of class #' [DBIResult-class]. #' For some queries you need to pass `immediate = TRUE`. #' 1. Optionally, bind query parameters with[dbBind()] or [dbBindArrow()]. #' This is required only if the query contains placeholders #' such as `?` or `$1`, depending on the database backend. #' 1. Optionally, use [dbGetRowsAffected()] to retrieve the number #' of rows affected by the query. #' 1. Repeat the last two steps as necessary. #' 1. Use [dbClearResult()] to clean up the result set object. #' This step is mandatory even if no rows have been fetched #' or if an error has occurred during the processing. #' It is good practice to use [on.exit()] or [withr::defer()] #' to ensure that this step is always executed. #' #' @template methods #' @templateVar method_name dbBind #' #' @inherit DBItest::spec_meta_bind return #' @inheritSection DBItest::spec_meta_bind Failure modes #' @inheritSection DBItest::spec_meta_bind Specification #' #' @inheritParams dbClearResult #' @param params For `dbBind()`, a list of values, named or unnamed, #' or a data frame, with one element/column per query parameter. #' For `dbBindArrow()`, values as a nanoarrow stream, #' with one column per query parameter. #' @family DBIResult generics #' @family DBIResultArrow generics #' @family data retrieval generics #' @family command execution generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' # Data frame flow: #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "iris", iris) #' #' # Using the same query for different values #' iris_result <- dbSendQuery(con, "SELECT * FROM iris WHERE [Petal.Width] > ?") #' dbBind(iris_result, list(2.3)) #' dbFetch(iris_result) #' dbBind(iris_result, list(3)) #' dbFetch(iris_result) #' dbClearResult(iris_result) #' #' # Executing the same statement with different values at once #' iris_result <- dbSendStatement(con, "DELETE FROM iris WHERE [Species] = $species") #' dbBind(iris_result, list(species = c("setosa", "versicolor", "unknown"))) #' dbGetRowsAffected(iris_result) #' dbClearResult(iris_result) #' #' nrow(dbReadTable(con, "iris")) #' #' dbDisconnect(con) #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' #' # Arrow flow: #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "iris", iris) #' #' # Using the same query for different values #' iris_result <- dbSendQueryArrow(con, "SELECT * FROM iris WHERE [Petal.Width] > ?") #' dbBindArrow( #' iris_result, #' nanoarrow::as_nanoarrow_array_stream(data.frame(2.3, fix.empty.names = FALSE)) #' ) #' as.data.frame(dbFetchArrow(iris_result)) #' dbBindArrow( #' iris_result, #' nanoarrow::as_nanoarrow_array_stream(data.frame(3, fix.empty.names = FALSE)) #' ) #' as.data.frame(dbFetchArrow(iris_result)) #' dbClearResult(iris_result) #' #' # Executing the same statement with different values at once #' iris_result <- dbSendStatement(con, "DELETE FROM iris WHERE [Species] = $species") #' dbBindArrow(iris_result, nanoarrow::as_nanoarrow_array_stream(data.frame( #' species = c("setosa", "versicolor", "unknown") #' ))) #' dbGetRowsAffected(iris_result) #' dbClearResult(iris_result) #' #' nrow(dbReadTable(con, "iris")) #' #' dbDisconnect(con) setGeneric("dbBind", def = function(res, params, ...) standardGeneric("dbBind") ) DBI/R/04-DBIResult.R0000644000176200001440000000270714552712156013230 0ustar liggesusersNULL #' DBIResult class #' #' This virtual class describes the result and state of execution of #' a DBMS statement (any statement, query or non-query). The result set #' keeps track of whether the statement produces output how many rows were #' affected by the operation, how many rows have been fetched (if statement is #' a query), whether there are more rows to fetch, etc. #' #' @section Implementation notes: #' Individual drivers are free to allow single or multiple #' active results per connection. #' #' The default show method displays a summary of the query using other #' DBI generics. #' #' @name DBIResult-class #' @docType class #' @family DBI classes #' @family DBIResult generics #' @export setClass("DBIResult", contains = c("DBIObject", "VIRTUAL")) show_result <- function(object) { cat("<", is(object)[1], ">\n", sep = "") if (!dbIsValid(object)) { cat("EXPIRED\n") } else { cat(" SQL ", dbGetStatement(object), "\n", sep = "") done <- if (dbHasCompleted(object)) "complete" else "incomplete" cat(" ROWS Fetched: ", dbGetRowCount(object), " [", done, "]\n", sep = "") cat(" Changed: ", dbGetRowsAffected(object), "\n", sep = "") } } #' @name dbGetInfo #' @section Implementation notes: #' The default implementation for `DBIResult objects` #' constructs such a list from the return values of the corresponding methods, #' [dbGetStatement()], [dbGetRowCount()], #' [dbGetRowsAffected()], and [dbHasCompleted()]. NULL DBI/R/dbGetRowCount_DBIResultArrow.R0000644000176200001440000000037414552712156016626 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbGetRowCount_DBIResultArrow <- function(res, ...) { dbGetRowCount(res@result, ...) } #' @rdname hidden_aliases #' @export setMethod("dbGetRowCount", signature("DBIResultArrow"), dbGetRowCount_DBIResultArrow) DBI/R/13-dbWriteTable.R0000644000176200001440000000364514552712323014001 0ustar liggesusers#' Copy data frames to database tables #' #' Writes, overwrites or appends a data frame to a database table, optionally #' converting row names to a column and specifying SQL data types for fields. #' #' @details #' This function expects a data frame. #' Use [dbWriteTableArrow()] to write an Arrow object. #' #' This function is useful if you want to create and load a table at the same time. #' Use [dbAppendTable()] or [dbAppendTableArrow()] for appending data to an existing #' table, [dbCreateTable()] or [dbCreateTableArrow()] for creating a table, #' and [dbExistsTable()] and [dbRemoveTable()] for overwriting tables. #' #' DBI only standardizes writing data frames with `dbWriteTable()`. #' Some backends might implement methods that can consume CSV files #' or other data formats. #' For details, see the documentation for the individual methods. #' #' @template methods #' @templateVar method_name dbWriteTable #' #' @inherit DBItest::spec_sql_write_table return #' @inheritSection DBItest::spec_sql_write_table Failure modes #' @inheritSection DBItest::spec_sql_write_table Additional arguments #' @inheritSection DBItest::spec_sql_write_table Specification #' #' @inheritParams dbGetQuery #' @inheritParams dbReadTable #' @param value A [data.frame] (or coercible to data.frame). #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars[1:5, ]) #' dbReadTable(con, "mtcars") #' #' dbWriteTable(con, "mtcars", mtcars[6:10, ], append = TRUE) #' dbReadTable(con, "mtcars") #' #' dbWriteTable(con, "mtcars", mtcars[1:10, ], overwrite = TRUE) #' dbReadTable(con, "mtcars") #' #' # No row names #' dbWriteTable(con, "mtcars", mtcars[1:10, ], overwrite = TRUE, row.names = FALSE) #' dbReadTable(con, "mtcars") setGeneric("dbWriteTable", def = function(conn, name, value, ...) standardGeneric("dbWriteTable") ) DBI/R/21-dbAppendTableArrow.R0000644000176200001440000000240014552712323015114 0ustar liggesusers#' Insert rows into a table from an Arrow stream #' #' @description #' `r lifecycle::badge('experimental')` #' #' The `dbAppendTableArrow()` method assumes that the table has been created #' beforehand, e.g. with [dbCreateTableArrow()]. #' The default implementation calls [dbAppendTable()] for each chunk #' of the stream. #' Use [dbAppendTable()] to append data from a data.frame. #' #' @inheritParams dbReadTable #' @param value An object coercible with [nanoarrow::as_nanoarrow_array_stream()]. #' @inheritParams sqlAppendTableTemplate #' #' @template methods #' @templateVar method_name dbAppendTableArrow #' #' @inherit DBItest::spec_arrow_append_table_arrow return #' @inheritSection DBItest::spec_arrow_append_table_arrow Failure modes #' @inheritSection DBItest::spec_arrow_append_table_arrow Specification #' #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' dbCreateTableArrow(con, "iris", iris[0, ]) #' dbAppendTableArrow(con, "iris", iris[1:5, ]) #' dbReadTable(con, "iris") #' dbDisconnect(con) setGeneric("dbAppendTableArrow", def = function(conn, name, value, ...) standardGeneric("dbAppendTableArrow") ) DBI/R/dbGetRowCount.R0000644000176200001440000000162014552712201013720 0ustar liggesusers#' The number of rows fetched so far #' #' Returns the total number of rows actually fetched with calls to [dbFetch()] #' for this result set. #' #' @template methods #' @templateVar method_name dbGetRowCount #' #' @inherit DBItest::spec_meta_get_row_count return #' @inheritSection DBItest::spec_meta_get_row_count Failure modes #' #' @inheritParams dbClearResult #' @family DBIResult generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' rs <- dbSendQuery(con, "SELECT * FROM mtcars") #' #' dbGetRowCount(rs) #' ret1 <- dbFetch(rs, 10) #' dbGetRowCount(rs) #' ret2 <- dbFetch(rs) #' dbGetRowCount(rs) #' nrow(ret1) + nrow(ret2) #' #' dbClearResult(rs) #' dbDisconnect(con) setGeneric("dbGetRowCount", def = function(res, ...) standardGeneric("dbGetRowCount"), valueClass = "numeric" ) DBI/R/sqlCreateTable_DBIConnection.R0000644000176200001440000000166014350241735016574 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL sqlCreateTable_DBIConnection <- function(con, table, fields, row.names = NA, temporary = FALSE, ...) { if (missing(row.names)) { warning("Do not rely on the default value of the row.names argument for sqlCreateTable(), it will change in the future.", call. = FALSE ) } table <- dbQuoteIdentifier(con, table) if (is.data.frame(fields)) { fields <- sqlRownamesToColumn(fields, row.names) fields <- vapply(fields, function(x) DBI::dbDataType(con, x), character(1)) } field_names <- dbQuoteIdentifier(con, names(fields)) field_types <- unname(fields) fields <- paste0(field_names, " ", field_types) SQL(paste0( "CREATE ", if (temporary) "TEMPORARY ", "TABLE ", table, " (\n", " ", paste(fields, collapse = ",\n "), "\n)\n" )) } #' @rdname hidden_aliases #' @export setMethod("sqlCreateTable", signature("DBIConnection"), sqlCreateTable_DBIConnection) DBI/R/dbWriteTableArrow_DBIConnection.R0000644000176200001440000000205514552712323017263 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbWriteTableArrow_DBIConnection <- function(conn, name, value, append = FALSE, overwrite = FALSE, ..., temporary = FALSE) { require_arrow() stopifnot(is.logical(append)) stopifnot(length(append) == 1) stopifnot(!is.na(append)) stopifnot(is.logical(overwrite)) stopifnot(length(overwrite) == 1) stopifnot(!is.na(overwrite)) stopifnot(is.logical(temporary)) stopifnot(length(temporary) == 1) stopifnot(!is.na(temporary)) name <- dbQuoteIdentifier(conn, name) value <- nanoarrow::as_nanoarrow_array_stream(value) if (overwrite && append) { stop("overwrite and append cannot both be TRUE") } exists <- dbExistsTable(conn, name) if (overwrite && exists) { dbRemoveTable(conn, name) } if (overwrite || !append || !exists) { dbCreateTableArrow(conn, name, value, temporary = temporary) } dbAppendTableArrow(conn, name, value) invisible(TRUE) } #' @rdname hidden_aliases #' @export setMethod("dbWriteTableArrow", signature("DBIConnection"), dbWriteTableArrow_DBIConnection) DBI/R/hms.R0000644000176200001440000000401014350241735011762 0ustar liggesusers# from hms format_hms <- function(x) { units(x) <- "secs" xx <- decompose(x) ifelse(is.na(x), NA_character_, paste0( ifelse(xx$sign, "-", ""), format_hours(xx$hours), ":", format_two_digits(xx$minute_of_hour), ":", format_two_digits(xx$second_of_minute), format_tics(xx$tics))) } format_hours <- function(x) { # Difference to hms: don't justify here format_two_digits(x) } format_two_digits <- function(x) { formatC(x, format = "f", digits = 0, width = 2, flag = "0") } format_tics <- function(x) { x <- x / TICS_PER_SECOND out <- format(x, scientific = FALSE, digits = SPLIT_SECOND_DIGITS + 1L) digits <- max(min(max(nchar(out) - 2), SPLIT_SECOND_DIGITS), 0) out <- formatC(x, format = "f", digits = digits) gsub("^0", "", out) } SPLIT_SECOND_DIGITS <- 6L TICS_PER_SECOND <- 10^SPLIT_SECOND_DIGITS SECONDS_PER_MINUTE <- 60 MINUTES_PER_HOUR <- 60 HOURS_PER_DAY <- 24 TICS_PER_MINUTE <- SECONDS_PER_MINUTE * TICS_PER_SECOND TICS_PER_HOUR <- MINUTES_PER_HOUR * TICS_PER_MINUTE TICS_PER_DAY <- HOURS_PER_DAY * TICS_PER_HOUR days <- function(x) { trunc(x / TICS_PER_DAY) } hours <- function(x) { trunc(x / TICS_PER_HOUR) } hour_of_day <- function(x) { abs(hours(x) - days(x) * HOURS_PER_DAY) } minutes <- function(x) { trunc(x / TICS_PER_MINUTE) } minute_of_hour <- function(x) { abs(minutes(x) - hours(x) * MINUTES_PER_HOUR) } seconds <- function(x) { trunc(x / TICS_PER_SECOND) } second_of_minute <- function(x) { abs(seconds(x) - minutes(x) * SECONDS_PER_MINUTE) } tics <- function(x) { x } tic_of_second <- function(x) { abs(tics(x) - seconds(x) * TICS_PER_SECOND) } decompose <- function(x) { x <- unclass(x) * TICS_PER_SECOND # #140 xr <- round(x) out <- list( sign = xr < 0 & !is.na(xr), hours = abs(hours(xr)), minute_of_hour = minute_of_hour(xr), second_of_minute = second_of_minute(xr), tics = tic_of_second(xr) ) # #140: Make sure zeros are printed fake_zero <- (out$tics == 0) & (xr != x) out$tics[fake_zero] <- 0.25 out } DBI/R/show_DBIResult.R0000644000176200001440000000060514350241735014036 0ustar liggesusers#' @rdname hidden_aliases #' @param object Object to display #' @usage NULL show_DBIResult <- function(object) { # to protect drivers that fail to implement the required methods (e.g., # RPostgreSQL) tryCatch( show_result(object), error = function(e) NULL ) invisible(NULL) } #' @rdname hidden_aliases #' @export setMethod("show", signature("DBIResult"), show_DBIResult) DBI/R/dbQuoteIdentifier.R0000644000176200001440000000263414552712323014613 0ustar liggesusers#' Quote identifiers #' #' Call this method to generate a string that is suitable for #' use in a query as a column or table name, to make sure that you #' generate valid SQL and protect against SQL injection attacks. The inverse #' operation is [dbUnquoteIdentifier()]. #' #' @inheritParams dbGetQuery #' @param x A character vector, [SQL] or [Id] object to quote as identifier. #' @param ... Other arguments passed on to methods. #' #' @template methods #' @templateVar method_name dbQuoteIdentifier #' #' @inherit DBItest::spec_sql_quote_identifier return #' @inheritSection DBItest::spec_sql_quote_identifier Failure modes #' @inheritSection DBItest::spec_sql_quote_identifier Specification #' #' @family DBIConnection generics #' @export #' @examples #' # Quoting ensures that arbitrary input is safe for use in a query #' name <- "Robert'); DROP TABLE Students;--" #' dbQuoteIdentifier(ANSI(), name) #' #' # Use Id() to specify other components such as the schema #' id_name <- Id(schema = "schema_name", table = "table_name") #' id_name #' dbQuoteIdentifier(ANSI(), id_name) #' #' # SQL vectors are always passed through as is #' var_name <- SQL("select") #' var_name #' dbQuoteIdentifier(ANSI(), var_name) #' #' # This mechanism is used to prevent double escaping #' dbQuoteIdentifier(ANSI(), dbQuoteIdentifier(ANSI(), name)) setGeneric("dbQuoteIdentifier", def = function(conn, x, ...) standardGeneric("dbQuoteIdentifier") ) DBI/R/sqlInterpolate_DBIConnection.R0000644000176200001440000000244714350241735016713 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL sqlInterpolate_DBIConnection <- function(conn, sql, ..., .dots = list()) { pos <- sqlParseVariables(conn, sql) if (length(pos$start) == 0) { return(SQL(sql)) } vars <- substring(sql, pos$start + 1, pos$end) positional_vars <- pos$start == pos$end if (all(positional_vars) != any(positional_vars)) { stop("Can't mix positional (?) and named (?asdf) variables", call. = FALSE) } values <- c(list(...), .dots) if (all(positional_vars)) { if (length(vars) != length(values)) { stop("Supplied values don't match positional vars to interpolate", call. = FALSE) } if (any(names(values) != "")) { stop("Positional variables don't take named arguments") } } else { if (!setequal(vars, names(values))) { stop("Supplied values don't match named vars to interpolate", call. = FALSE) } values <- values[vars] } safe_values <- vapply(values, function(x) dbQuoteLiteral(conn, x), character(1)) for (i in rev(seq_along(vars))) { sql <- paste0( substring(sql, 0, pos$start[i] - 1), safe_values[i], substring(sql, pos$end[i] + 1, nchar(sql)) ) } SQL(sql) } #' @rdname hidden_aliases #' @export setMethod("sqlInterpolate", signature("DBIConnection"), sqlInterpolate_DBIConnection) DBI/R/dbListConnections.R0000644000176200001440000000072414350241735014627 0ustar liggesusers#' List currently open connections #' #' DEPRECATED, drivers are no longer required to implement this method. #' Keep track of the connections you opened if you require a list. #' #' @param drv A object inheriting from [DBIDriver-class] #' @param ... Other arguments passed on to methods. #' @family DBIDriver generics #' @keywords internal #' @export #' @return a list setGeneric("dbListConnections", def = function(drv, ...) standardGeneric("dbListConnections") ) DBI/R/sqlData.R0000644000176200001440000000206014552712201012562 0ustar liggesusers#' Convert a data frame into form suitable for upload to an SQL database #' #' This is a generic method that coerces R objects into vectors suitable for #' upload to the database. The output will vary a little from method to #' method depending on whether the main upload device is through a single #' SQL string or multiple parameterized queries. #' This method is mostly useful for backend implementers. #' #' The default method: #' #' - Converts factors to characters #' - Quotes all strings with [dbQuoteIdentifier()] #' - Converts all columns to strings with [dbQuoteLiteral()] #' - Replaces NA with NULL #' #' @inheritParams sqlCreateTable #' @inheritParams rownames #' @param value A data frame #' #' @template methods #' @templateVar method_name sqlData #' #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' sqlData(con, head(iris)) #' sqlData(con, head(mtcars)) #' #' dbDisconnect(con) setGeneric("sqlData", def = function(con, value, row.names = NA, ...) standardGeneric("sqlData") ) DBI/R/14-dbSendQuery.R0000644000176200001440000000530014552712323013645 0ustar liggesusers#' Execute a query on a given database connection #' #' The `dbSendQuery()` method only submits and synchronously executes the #' SQL query to the database engine. It does \emph{not} extract any #' records --- for that you need to use the [dbFetch()] method, and #' then you must call [dbClearResult()] when you finish fetching the #' records you need. #' For interactive use, you should almost always prefer [dbGetQuery()]. #' Use [dbSendQueryArrow()] or [dbGetQueryArrow()] instead to retrieve the results #' as an Arrow object. #' #' This method is for `SELECT` queries only. Some backends may #' support data manipulation queries through this method for compatibility #' reasons. However, callers are strongly encouraged to use #' [dbSendStatement()] for data manipulation statements. #' #' The query is submitted to the database server and the DBMS executes it, #' possibly generating vast amounts of data. Where these data live #' is driver-specific: some drivers may choose to leave the output on the server #' and transfer them piecemeal to R, others may transfer all the data to the #' client -- but not necessarily to the memory that R manages. See individual #' drivers' `dbSendQuery()` documentation for details. #' #' @inheritSection dbBind The data retrieval flow #' #' @template methods #' @templateVar method_name dbSendQuery #' #' @inherit DBItest::spec_result_send_query return #' @inheritSection DBItest::spec_result_send_query Failure modes #' @inheritSection DBItest::spec_result_send_query Additional arguments #' @inheritSection DBItest::spec_result_send_query Specification #' @inheritSection DBItest::spec_result_send_query Specification for the `immediate` argument #' #' @inheritParams dbGetQuery #' @param statement a character string containing SQL. #' #' @family DBIConnection generics #' @family data retrieval generics #' @seealso For updates: [dbSendStatement()] and [dbExecute()]. #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4") #' dbFetch(rs) #' dbClearResult(rs) #' #' # Pass one set of values with the param argument: #' rs <- dbSendQuery( #' con, #' "SELECT * FROM mtcars WHERE cyl = ?", #' params = list(4L) #' ) #' dbFetch(rs) #' dbClearResult(rs) #' #' # Pass multiple sets of values with dbBind(): #' rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = ?") #' dbBind(rs, list(6L)) #' dbFetch(rs) #' dbBind(rs, list(8L)) #' dbFetch(rs) #' dbClearResult(rs) #' #' dbDisconnect(con) #' @export setGeneric("dbSendQuery", def = function(conn, statement, ...) standardGeneric("dbSendQuery"), valueClass = "DBIResult" ) DBI/R/dbListResults.R0000644000176200001440000000100614350241735014000 0ustar liggesusers#' A list of all pending results #' #' DEPRECATED. DBI currenty supports only one open result set per connection, #' you need to keep track of the result sets you open if you need this #' functionality. #' #' @inheritParams dbGetQuery #' @family DBIConnection generics #' @return a list. If no results are active, an empty list. If only #' a single result is active, a list with one element. #' @export #' @keywords internal setGeneric("dbListResults", def = function(conn, ...) standardGeneric("dbListResults") ) DBI/R/SQLKeywords_missing.R0000644000176200001440000000033414350241735015120 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL SQLKeywords_missing <- function(dbObj, ...) .SQL92Keywords #' @rdname hidden_aliases setMethod("SQLKeywords", signature("missing"), SQLKeywords_missing, valueClass = "character") DBI/R/show_AnsiConnection.R0000644000176200001440000000032014350241735015145 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL show_AnsiConnection <- function(object) { cat("\n") } #' @rdname hidden_aliases #' @export setMethod("show", "AnsiConnection", show_AnsiConnection) DBI/R/isSQLKeyword_DBIObject_character.R0000644000176200001440000000050714350241735017363 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL isSQLKeyword_DBIObject_character <- function(dbObj, name, keywords, case, ...) isSQLKeyword.default(name, keywords, case) #' @rdname hidden_aliases setMethod("isSQLKeyword", signature(dbObj = "DBIObject", name = "character"), isSQLKeyword_DBIObject_character, valueClass = "logical") DBI/R/dbListFields.R0000644000176200001440000000146714552712201013553 0ustar liggesusers#' List field names of a remote table #' #' Returns the field names of a remote table as a character vector. #' #' @inheritParams dbReadTable #' #' @template methods #' @templateVar method_name dbListFields #' #' @inherit DBItest::spec_sql_list_fields return #' @inheritSection DBItest::spec_sql_list_fields Failure modes #' @inheritSection DBItest::spec_sql_list_fields Specification #' #' @family DBIConnection generics #' @seealso [dbColumnInfo()] to get the type of the fields. #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' dbListFields(con, "mtcars") #' #' dbDisconnect(con) setGeneric("dbListFields", def = function(conn, name, ...) standardGeneric("dbListFields"), valueClass = "character" ) DBI/R/dbListObjects_DBIConnection_ANY.R0000644000176200001440000000072214350241735017141 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbListObjects_DBIConnection_ANY <- function(conn, prefix = NULL, ...) { names <- dbListTables(conn) tables <- lapply(names, function(x) Id(table = x)) ret <- data.frame( table = I(unname(tables)), stringsAsFactors = FALSE ) ret$is_prefix <- rep_len(FALSE, nrow(ret)) ret } #' @rdname hidden_aliases #' @export setMethod("dbListObjects", signature("DBIConnection", "ANY"), dbListObjects_DBIConnection_ANY) DBI/R/dbUnloadDriver.R0000644000176200001440000000034714350241735014110 0ustar liggesusers#' @description #' `dbUnloadDriver()` is not implemented for modern backends. #' @rdname dbDriver #' @family DBIDriver generics #' @export setGeneric("dbUnloadDriver", def = function(drv, ...) standardGeneric("dbUnloadDriver") ) DBI/R/dbGetRowsAffected.R0000644000176200001440000000164514552712201014523 0ustar liggesusers#' The number of rows affected #' #' This method returns the number of rows that were added, deleted, or updated #' by a data manipulation statement. #' #' @inheritSection dbBind The command execution flow #' #' @template methods #' @templateVar method_name dbGetRowsAffected #' #' @inherit DBItest::spec_meta_get_rows_affected return #' @inheritSection DBItest::spec_meta_get_rows_affected Failure modes #' #' @inheritParams dbClearResult #' @family DBIResult generics #' @family command execution generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' rs <- dbSendStatement(con, "DELETE FROM mtcars") #' dbGetRowsAffected(rs) #' nrow(mtcars) #' #' dbClearResult(rs) #' dbDisconnect(con) setGeneric("dbGetRowsAffected", def = function(res, ...) standardGeneric("dbGetRowsAffected"), valueClass = "numeric" ) DBI/R/dbAppendTable_DBIConnection.R0000644000176200001440000000114114350241735016360 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbAppendTable_DBIConnection <- function(conn, name, value, ..., row.names = NULL) { if (!is.null(row.names)) { stop("Can't pass `row.names` to `dbAppendTable()`", call. = FALSE) } stopifnot(is.data.frame(value)) query <- sqlAppendTableTemplate( con = conn, table = name, values = value, row.names = row.names, prefix = "?", pattern = "", ... ) dbExecute(conn, query, params = unname(as.list(value))) } #' @rdname hidden_aliases #' @export setMethod("dbAppendTable", signature("DBIConnection"), dbAppendTable_DBIConnection) DBI/R/sqlAppendTable.R0000644000176200001440000000213514350241735014100 0ustar liggesusers#' Compose query to insert rows into a table #' #' `sqlAppendTable()` generates a single SQL string that inserts a #' data frame into an existing table. `sqlAppendTableTemplate()` generates #' a template suitable for use with [dbBind()]. #' The default methods are ANSI SQL 99 compliant. #' These methods are mostly useful for backend implementers. #' #' The `row.names` argument must be passed explicitly in order to avoid #' a compatibility warning. The default will be changed in a later release. #' #' @inheritParams sqlCreateTable #' @inheritParams rownames #' @param values A data frame. Factors will be converted to character vectors. #' Character vectors will be escaped with [dbQuoteString()]. #' #' @template methods #' @templateVar method_name sqlAppendTable #' #' @family SQL generation #' @export #' @examples #' sqlAppendTable(ANSI(), "iris", head(iris)) #' #' sqlAppendTable(ANSI(), "mtcars", head(mtcars)) #' sqlAppendTable(ANSI(), "mtcars", head(mtcars), row.names = FALSE) setGeneric("sqlAppendTable", def = function(con, table, values, row.names = NA, ...) standardGeneric("sqlAppendTable") ) DBI/R/show_Id.R0000644000176200001440000000035114537352607012603 0ustar liggesusers#' @rdname hidden_aliases #' @param object Table object to print #' @usage NULL show_Id <- function(object) { cat(toString(object), "\n", sep = "") } #' @rdname hidden_aliases #' @export setMethod("show", signature("Id"), show_Id) DBI/R/dbiDataType_numeric.R0000644000176200001440000000020014350241735015104 0ustar liggesusers#' @usage NULL dbiDataType_numeric <- function(x) "DOUBLE" setMethod("dbiDataType", signature("numeric"), dbiDataType_numeric) DBI/R/dbiDataType_data.frame.R0000644000176200001440000000027214350241735015455 0ustar liggesusersdbiDataType_data.frame <- function(x) { vapply(x, dbiDataType, FUN.VALUE = character(1), USE.NAMES = TRUE) } setMethod("dbiDataType", signature("data.frame"), dbiDataType_data.frame) DBI/R/dbReadTable_DBIConnection_Id.R0000644000176200001440000000043514350241735016445 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbReadTable_DBIConnection_Id <- function(conn, name, ...) { dbReadTable(conn, dbQuoteIdentifier(conn, name), ...) } #' @rdname hidden_aliases #' @export setMethod("dbReadTable", signature("DBIConnection", "Id"), dbReadTable_DBIConnection_Id) DBI/R/sqlAppendTable_DBIConnection.R0000644000176200001440000000155514350241735016603 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL sqlAppendTable_DBIConnection <- function(con, table, values, row.names = NA, ...) { stopifnot(is.list(values)) if (missing(row.names)) { warning("Do not rely on the default value of the row.names argument for sqlAppendTable(), it will change in the future.", call. = FALSE ) } sql_values <- sqlData(con, values, row.names) table <- dbQuoteIdentifier(con, table) fields <- dbQuoteIdentifier(con, names(sql_values)) # Convert fields into a character matrix rows <- do.call(paste, c(unname(sql_values), sep = ", ")) SQL(paste0( "INSERT INTO ", table, "\n", " (", paste(fields, collapse = ", "), ")\n", "VALUES\n", paste0(" (", rows, ")", collapse = ",\n") )) } #' @rdname hidden_aliases #' @export setMethod("sqlAppendTable", signature("DBIConnection"), sqlAppendTable_DBIConnection) DBI/R/make.db.names.R0000644000176200001440000000571614350241735013614 0ustar liggesusers#' Make R identifiers into legal SQL identifiers #' #' These methods are DEPRECATED. Please use [dbQuoteIdentifier()] #' (or possibly [dbQuoteString()]) instead. #' #' The algorithm in `make.db.names` first invokes `make.names` and #' then replaces each occurrence of a dot `.` by an underscore `_`. If #' `allow.keywords` is `FALSE` and identifiers collide with SQL #' keywords, a small integer is appended to the identifier in the form of #' `"_n"`. #' #' 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. #' #' @section Bugs: #' The current mapping is not guaranteed to be fully reversible: some SQL #' identifiers that get mapped into R identifiers with `make.names` and #' then back to SQL with [make.db.names()] will not be equal to the #' original SQL identifiers (e.g., compound SQL identifiers of the form #' `username.tablename` will loose the dot ``.''). #' #' @references 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. #' @aliases #' make.db.names #' SQLKeywords #' isSQLKeyword #' @param dbObj any DBI object (e.g., `DBIDriver`). #' @param snames a character vector of R identifiers (symbols) from which we #' need to make SQL identifiers. #' @param name a character vector with database identifier candidates we need #' to determine whether they are legal SQL identifiers or not. #' @param unique 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. #' @param allow.keywords logical describing whether SQL keywords should be #' allowed in the resulting set of SQL names. Its default is `TRUE` #' @param keywords a character vector with SQL keywords, by default it's #' `.SQL92Keywords` defined by the DBI. #' @param case a character string specifying whether to make the comparison as #' lower case, upper case, or any of the two. it defaults to `any`. #' @param \dots any other argument are passed to the driver implementation. #' @return `make.db.names` returns a character vector of legal SQL #' identifiers corresponding to its `snames` argument. #' #' `SQLKeywords` returns a character vector of all known keywords for the #' database-engine associated with `dbObj`. #' #' `isSQLKeyword` returns a logical vector parallel to `name`. #' @export #' @keywords internal setGeneric("make.db.names", def = function(dbObj, snames, keywords = .SQL92Keywords, unique = TRUE, allow.keywords = TRUE, ...) standardGeneric("make.db.names"), signature = c("dbObj", "snames"), valueClass = "character" ) DBI/R/SQLKeywords_DBIObject.R0000644000176200001440000000034214350241735015173 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL SQLKeywords_DBIObject <- function(dbObj, ...) .SQL92Keywords #' @rdname hidden_aliases setMethod("SQLKeywords", signature("DBIObject"), SQLKeywords_DBIObject, valueClass = "character") DBI/R/SQLKeywords.R0000644000176200001440000000040014350241735013361 0ustar liggesusers## SQL ANSI 92 (plus ISO's) keywords --- all 220 of them! ## (See pp. 22 and 23 in X/Open SQL and RDA, 1994, isbn 1-872630-68-8) #' @export setGeneric("SQLKeywords", def = function(dbObj, ...) standardGeneric("SQLKeywords"), valueClass = "character" ) DBI/R/fetch.R0000644000176200001440000000021514350241735012267 0ustar liggesusers#' @rdname dbFetch #' @export setGeneric("fetch", def = function(res, n = -1, ...) standardGeneric("fetch"), valueClass = "data.frame" ) DBI/R/dbFetchArrow.R0000644000176200001440000000255014552712323013554 0ustar liggesusers#' Fetch records from a previously executed query as an Arrow object #' #' @description #' `r lifecycle::badge('experimental')` #' #' Fetch the result set and return it as an Arrow object. #' Use [dbFetchArrowChunk()] to fetch results in chunks. #' #' @inheritSection dbBind The data retrieval flow for Arrow streams #' #' @template methods #' @templateVar method_name dbFetchArrow #' #' @inherit DBItest::spec_arrow_fetch_arrow return #' @inheritSection DBItest::spec_arrow_fetch_arrow Failure modes #' @inheritSection DBItest::spec_arrow_fetch_arrow Specification #' #' @param res An object inheriting from [DBIResultArrow-class], created by #' [dbSendQueryArrow()]. #' @param ... Other arguments passed on to methods. #' @seealso Close the result set with [dbClearResult()] as soon as you #' finish retrieving the records you want. #' @family DBIResultArrow generics #' @family data retrieval generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' #' # Fetch all results #' rs <- dbSendQueryArrow(con, "SELECT * FROM mtcars WHERE cyl = 4") #' as.data.frame(dbFetchArrow(rs)) #' dbClearResult(rs) #' #' dbDisconnect(con) setGeneric("dbFetchArrow", def = function(res, ...) standardGeneric("dbFetchArrow") ) DBI/R/dbUnquoteIdentifier.R0000644000176200001440000000243214552712323015152 0ustar liggesusers#' Unquote identifiers #' #' Call this method to convert a [SQL] object created by [dbQuoteIdentifier()] #' back to a list of [Id] objects. #' #' @inheritParams dbGetQuery #' @param x An [SQL] or [Id] object. #' @param ... Other arguments passed on to methods. #' #' @template methods #' @templateVar method_name dbUnquoteIdentifier #' #' @inherit DBItest::spec_sql_unquote_identifier return #' @inheritSection DBItest::spec_sql_unquote_identifier Failure modes #' @inheritSection DBItest::spec_sql_unquote_identifier Specification #' #' @family DBIConnection generics #' @export #' @examples #' # Unquoting allows to understand the structure of a #' # possibly complex quoted identifier #' dbUnquoteIdentifier( #' ANSI(), #' SQL(c('"Catalog"."Schema"."Table"', '"Schema"."Table"', '"UnqualifiedTable"')) #' ) #' #' # The returned object is always a list, #' # also for Id objects #' dbUnquoteIdentifier(ANSI(), Id("Catalog", "Schema", "Table")) #' #' # Quoting and unquoting are inverses #' dbQuoteIdentifier( #' ANSI(), #' dbUnquoteIdentifier(ANSI(), SQL("UnqualifiedTable"))[[1]] #' ) #' #' dbQuoteIdentifier( #' ANSI(), #' dbUnquoteIdentifier(ANSI(), Id("Schema", "Table"))[[1]] #' ) setGeneric("dbUnquoteIdentifier", def = function(conn, x, ...) standardGeneric("dbUnquoteIdentifier") ) DBI/R/sqlAppendTableTemplate.R0000644000176200001440000000275614350241735015605 0ustar liggesusers#' @rdname sqlAppendTable #' @inheritParams sqlCreateTable #' @inheritParams rownames #' @param prefix Parameter prefix to use for placeholders. #' @param pattern Parameter pattern to use for placeholders: #' - `""`: no pattern #' - `"1"`: position #' - anything else: field name #' @export #' @examples #' sqlAppendTableTemplate(ANSI(), "iris", iris) #' #' sqlAppendTableTemplate(ANSI(), "mtcars", mtcars) #' sqlAppendTableTemplate(ANSI(), "mtcars", mtcars, row.names = FALSE) sqlAppendTableTemplate <- function(con, table, values, row.names = NA, prefix = "?", ..., pattern = "") { if (missing(row.names)) { warning("Do not rely on the default value of the `row.names` argument to `sqlAppendTableTemplate()`, it will change in the future.", call. = FALSE ) } if (length(values) == 0) { stop("Must pass at least one column in `values`", call. = FALSE) } table <- dbQuoteIdentifier(con, table) if (length(table) != 1) { stop("Must pass one table name", call. = FALSE) } values <- sqlRownamesToColumn(values[0, , drop = FALSE], row.names) fields <- dbQuoteIdentifier(con, names(values)) if (pattern == "") { suffix <- rep("", length(fields)) } else if (pattern == "1") { suffix <- as.character(seq_along(fields)) } else { suffix <- names(fields) } placeholders <- lapply(paste0(prefix, suffix), SQL) names(placeholders) <- names(values) sqlAppendTable( con = con, table = table, values = placeholders, row.names = row.names ) } DBI/R/dbWithTransaction.R0000644000176200001440000000464414552712201014632 0ustar liggesusers#' Self-contained SQL transactions #' #' Given that \link{transactions} are implemented, this function #' allows you to pass in code that is run in a transaction. #' The default method of `dbWithTransaction()` calls [dbBegin()] #' before executing the code, #' and [dbCommit()] after successful completion, #' or [dbRollback()] in case of an error. #' The advantage is #' that you don't have to remember to do `dbBegin()` and `dbCommit()` or #' `dbRollback()` -- that is all taken care of. #' The special function `dbBreak()` allows an early exit with rollback, #' it can be called only inside `dbWithTransaction()`. #' #' DBI implements `dbWithTransaction()`, backends should need to override this #' generic only if they implement specialized handling. #' #' @template methods #' @templateVar method_name dbWithTransaction #' #' @inherit DBItest::spec_transaction_with_transaction return #' @inheritSection DBItest::spec_transaction_with_transaction Failure modes #' @inheritSection DBItest::spec_transaction_with_transaction Specification #' #' @inheritParams dbGetQuery #' @param code An arbitrary block of R code. #' #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "cash", data.frame(amount = 100)) #' dbWriteTable(con, "account", data.frame(amount = 2000)) #' #' # All operations are carried out as logical unit: #' dbWithTransaction( #' con, #' { #' withdrawal <- 300 #' dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) #' dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) #' } #' ) #' #' # The code is executed as if in the curent environment: #' withdrawal #' #' # The changes are committed to the database after successful execution: #' dbReadTable(con, "cash") #' dbReadTable(con, "account") #' #' # Rolling back with dbBreak(): #' dbWithTransaction( #' con, #' { #' withdrawal <- 5000 #' dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal)) #' dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal)) #' if (dbReadTable(con, "account")$amount < 0) { #' dbBreak() #' } #' } #' ) #' #' # These changes were not committed to the database: #' dbReadTable(con, "cash") #' dbReadTable(con, "account") #' #' dbDisconnect(con) setGeneric("dbWithTransaction", def = function(conn, code, ...) standardGeneric("dbWithTransaction") ) DBI/R/dbReadTableArrow_DBIConnection.R0000644000176200001440000000053114552712156017045 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbReadTableArrow_DBIConnection <- function(conn, name, ...) { sql_name <- dbReadTable_toSqlName(conn, name, ...) dbGetQueryArrow(conn, paste0("SELECT * FROM ", sql_name)) } #' @rdname hidden_aliases #' @export setMethod("dbReadTableArrow", signature("DBIConnection"), dbReadTableArrow_DBIConnection) DBI/R/dbGetQuery.R0000644000176200001440000000503314552712323013254 0ustar liggesusers#' Retrieve results from a query #' #' Returns the result of a query as a data frame. #' `dbGetQuery()` comes with a default implementation #' (which should work with most backends) that calls #' [dbSendQuery()], then [dbFetch()], ensuring that #' the result is always freed by [dbClearResult()]. #' For retrieving chunked/paged results or for passing query parameters, #' see [dbSendQuery()], in particular the "The data retrieval flow" section. #' For retrieving results as an Arrow object, see [dbGetQueryArrow()]. #' #' This method is for `SELECT` queries only #' (incl. other SQL statements that return a `SELECT`-alike result, #' e.g., execution of a stored procedure or data manipulation queries #' like `INSERT INTO ... RETURNING ...`). #' To execute a stored procedure that does not return a result set, #' use [dbExecute()]. #' #' Some backends may #' support data manipulation statements through this method for compatibility #' reasons. However, callers are strongly advised to use #' [dbExecute()] for data manipulation statements. #' #' @template methods #' @templateVar method_name dbGetQuery #' #' @inherit DBItest::spec_result_get_query return #' @inheritSection DBItest::spec_result_get_query Failure modes #' @inheritSection DBItest::spec_result_get_query Additional arguments #' @inheritSection DBItest::spec_result_get_query Specification #' @inheritSection DBItest::spec_result_get_query Specification for the `immediate` argument #' #' @section Implementation notes: #' Subclasses should override this method only if they provide some sort of #' performance optimization. #' #' @param conn A [DBIConnection-class] object, as returned by #' [dbConnect()]. #' @param statement a character string containing SQL. #' @param ... Other parameters passed on to methods. #' @family DBIConnection generics #' @family data retrieval generics #' @seealso For updates: [dbSendStatement()] and [dbExecute()]. #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' dbGetQuery(con, "SELECT * FROM mtcars") #' dbGetQuery(con, "SELECT * FROM mtcars", n = 6) #' #' # Pass values using the param argument: #' # (This query runs eight times, once for each different #' # parameter. The resulting rows are combined into a single #' # data frame.) #' dbGetQuery( #' con, #' "SELECT COUNT(*) FROM mtcars WHERE cyl = ?", #' params = list(1:8) #' ) #' #' dbDisconnect(con) setGeneric("dbGetQuery", def = function(conn, statement, ...) standardGeneric("dbGetQuery") ) DBI/R/dbQuoteIdentifier_DBIConnection.R0000644000176200001440000000253014552712201017277 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbQuoteIdentifier_DBIConnection <- function(conn, x, ...) { # Don't support lists, auto-vectorization violates type stability if (is(x, "SQL")) return(x) if (!is.character(x)) stop("x must be character or SQL", call. = FALSE) if (any(is.na(x))) { stop("Cannot pass NA to dbQuoteIdentifier()", call. = FALSE) } # Avoid fixed = TRUE due to https://github.com/r-dbi/DBItest/issues/156 x <- gsub('"', '""', enc2utf8(x)) if (length(x) == 0L) { SQL(character(), names = names(x)) } else { # Not calling encodeString() here to keep things simple SQL(paste('"', x, '"', sep = ""), names = names(x)) } } #' @rdname hidden_aliases #' @export setMethod("dbQuoteIdentifier", signature("DBIConnection"), dbQuoteIdentifier_DBIConnection) # Need to keep other method declarations around for now, because clients might # use getMethod(), see e.g. https://github.com/r-dbi/odbc/pull/149 #' @rdname hidden_aliases #' @export setMethod("dbQuoteIdentifier", signature("DBIConnection", "character"), dbQuoteIdentifier_DBIConnection) #' @rdname hidden_aliases #' @export setMethod("dbQuoteIdentifier", signature("DBIConnection", "SQL"), dbQuoteIdentifier_DBIConnection) #' @rdname hidden_aliases #' @export setMethod("dbQuoteIdentifier", signature("DBIConnection", "Id"), dbQuoteIdentifier_DBIConnection_Id) DBI/R/summary.R0000644000176200001440000000002614350241735012673 0ustar liggesuserssetGeneric("summary") DBI/R/dbIsReadOnly_DBIConnector.R0000644000176200001440000000035114350241735016047 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbIsReadOnly_DBIConnector <- function(dbObj, ...) { dbIsReadOnly(dbObj@.drv, ...) } #' @rdname hidden_aliases setMethod("dbIsReadOnly", signature("DBIConnector"), dbIsReadOnly_DBIConnector) DBI/R/dbiDataType_ANY.R0000644000176200001440000000035214552712156014105 0ustar liggesusersdbiDataType_ANY <- function(x) { if (inherits(x, "blob")) { return("BLOB") } stop("Unknown SQL data type for object of class ", paste(class(x), collapse = "/")) } setMethod("dbiDataType", signature("ANY"), dbiDataType_ANY) DBI/R/dbiDataType_AsIs.R0000644000176200001440000000022514350241735014310 0ustar liggesusersdbiDataType_AsIs <- function(x) { oldClass(x) <- oldClass(x)[-1] dbiDataType(x) } setMethod("dbiDataType", signature("AsIs"), dbiDataType_AsIs) DBI/R/dbReadTable.R0000644000176200001440000000276314552712323013341 0ustar liggesusers#' Read database tables as data frames #' #' Reads a database table to a data frame, optionally converting #' a column to row names and converting the column names to valid #' R identifiers. #' Use [dbReadTableArrow()] instead to obtain an Arrow object. #' #' @details #' This function returns a data frame. #' Use [dbReadTableArrow()] to obtain an Arrow object. #' #' @template methods #' @templateVar method_name dbReadTable #' #' @inherit DBItest::spec_sql_read_table return #' @inheritSection DBItest::spec_sql_read_table Failure modes #' @inheritSection DBItest::spec_sql_read_table Additional arguments #' @inheritSection DBItest::spec_sql_read_table Specification #' #' @inheritParams dbGetQuery #' @param name The table name, passed on to [dbQuoteIdentifier()]. Options are: #' - a character string with the unquoted DBMS table name, #' e.g. `"table_name"`, #' - a call to [Id()] with components to the fully qualified table name, #' e.g. `Id(schema = "my_schema", table = "table_name")` #' - a call to [SQL()] with the quoted and fully qualified table name #' given verbatim, e.g. `SQL('"my_schema"."table_name"')` #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars[1:10, ]) #' dbReadTable(con, "mtcars") #' #' dbDisconnect(con) setGeneric("dbReadTable", def = function(conn, name, ...) standardGeneric("dbReadTable"), valueClass = "data.frame" ) DBI/R/methods_as_rd.R0000644000176200001440000000413214542471013014010 0ustar liggesusersmethods_as_rd <- function(method) { if (method == "transactions") { method <- c("dbBegin", "dbCommit", "dbRollback") } if (identical(Sys.getenv("IN_PKGDOWN"), "true") && file.exists("DESCRIPTION")) { packages <- strsplit(read.dcf("DESCRIPTION")[, "Config/Needs/website"], ",( |\n)*", perl = TRUE)[[1]] packages <- grep("/", packages, invert = TRUE, value = TRUE) for (package in packages) { stopifnot(requireNamespace(package, quietly = TRUE)) } } methods <- unlist(lapply(method, methods::findMethods), recursive = FALSE) # Extracted from roxygen2::object_topic.s4method s4_topic <- function(x) { sig <- paste0(x@defined, collapse = ",") sig_text <- paste0('"', x@defined, '"', collapse = ", ") package <- unname(tryCatch( getNamespaceName(environment(x@.Data)), error = function(e) NA )) if (is.na(package) || package == "DBI") { return(data.frame()) } topic <- paste0(x@generic, ",", sig, "-method") call <- paste0(package, "::", x@generic, "(", sig_text, ")") if (identical(Sys.getenv("IN_PKGDOWN"), "true")) { url <- downlit::autolink_url(paste0("?", package, "::`", topic, "`")) } else { url <- NA } data.frame(package, topic, call, url, stringsAsFactors = FALSE) } item_list <- lapply(methods@.Data, s4_topic) items <- do.call(rbind, item_list) if (is.null(items) || ncol(items) == 0) { return("") } items <- items[order(items$call), ] if (identical(Sys.getenv("IN_PKGDOWN"), "true")) { linked <- ifelse(is.na(items$url), items$call, paste0("\\href{", items$url, "}{", items$call, "}")) item_text <- paste0("\\code{", linked, "}") } else { item_text <- paste0("\\code{\\link[=", items$topic, "]{", items$call, "}}") } paste0( "\\subsection{Methods in other packages}{\n\n", "This documentation page describes the generics. ", "Refer to the documentation pages linked below for the documentation for the methods that are implemented in various backend packages.", "\\itemize{\n", paste0("\\item ", item_text, "\n", collapse = ""), "}}\n" ) } DBI/R/dbGetQuery_DBIConnection_character.R0000644000176200001440000000062714350241735017772 0ustar liggesusers#' @rdname hidden_aliases #' @param n Number of rows to fetch, default -1 #' @usage NULL dbGetQuery_DBIConnection_character <- function(conn, statement, ..., n = -1L) { rs <- dbSendQuery(conn, statement, ...) on.exit(dbClearResult(rs)) dbFetch(rs, n = n, ...) } #' @rdname hidden_aliases #' @export setMethod("dbGetQuery", signature("DBIConnection", "character"), dbGetQuery_DBIConnection_character) DBI/R/dbConnect.R0000644000176200001440000000346014552712201013075 0ustar liggesusers#' Create a connection to a DBMS #' #' Connect to a DBMS going through the appropriate authentication procedure. #' Some implementations may allow you to have multiple connections open, so you #' may invoke this function repeatedly assigning its output to different #' objects. #' The authentication mechanism is left unspecified, so check the #' documentation of individual drivers for details. #' Use [dbCanConnect()] to check if a connection can be established. #' #' @template methods #' @templateVar method_name dbConnect #' #' @inherit DBItest::spec_driver_connect return #' @inheritSection DBItest::spec_driver_connect Specification #' #' @param drv an object that inherits from [DBIDriver-class], #' or an existing [DBIConnection-class] #' object (in order to clone an existing connection). #' @param ... authentication arguments needed by the DBMS instance; these #' typically include `user`, `password`, `host`, `port`, `dbname`, etc. #' For details see the appropriate `DBIDriver`. #' @seealso [dbDisconnect()] to disconnect from a database. #' @family DBIDriver generics #' @family DBIConnector generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' # SQLite only needs a path to the database. (Here, ":memory:" is a special #' # path that creates an in-memory database.) Other database drivers #' # will require more details (like user, password, host, port, etc.) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' con #' #' dbListTables(con) #' #' dbDisconnect(con) #' #' # Bad, for subtle reasons: #' # This code fails when RSQLite isn't loaded yet, #' # because dbConnect() doesn't know yet about RSQLite. #' dbListTables(con <- dbConnect(RSQLite::SQLite(), ":memory:")) setGeneric("dbConnect", def = function(drv, ...) standardGeneric("dbConnect"), valueClass = "DBIConnection" ) DBI/R/dbGetQueryArrow_DBIConnection.R0000644000176200001440000000054314552712156016772 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbGetQueryArrow_DBIConnection_character <- function(conn, statement, ...) { rs <- dbSendQueryArrow(conn, statement, ...) on.exit(dbClearResult(rs)) dbFetchArrow(rs, ...) } #' @rdname hidden_aliases #' @export setMethod("dbGetQueryArrow", signature("DBIConnection"), dbGetQueryArrow_DBIConnection_character) DBI/R/dbWriteTable_DBIConnection_Id_ANY.R0000644000176200001440000000047614350241735017400 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbWriteTable_DBIConnection_Id_ANY <- function(conn, name, value, ...) { dbWriteTable(conn, dbQuoteIdentifier(conn, name), value, ...) } #' @rdname hidden_aliases #' @export setMethod("dbWriteTable", signature("DBIConnection", "Id", "ANY"), dbWriteTable_DBIConnection_Id_ANY) DBI/R/data-types.R0000644000176200001440000000005514350241735013253 0ustar liggesuserssetOldClass("difftime") setOldClass("AsIs") DBI/R/dbQuoteString_DBIConnection.R0000644000176200001440000000215514350241735016473 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbQuoteString_DBIConnection <- function(conn, x, ...) { if (is(x, "SQL")) return(x) if (!is.character(x)) stop("x must be character or SQL", call. = FALSE) # Avoid fixed = TRUE due to https://github.com/r-dbi/DBItest/issues/156 x <- gsub("'", "''", enc2utf8(x)) if (length(x) == 0L) { SQL(character()) } else { # Not calling encodeString() here, see also https://stackoverflow.com/a/549244/946850 # and especially the comment by Álvaro González str <- paste("'", x, "'", sep = "") str[is.na(x)] <- "NULL" SQL(str) } } # Need to keep other method declarations around for now, because clients might # use getMethod(), see e.g. https://github.com/r-dbi/odbc/pull/149 #' @rdname hidden_aliases #' @export setMethod("dbQuoteString", signature("DBIConnection"), dbQuoteString_DBIConnection) #' @rdname hidden_aliases #' @export setMethod("dbQuoteString", signature("DBIConnection", "character"), dbQuoteString_DBIConnection) #' @rdname hidden_aliases #' @export setMethod("dbQuoteString", signature("DBIConnection", "SQL"), dbQuoteString_DBIConnection) DBI/R/dbFetch.R0000644000176200001440000000361514552712323012544 0ustar liggesusers#' Fetch records from a previously executed query #' #' Fetch the next `n` elements (rows) from the result set and return them #' as a data.frame. #' #' `fetch()` is provided for compatibility with older DBI clients - for all #' new code you are strongly encouraged to use `dbFetch()`. The default #' implementation for `dbFetch()` calls `fetch()` so that it is compatible with #' existing code. Modern backends should implement for `dbFetch()` only. #' #' @inheritSection dbBind The data retrieval flow #' #' @template methods #' @templateVar method_name dbFetch #' #' @inherit DBItest::spec_result_fetch return #' @inheritSection DBItest::spec_result_fetch Failure modes #' @inheritSection DBItest::spec_result_fetch Specification #' @inheritSection DBItest::spec_result_roundtrip Specification #' #' @param res An object inheriting from [DBIResult-class], created by #' [dbSendQuery()]. #' @param n maximum number of records to retrieve per fetch. Use `n = -1` #' or `n = Inf` #' to retrieve all pending records. Some implementations may recognize other #' special values. #' @param ... Other arguments passed on to methods. #' @seealso Close the result set with [dbClearResult()] as soon as you #' finish retrieving the records you want. #' @family DBIResult generics #' @family data retrieval generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' #' # Fetch all results #' rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4") #' dbFetch(rs) #' dbClearResult(rs) #' #' # Fetch in chunks #' rs <- dbSendQuery(con, "SELECT * FROM mtcars") #' while (!dbHasCompleted(rs)) { #' chunk <- dbFetch(rs, 10) #' print(nrow(chunk)) #' } #' #' dbClearResult(rs) #' dbDisconnect(con) setGeneric("dbFetch", def = function(res, n = -1, ...) standardGeneric("dbFetch"), valueClass = "data.frame" ) DBI/R/dbGetStatement.R0000644000176200001440000000143114552712201014104 0ustar liggesusers#' Get the statement associated with a result set #' #' Returns the statement that was passed to [dbSendQuery()] #' or [dbSendStatement()]. #' #' @template methods #' @templateVar method_name dbGetStatement #' #' @inherit DBItest::spec_meta_get_statement return #' @inheritSection DBItest::spec_meta_get_statement Failure modes #' #' @inheritParams dbClearResult #' @family DBIResult generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "mtcars", mtcars) #' rs <- dbSendQuery(con, "SELECT * FROM mtcars") #' dbGetStatement(rs) #' #' dbClearResult(rs) #' dbDisconnect(con) setGeneric("dbGetStatement", def = function(res, ...) standardGeneric("dbGetStatement"), valueClass = "character" ) DBI/R/02-DBIDriver.R0000644000176200001440000000273414552712156013203 0ustar liggesusersNULL #' DBIDriver class #' #' Base class for all DBMS drivers (e.g., RSQLite, MySQL, PostgreSQL). #' The virtual class `DBIDriver` defines the operations for creating #' connections and defining data type mappings. Actual driver classes, for #' instance `RPostgres`, `RMariaDB`, etc. implement these operations in a #' DBMS-specific manner. #' #' @docType class #' @name DBIDriver-class #' @family DBI classes #' @family DBIDriver generics #' @export setClass("DBIDriver", contains = c("DBIObject", "VIRTUAL")) show_driver <- function(object) { cat("<", is(object)[1], ">\n", sep = "") } findDriver <- function(drvName) { # If it exists in the global environment, use that d <- get2(drvName, globalenv()) if (!is.null(d)) return(d) # Otherwise, see if the appropriately named package is available if (is_attached(drvName)) { d <- get2(drvName, asNamespace(drvName)) if (!is.null(d)) return(d) } pkgName <- paste0("R", drvName) # First, see if package with name R + drvName is available if (is_attached(pkgName)) { d <- get2(drvName, asNamespace(pkgName)) if (!is.null(d)) return(d) } # Can't find it: stop( "Couldn't find driver ", drvName, ". Looked in:\n", "* global namespace\n", "* in package called ", drvName, "\n", "* in package called ", pkgName, call. = FALSE ) } get2 <- function(x, env) { if (!exists(x, envir = env)) return(NULL) get(x, envir = env) } is_attached <- function(x) { x %in% loadedNamespaces() } DBI/R/dbBindArrow_DBIResult.R0000644000176200001440000000065214552712323015255 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbBindArrow_DBIResult <- function(res, params, ...) { dbBind(res, params = param_stream_to_list(params), ...) } #' @rdname hidden_aliases #' @export setMethod("dbBindArrow", signature("DBIResult"), dbBindArrow_DBIResult) param_stream_to_list <- function(params) { params <- as.list(as.data.frame(params)) if (all(names(params) == "")) { names(params) <- NULL } params } DBI/R/dbClearResult.R0000644000176200001440000000215714552712323013740 0ustar liggesusers#' Clear a result set #' #' Frees all resources (local and remote) associated with a result set. #' This step is mandatory for all objects obtained by calling #' [dbSendQuery()] or [dbSendStatement()]. #' #' @inheritSection dbBind The data retrieval flow #' @inheritSection dbBind The command execution flow #' #' @template methods #' @templateVar method_name dbClearResult #' #' @inherit DBItest::spec_result_clear_result return #' @inheritSection DBItest::spec_result_clear_result Failure modes #' @inheritSection DBItest::spec_result_clear_result Specification #' #' @param res An object inheriting from [DBIResult-class]. #' @param ... Other arguments passed on to methods. #' @family DBIResult generics #' @family DBIResultArrow generics #' @family data retrieval generics #' @family command execution generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' rs <- dbSendQuery(con, "SELECT 1") #' print(dbFetch(rs)) #' #' dbClearResult(rs) #' dbDisconnect(con) setGeneric("dbClearResult", def = function(res, ...) standardGeneric("dbClearResult") ) DBI/R/dbCreateTable_DBIConnection.R0000644000176200001440000000105014350241735016353 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbCreateTable_DBIConnection <- function(conn, name, fields, ..., row.names = NULL, temporary = FALSE) { stopifnot(is.null(row.names)) stopifnot(is.logical(temporary), length(temporary) == 1L) query <- sqlCreateTable( con = conn, table = name, fields = fields, row.names = row.names, temporary = temporary, ... ) dbExecute(conn, query) invisible(TRUE) } #' @rdname hidden_aliases #' @export setMethod("dbCreateTable", signature("DBIConnection"), dbCreateTable_DBIConnection) DBI/R/sqlData_DBIConnection.R0000644000176200001440000000133314350241735015267 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL sqlData_DBIConnection <- function(con, value, row.names = NA, ...) { value <- sqlRownamesToColumn(value, row.names) # Convert factors to strings is_factor <- vapply(value, is.factor, logical(1)) value[is_factor] <- lapply(value[is_factor], as.character) # Quote all strings is_char <- vapply(value, is.character, logical(1)) value[is_char] <- lapply(value[is_char], function(x) { enc2utf8(dbQuoteString(con, x)) }) # Convert everything to character and turn NAs into NULL value[!is_char] <- lapply(value[!is_char], dbQuoteLiteral, conn = con) value } #' @rdname hidden_aliases #' @export setMethod("sqlData", signature("DBIConnection"), sqlData_DBIConnection) DBI/R/dbQuoteString.R0000644000176200001440000000225414350241735013775 0ustar liggesusers#' Quote literal strings #' #' Call this method to generate a string that is suitable for #' use in a query as a string literal, to make sure that you #' generate valid SQL and protect against SQL injection attacks. #' #' @inheritParams dbGetQuery #' @param x A character vector to quote as string. #' @param ... Other arguments passed on to methods. #' #' @template methods #' @templateVar method_name dbQuoteString #' #' @inherit DBItest::spec_sql_quote_string return #' @inheritSection DBItest::spec_sql_quote_string Failure modes #' @inheritSection DBItest::spec_sql_quote_string Specification #' #' @family DBIResult generics #' @export #' @examples #' # Quoting ensures that arbitrary input is safe for use in a query #' name <- "Robert'); DROP TABLE Students;--" #' dbQuoteString(ANSI(), name) #' #' # NAs become NULL #' dbQuoteString(ANSI(), c("x", NA)) #' #' # SQL vectors are always passed through as is #' var_name <- SQL("select") #' var_name #' dbQuoteString(ANSI(), var_name) #' #' # This mechanism is used to prevent double escaping #' dbQuoteString(ANSI(), dbQuoteString(ANSI(), name)) setGeneric("dbQuoteString", def = function(conn, x, ...) standardGeneric("dbQuoteString") ) DBI/R/dbCreateTableArrow_DBIConnection.R0000644000176200001440000000106014552712323017367 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbCreateTableArrow_DBIConnection <- function(conn, name, value, ..., temporary = FALSE) { require_arrow() # https://github.com/apache/arrow-nanoarrow/issues/347 if (!inherits(value, "nanoarrow_schema")) { value <- nanoarrow::infer_nanoarrow_schema(value) } ptype <- nanoarrow::infer_nanoarrow_ptype(value) dbCreateTable(conn, name, ptype, ..., temporary = temporary) } #' @rdname hidden_aliases #' @export setMethod("dbCreateTableArrow", signature("DBIConnection"), dbCreateTableArrow_DBIConnection) DBI/R/dbIsValid.R0000644000176200001440000000152114552712323013040 0ustar liggesusers#' Is this DBMS object still valid? #' #' This generic tests whether a database object is still valid (i.e. it hasn't #' been disconnected or cleared). #' #' @template methods #' @templateVar method_name dbIsValid #' #' @inherit DBItest::spec_meta_is_valid return #' #' @inheritParams dbGetInfo #' @family DBIDriver generics #' @family DBIConnection generics #' @family DBIResult generics #' @family DBIResultArrow generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' dbIsValid(RSQLite::SQLite()) #' #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' dbIsValid(con) #' #' rs <- dbSendQuery(con, "SELECT 1") #' dbIsValid(rs) #' #' dbClearResult(rs) #' dbIsValid(rs) #' #' dbDisconnect(con) #' dbIsValid(con) setGeneric("dbIsValid", def = function(dbObj, ...) standardGeneric("dbIsValid"), valueClass = "logical" ) DBI/R/dbRemoveTable_DBIConnection_Id.R0000644000176200001440000000044514350241735017030 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbRemoveTable_DBIConnection_Id <- function(conn, name, ...) { dbRemoveTable(conn, dbQuoteIdentifier(conn, name), ...) } #' @rdname hidden_aliases #' @export setMethod("dbRemoveTable", signature("DBIConnection", "Id"), dbRemoveTable_DBIConnection_Id) DBI/R/dbListObjects.R0000644000176200001440000000271214552712201013730 0ustar liggesusers#' List remote objects #' #' Returns the names of remote objects accessible through this connection #' as a data frame. #' This should include temporary objects, but not all database backends #' (in particular \pkg{RMariaDB} and \pkg{RMySQL}) support this. #' Compared to [dbListTables()], this method also enumerates tables and views #' in schemas, and returns fully qualified identifiers to access these objects. #' This allows exploration of all database objects available to the current #' user, including those that can only be accessed by giving the full #' namespace. #' #' @template methods #' @templateVar method_name dbListObjects #' #' @inherit DBItest::spec_sql_list_objects return #' @inheritSection DBItest::spec_sql_list_objects Failure modes #' @inheritSection DBItest::spec_sql_list_objects Specification #' #' @inheritParams dbGetQuery #' @param prefix A fully qualified path in the database's namespace, or `NULL`. #' This argument will be processed with [dbUnquoteIdentifier()]. #' If given the method will return all objects accessible through this prefix. #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbListObjects(con) #' dbWriteTable(con, "mtcars", mtcars) #' dbListObjects(con) #' #' dbDisconnect(con) setGeneric("dbListObjects", def = function(conn, prefix = NULL, ...) standardGeneric("dbListObjects"), valueClass = "data.frame" ) DBI/R/06-ANSI.R0000644000176200001440000000067214552712156012166 0ustar liggesuserssetClass("AnsiConnection", contains = "DBIConnection") #' A dummy DBI connector that simulates ANSI-SQL compliance #' #' @export #' @keywords internal #' @examples #' ANSI() ANSI <- function() { new("AnsiConnection") } #' Internal page for hidden aliases #' #' For S4 methods that require a documentation entry but only clutter the index. #' #' @usage NULL #' @format NULL #' @keywords internal #' @docType methods hidden_aliases <- NULL DBI/R/dbiDataType_logical.R0000644000176200001440000000020214350241735015056 0ustar liggesusers#' @usage NULL dbiDataType_logical <- function(x) "SMALLINT" setMethod("dbiDataType", signature("logical"), dbiDataType_logical) DBI/R/dbExecute_DBIConnection_character.R0000644000176200001440000000053414350241735017624 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbExecute_DBIConnection_character <- function(conn, statement, ...) { rs <- dbSendStatement(conn, statement, ...) on.exit(dbClearResult(rs)) dbGetRowsAffected(rs) } #' @rdname hidden_aliases #' @export setMethod("dbExecute", signature("DBIConnection", "character"), dbExecute_DBIConnection_character) DBI/R/dbBegin.R0000644000176200001440000000016214350241735012531 0ustar liggesusers#' @export #' @rdname transactions setGeneric("dbBegin", def = function(conn, ...) standardGeneric("dbBegin") ) DBI/R/dbCallProc.R0000644000176200001440000000076014350241735013210 0ustar liggesusers#' Call an SQL stored procedure #' #' **Deprecated since 2014** #' #' The recommended way of calling a stored procedure is now #' #' \enumerate{ #' \item{\code{\link{dbGetQuery}} if a result set is returned} #' \item{\code{\link{dbExecute}} for data manipulation and other cases where no result set is returned} #' } #' #' @inheritParams dbGetQuery #' @keywords internal #' @export setGeneric("dbCallProc", def = function(conn, ...) { .Deprecated() standardGeneric("dbCallProc") } ) DBI/R/dbiDataType_integer.R0000644000176200001440000000017514350241735015112 0ustar liggesusers#' @usage NULL dbiDataType_integer <- function(x) "INT" setMethod("dbiDataType", signature("integer"), dbiDataType_integer) DBI/R/dbBindArrow_DBIResultArrowDefault.R0000644000176200001440000000050414552712323017571 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbBindArrow_DBIResultArrowDefault <- function(res, params, ...) { dbBind(res@result, params = param_stream_to_list(params), ...) invisible(res) } #' @rdname hidden_aliases #' @export setMethod("dbBindArrow", signature("DBIResultArrowDefault"), dbBindArrow_DBIResultArrowDefault) DBI/R/23-dbWriteTableArrow.R0000644000176200001440000000317314552712323015011 0ustar liggesusers#' Copy Arrow objects to database tables #' #' @description #' `r lifecycle::badge('experimental')` #' #' Writes, overwrites or appends an Arrow object to a database table. #' #' @details #' This function expects an Arrow object. #' Convert a data frame to an Arrow object with [nanoarrow::as_nanoarrow_array_stream()] or #' use [dbWriteTable()] to write a data frame. #' #' This function is useful if you want to create and load a table at the same time. #' Use [dbAppendTableArrow()] for appending data to an existing #' table, [dbCreateTableArrow()] for creating a table and specifying field types, #' and [dbRemoveTable()] for overwriting tables. #' #' @template methods #' @templateVar method_name dbWriteTableArrow #' #' @inherit DBItest::spec_arrow_write_table_arrow return #' @inheritSection DBItest::spec_arrow_write_table_arrow Failure modes #' @inheritSection DBItest::spec_arrow_write_table_arrow Additional arguments #' @inheritSection DBItest::spec_arrow_write_table_arrow Specification #' #' @inheritParams dbGetQuery #' @inheritParams dbReadTable #' @param value An nanoarray stream, or an object coercible to a nanoarray stream with #' [nanoarrow::as_nanoarrow_array_stream()]. #' @family DBIConnection generics #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) && requireNamespace("nanoarrow", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTableArrow(con, "mtcars", nanoarrow::as_nanoarrow_array_stream(mtcars[1:5, ])) #' dbReadTable(con, "mtcars") #' #' dbDisconnect(con) setGeneric("dbWriteTableArrow", def = function(conn, name, value, ...) standardGeneric("dbWriteTableArrow") ) DBI/R/dbGetStatement_DBIResultArrow.R0000644000176200001440000000040014552712156017000 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbGetStatement_DBIResultArrow <- function(res, ...) { dbGetStatement(res@result, ...) } #' @rdname hidden_aliases #' @export setMethod("dbGetStatement", signature("DBIResultArrow"), dbGetStatement_DBIResultArrow) DBI/R/dbExecute.R0000644000176200001440000000426014552712323013112 0ustar liggesusers#' Change database state #' #' Executes a statement and returns the number of rows affected. #' `dbExecute()` comes with a default implementation #' (which should work with most backends) that calls #' [dbSendStatement()], then [dbGetRowsAffected()], ensuring that #' the result is always freed by [dbClearResult()]. #' For passing query parameters, see [dbBind()], in particular #' the "The command execution flow" section. #' #' You can also use `dbExecute()` to call a stored procedure #' that performs data manipulation or other actions that do not return a result set. #' To execute a stored procedure that returns a result set, #' or a data manipulation query that also returns a result set #' such as `INSERT INTO ... RETURNING ...`, use [dbGetQuery()] instead. #' #' @template methods #' @templateVar method_name dbExecute #' #' @section Implementation notes: #' Subclasses should override this method only if they provide some sort of #' performance optimization. #' #' @inherit DBItest::spec_result_execute return #' @inheritSection DBItest::spec_result_execute Failure modes #' @inheritSection DBItest::spec_result_execute Additional arguments #' @inheritSection DBItest::spec_result_execute Specification #' @inheritSection DBItest::spec_result_execute Specification for the `immediate` argument #' #' @inheritParams dbGetQuery #' @param statement a character string containing SQL. #' @family DBIConnection generics #' @family command execution generics #' @seealso For queries: [dbSendQuery()] and [dbGetQuery()]. #' @export #' @examplesIf requireNamespace("RSQLite", quietly = TRUE) #' con <- dbConnect(RSQLite::SQLite(), ":memory:") #' #' dbWriteTable(con, "cars", head(cars, 3)) #' dbReadTable(con, "cars") # there are 3 rows #' dbExecute( #' con, #' "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" #' ) #' dbReadTable(con, "cars") # there are now 6 rows #' #' # Pass values using the param argument: #' dbExecute( #' con, #' "INSERT INTO cars (speed, dist) VALUES (?, ?)", #' params = list(4:7, 5:8) #' ) #' dbReadTable(con, "cars") # there are now 10 rows #' #' dbDisconnect(con) setGeneric("dbExecute", def = function(conn, statement, ...) standardGeneric("dbExecute") ) DBI/R/dbQuoteLiteral_DBIConnection.R0000644000176200001440000000251014350241735016614 0ustar liggesusers#' @rdname hidden_aliases #' @usage NULL dbQuoteLiteral_DBIConnection <- function(conn, x, ...) { # Switchpatching to avoid ambiguous S4 dispatch, so that our method # is used only if no alternatives are available. if (is(x, "SQL")) { return(x) } if (is.factor(x)) { return(dbQuoteString(conn, as.character(x))) } if (is.character(x)) { return(dbQuoteString(conn, x)) } if (inherits(x, "POSIXt")) { return(dbQuoteString( conn, strftime(as.POSIXct(x), "%Y%m%d%H%M%S", tz = "UTC") )) } if (inherits(x, "Date")) { return(dbQuoteString(conn, as.character(x))) } if (inherits(x, "difftime")) { return(dbQuoteString(conn, format_hms(x))) } if (is.list(x)) { blob_data <- vapply( x, function(x) { if (is.null(x)) { "NULL" } else if (is.raw(x)) { paste0("X'", paste(format(x), collapse = ""), "'") } else { stop("Lists must contain raw vectors or NULL", call. = FALSE) } }, character(1) ) return(SQL(blob_data, names = names(x))) } if (is.logical(x)) { x <- as.numeric(x) } x <- as.character(x) x[is.na(x)] <- "NULL" SQL(x, names = names(x)) } #' @rdname hidden_aliases #' @export setMethod("dbQuoteLiteral", signature("DBIConnection"), dbQuoteLiteral_DBIConnection) DBI/R/dbRollback.R0000644000176200001440000000017014350241735013235 0ustar liggesusers#' @export #' @rdname transactions setGeneric("dbRollback", def = function(conn, ...) standardGeneric("dbRollback") ) DBI/R/dbIsReadOnly.R0000644000176200001440000000075014350241735013521 0ustar liggesusers#' Is this DBMS object read only? #' #' This generic tests whether a database object is read only. #' #' @inheritParams dbGetInfo #' #' @template methods #' @templateVar method_name dbIsReadOnly #' #' @family DBIDriver generics #' @family DBIConnection generics #' @family DBIResult generics #' @family DBIConnector generics #' @export #' @examples #' dbIsReadOnly(ANSI()) setGeneric("dbIsReadOnly", def = function(dbObj, ...) standardGeneric("dbIsReadOnly"), valueClass = "logical") DBI/R/dbCommit.R0000644000176200001440000000016414350241735012737 0ustar liggesusers#' @export #' @rdname transactions setGeneric("dbCommit", def = function(conn, ...) standardGeneric("dbCommit") ) DBI/R/SQL.R0000644000176200001440000000403614350241735011642 0ustar liggesusers#' SQL quoting #' #' This set of classes and generics make it possible to flexibly deal with SQL #' escaping needs. By default, any user supplied input to a query should be #' escaped using either [dbQuoteIdentifier()] or [dbQuoteString()] #' depending on whether it refers to a table or variable name, or is a literal #' string. #' These functions may return an object of the `SQL` class, #' which tells DBI functions that a character string does not need to be escaped #' anymore, to prevent double escaping. #' The `SQL` class has associated the `SQL()` constructor function. #' #' @section Implementation notes: #' #' DBI provides default generics for SQL-92 compatible quoting. If the database #' uses a different convention, you will need to provide your own methods. #' Note that because of the way that S4 dispatch finds methods and because #' SQL inherits from character, if you implement (e.g.) a method for #' `dbQuoteString(MyConnection, character)`, you will also need to #' implement `dbQuoteString(MyConnection, SQL)` - this should simply #' return `x` unchanged. #' #' @param x A character vector to label as being escaped SQL. #' @param ... Other arguments passed on to methods. Not otherwise used. #' @param names Names for the returned object, must have the same length as `x`. #' @return An object of class `SQL`. #' @export #' @examples #' dbQuoteIdentifier(ANSI(), "SELECT") #' dbQuoteString(ANSI(), "SELECT") #' #' # SQL vectors are always passed through as is #' var_name <- SQL("SELECT") #' var_name #' #' dbQuoteIdentifier(ANSI(), var_name) #' dbQuoteString(ANSI(), var_name) #' #' # This mechanism is used to prevent double escaping #' dbQuoteString(ANSI(), dbQuoteString(ANSI(), "SELECT")) SQL <- function(x, ..., names = NULL) { if (!is.null(names)) { stopifnot(length(x) == length(names)) } names(x) <- names new("SQL", x) } #' @rdname SQL #' @export #' @aliases #' SQL-class setClass("SQL", contains = "character") #' @export `[.SQL` <- function(x, ...) SQL(NextMethod()) #' @export `[[.SQL` <- function(x, ...) SQL(NextMethod()) DBI/NEWS.md0000644000176200001440000005035714561351766011776 0ustar liggesusers # DBI 1.2.2 (2024-02-09) ## Bug fixes - `Id()` does not assign empty names to the components if all arguments are unnamed (#464). - Add spec to version control to avoid weird pandoc errors on CRAN (#465). # DBI 1.2.1 (2024-01-12) ## Bug fixes - Fix `dbWriteTableArrow()` according to spec (#457). - Fix type inference in default method for `dbCreateTableArrow()` (#450). ## Features - `dbAppendTableArrow()` returns number of rows (#454). - Add `temporary` argument to `dbCreateTableArrow()` (#453). - Avoid coercing `params` in default implementation for `dbSendQueryArrow()` (#447). - Use `nanoarrow::infer_nanoarrow_schema()` in the default method for `dbCreateTable()` (#445). ## Chore - Add badge to `DBIResultArrow` class (#452). - Change maintainer e-mail. ## Documentation - Finalize Arrow vignette (#451, #455). - Document new Arrow generics (#444, #449). - Use dbitemplate (@maelle, #442). # DBI 1.2.0 (2023-12-20) ## Breaking changes - `dbUnquoteIdentifier()` creates `Id()` objects without component names and allows non-`NA` character input (#421, #422). ## Features - New generics `dbSendQueryArrow()`, `dbFetchArrow()`, `dbGetQueryArrow()`, `dbReadTableArrow()`, `dbWriteTableArrow()` (@nbenn, #390), `dbCreateTableArrow()`, `dbAppendTableArrow()` (#396), `dbBindArrow()` (#415) and `dbFetchArrowChunk()` (#424), with default implementations via nanoarrow (#414). - `Id()` now accepts unnamed components (#417). If names are provided, the components are arranged in SQL order (@eauleaf, #427). - New `dbIsValid()` method for `"DBIResultArrowDefault"` objects implemented by DBI (#425). - Implement `dbiDataType()` for objects of class `"blob"`. ## Documentation - Update pkgdown template (@maelle, #428, #438, #437). - Clarify repeated parameter binding (#430). - Deal with sundown of `https://relational.fit.cvut.cz` (#423). - Correct vignette titles (#419). - Harmonize table documentation (#400). - Tweak typo, add families for data retrieval and command execution. ## Testing - Enable BLOB tests for arrow \>= 10.0.0 (#395). - Run DBItest for SQLite as part of the checks here (#431). - Fix checks without suggested packages (#420). - Fix Windows tests on GHA (#406). - `testthat::use_testthat(3)` (#416). # DBI 1.1.3 (2022-06-18) ## Features - `dbAppendTable()` accepts `Id` (#381, @renkun-ken). ## Documentation - `?dbSendQuery` and related methods gain a section "The data retrieval flow" (#386). - `?dbSendStatement` and related methods gain a section "The command execution flow" (#386). # DBI 1.1.2 (2021-12-19) ## Features - Use `dbQuoteLiteral()` in default method for `sqlData()` (#362, #371). - Update specification with changes from DBItest 1.7.2 (#367). ## Documentation - The pkgdown documentation for DBI generics (e.g. `?dbConnect`) contains clickable links to all known backends (except ROracle), and an explanatory sentence (#360). - `?Id` gains better examples (#295, #370). - Elaborate on status of `dbWriteTable()` in the documentation (#352, #372). - Make method definition more similar to S3. All `setMethod()` calls refer to top-level functions (#368). - `?dbReadTable` and other pages gain pointers to `Id()` and `SQL()` (#359). # DBI 1.1.1 (2021-01-04) ## Documentation - Expand "Get started" vignette to two tutorials, basic and advanced (#332, @jawond). ## Bug fixes - `dbAppendTable()` now allows columns named `sep` (#336). - `dbAppendTable()` shows a better error message if the input has zero columns (#313). - `sqlInterpolate()` now correctly interprets consecutive comments (#329, @rnorberg). - `dbQuoteLiteral()` works for difftime objects (#325). - `dbQuoteLiteral()` quotes dates as `YYYY-MM-DD` without time zone (#331). ## Internal - Switch to GitHub Actions (#326). - Update URL in `DESCRIPTION`. # DBI 1.1.0 (2019-12-15) ## New features - New `DBIConnector` class (#280). - Specify `immediate` argument to `dbSendQuery()`, `dbGetQuery()`, `dbSendStatement()` and `dbExecute()` (#268). - Use specification for `dbGetInfo()` (#271). - `dbUnquoteIdentifier()` now supports `Id()` objects with `catalog` members (#266, @raffscallion). It also handles unquoted identifiers of the form `table`, `schema.table` or `catalog.schema.table`, for compatibility with dbplyr. ## Documentation - New DBI intro article (#286, @cutterkom). - Add pkgdown reference index (#288). - DBI specification on https://dbi.r-dbi.org/dev/articles/spec now comes with a table of contents and code formatting. - Update examples to refer to `params` instead of `param` (#235). - Improved documentation for `sqlInterpolate()` (#100). Add usage of `SQL()` to `sqlInterpolate()` examples (#259, @renkun-ken). - Improve documentation for `Id`. ## Internal - Add tests for `dbUnquoteIdentifier()` (#279, @baileych). - `sqlInterpolate()` uses `dbQuoteLiteral()` instead of checking the type of the input. - Avoid partial argument match in `dbWriteTable()` (#246, @richfitz). # DBI 1.0.0 (2018-05-02) ## New generics - New `dbAppendTable()` that by default calls `sqlAppendTableTemplate()` and then `dbExecute()` with a `param` argument, without support for `row.names` argument (#74). - New `dbCreateTable()` that by default calls `sqlCreateTable()` and then `dbExecute()`, without support for `row.names` argument (#74). - New `dbCanConnect()` generic with default implementation (#87). - New `dbIsReadOnly()` generic with default implementation (#190, @anhqle). ## Changes - `sqlAppendTable()` now accepts lists for the `values` argument, to support lists of `SQL` objects in R 3.1. - Add default implementation for `dbListFields(DBIConnection, Id)`, this relies on `dbQuoteIdentifier(DBIConnection, Id)` (#75). ## Documentation updates - The DBI specification vignette is rendered correctly from the installed package (#234). - Update docs on how to cope with stored procedures (#242, @aryoda). - Add "Additional arguments" sections and more examples for `dbGetQuery()`, `dbSendQuery()`, `dbExecute()` and `dbSendStatement()`. - The `dbColumnInfo()` method is now fully specified (#75). - The `dbListFields()` method is now fully specified (#75). - The dynamic list of methods in help pages doesn't contain methods in DBI anymore. ## Bug fixes - Pass missing `value` argument to secondary `dbWriteTable()` call (#737, @jimhester). - The `Id` class now uses `` and not `` when printing. - The default `dbUnquoteIdentifier()` implementation now complies to the spec. # DBI 0.8 (2018-02-24) Breaking changes ---------------- - `SQL()` now strips the names from the output if the `names` argument is unset. - The `dbReadTable()`, `dbWriteTable()`, `dbExistsTable()`, `dbRemoveTable()`, and `dbListFields()` generics now specialize over the first two arguments to support implementations with the `Id` S4 class as type for the second argument. Some packages may need to update their documentation to satisfy R CMD check again. New generics ------------ - Schema support: Export `Id()`, new generics `dbListObjects()` and `dbUnquoteIdentifier()`, methods for `Id` that call `dbQuoteIdentifier()` and then forward (#220). - New `dbQuoteLiteral()` generic. The default implementation uses switchpatch to avoid dispatch ambiguities, and forwards to `dbQuoteString()` for character vectors. Backends may override methods that also dispatch on the second argument, but in this case also an override for the `"SQL"` class is necessary (#172). Default implementations ----------------------- - Default implementations of `dbQuoteIdentifier()` and `dbQuoteLiteral()` preserve names, default implementation of `dbQuoteString()` strips names (#173). - Specialized methods for `dbQuoteString()` and `dbQuoteIdentifier()` are available again, for compatibility with clients that use `getMethod()` to access them (#218). - Add default implementation of `dbListFields()`. - The default implementation of `dbReadTable()` now has `row.names = FALSE` as default and also supports `row.names = NULL` (#186). API changes ----------- - The `SQL()` function gains an optional `names` argument which can be used to assign names to SQL strings. Deprecated generics ------------------- - `dbListConnections()` is soft-deprecated by documentation. - `dbListResults()` is deprecated by documentation (#58). - `dbGetException()` is soft-deprecated by documentation (#51). - The deprecated `print.list.pairs()` has been removed. Bug fixes --------- - Fix `dbDataType()` for `AsIs` object (#198, @yutannihilation). - Fix `dbQuoteString()` and `dbQuoteIdentifier()` to ignore invalid UTF-8 strings (r-dbi/DBItest#156). Documentation ------------- - Help pages for generics now contain a dynamic list of methods implemented by DBI backends (#162). - `sqlInterpolate()` now supports both named and positional variables (#216, @hannesmuehleisen). - Point to db.rstudio.com (@wibeasley, #209). - Reflect new 'r-dbi' organization in `DESCRIPTION` (@wibeasley, #207). Internal -------- - Using switchpatch on the second argument for default implementations of `dbQuoteString()` and `dbQuoteIdentifier()`. # DBI 0.7 (2017-06-17) - Import updated specs from `DBItest`. - The default implementation of `dbGetQuery()` now accepts an `n` argument and forwards it to `dbFetch()`. No warning about pending rows is issued anymore (#76). - Require R >= 3.0.0 (for `slots` argument of `setClass()`) (#169, @mvkorpel). # DBI 0.6-1 (2017-04-01) - Fix `dbReadTable()` for backends that do not provide their own implementation (#171). # DBI 0.6 (2017-03-08) - Interface changes - Deprecated `dbDriver()` and `dbUnloadDriver()` by documentation (#21). - Renamed arguments to `sqlInterpolate()` and `sqlParseVariables()` to be more consistent with the rest of the interface, and added `.dots` argument to `sqlParseVariables`. DBI drivers are now expected to implement `sqlParseVariables(conn, sql, ..., .dots)` and `sqlInterpolate(conn, sql, ...)` (#147). - Interface enhancements - Removed `valueClass = "logical"` for those generics where the return value is meaningless, to allow backends to return invisibly (#135). - Avoiding using braces in the definitions of generics if possible, so that standard generics can be detected (#146). - Added default implementation for `dbReadTable()`. - All standard generics are required to have an ellipsis (with test), for future extensibility. - Improved default implementation of `dbQuoteString()` and `dbQuoteIdentifier()` (#77). - Removed `tryCatch()` call in `dbGetQuery()` (#113). - Documentation improvements - Finalized first draft of DBI specification, now in a vignette. - Most methods now draw documentation from `DBItest`, only those where the behavior is not finally decided don't do this yet yet. - Removed `max.connections` requirement from documentation (#56). - Improved `dbBind()` documentation and example (#136). - Change `omegahat.org` URL to `omegahat.net`, the particular document still doesn't exist below the new domain. - Internal - Use roxygen2 inheritance to copy DBI specification to this package. - Use `tic` package for building documentation. - Use markdown in documentation. # DBI 0.5-1 (2016-09-09) - Documentation and example updates. # DBI 0.5 (2016-08-11, CRAN release) - Interface changes - `dbDataType()` maps `character` values to `"TEXT"` by default (#102). - The default implementation of `dbQuoteString()` doesn't call `encodeString()` anymore: Neither SQLite nor Postgres understand e.g. `\n` in a string literal, and all of SQLite, Postgres, and MySQL accept an embedded newline (#121). - Interface enhancements - New `dbSendStatement()` generic, forwards to `dbSendQuery()` by default (#20, #132). - New `dbExecute()`, calls `dbSendStatement()` by default (#109, @bborgesr). - New `dbWithTransaction()` that calls `dbBegin()` and `dbCommit()`, and `dbRollback()` on failure (#110, @bborgesr). - New `dbBreak()` function which allows aborting from within `dbWithTransaction()` (#115, #133). - Export `dbFetch()` and `dbQuoteString()` methods. - Documentation improvements: - One example per function (except functions scheduled for deprecation) (#67). - Consistent layout and identifier naming. - Better documentation of generics by adding links to the class and related generics in the "See also" section under "Other DBI... generics" (#130). S4 documentation is directed to a hidden page to unclutter documentation index (#59). - Fix two minor vignette typos (#124, @mdsumner). - Add package documentation. - Remove misleading parts in `dbConnect()` documentation (#118). - Remove misleading link in `dbDataType()` documentation. - Remove full stop from documentation titles. - New help topic "DBIspec" that contains the full DBI specification (currently work in progress) (#129). - HTML documentation generated by `staticdocs` is now uploaded to https://rstats-db.github.io/DBI for each build of the "production" branch (#131). - Further minor changes and fixes. - Internal - Use `contains` argument instead of `representation()` to denote base classes (#93). - Remove redundant declaration of transaction methods (#110, @bborgesr). # DBI 0.4-1 (2016-05-07, CRAN release) - The default `show()` implementations silently ignore all errors. Some DBI drivers (e.g., RPostgreSQL) might fail to implement `dbIsValid()` or the other methods used. # DBI 0.4 (2016-04-30) * New package maintainer: Kirill Müller. * `dbGetInfo()` gains a default method that extracts the information from `dbGetStatement()`, `dbGetRowsAffected()`, `dbHasCompleted()`, and `dbGetRowCount()`. This means that most drivers should no longer need to implement `dbGetInfo()` (which may be deprecated anyway at some point) (#55). * `dbDataType()` and `dbQuoteString()` are now properly exported. * The default implementation for `dbDataType()` (powered by `dbiDataType()`) now also supports `difftime` and `AsIs` objects and lists of `raw` (#70). * Default `dbGetQuery()` method now always calls `dbFetch()`, in a `tryCatch()` block. * New generic `dbBind()` for binding values to a parameterised query. * DBI gains a number of SQL generation functions. These make it easier to write backends by implementing common operations that are slightly tricky to do absolutely correctly. * `sqlCreateTable()` and `sqlAppendTable()` create tables from a data frame and insert rows into an existing table. These will power most implementations of `dbWriteTable()`. `sqlAppendTable()` is useful for databases that support parameterised queries. * `sqlRownamesToColumn()` and `sqlColumnToRownames()` provide a standard way of translating row names to and from the database. * `sqlInterpolate()` and `sqlParseVariables()` allows databases without native parameterised queries to use parameterised queries to avoid SQL injection attacks. * `sqlData()` is a new generic that converts a data frame into a data frame suitable for sending to the database. This is used to (e.g.) ensure all character vectors are encoded as UTF-8, or to convert R varible types (like factor) to types supported by the database. * The `sqlParseVariablesImpl()` is now implemented purely in R, with full test coverage (#83, @hannesmuehleisen). * `dbiCheckCompliance()` has been removed, the functionality is now available in the `DBItest` package (#80). * Added default `show()` methods for driver, connection and results. * New concrete `ANSIConnection` class and `ANSI()` function to generate a dummy ANSI compliant connection useful for testing. * Default `dbQuoteString()` and `dbQuoteIdentifer()` methods now use `encodeString()` so that special characters like `\n` are correctly escaped. `dbQuoteString()` converts `NA` to (unquoted) NULL. * The initial DBI proposal and DBI version 1 specification are now included as a vignette. These are there mostly for historical interest. * The new `DBItest` package is described in the vignette. * Deprecated `print.list.pairs()`. * Removed unused `dbi_dep()`. # Version 0.3.1 * Actually export `dbIsValid()` :/ * `dbGetQuery()` uses `dbFetch()` in the default implementation. # Version 0.3.0 ## New and enhanced generics * `dbIsValid()` returns a logical value describing whether a connection or result set (or other object) is still valid. (#12). * `dbQuoteString()` and `dbQuoteIdentifier()` to implement database specific quoting mechanisms. * `dbFetch()` added as alias to `fetch()` to provide consistent name. Implementers should define methods for both `fetch()` and `dbFetch()` until `fetch()` is deprecated in 2015. For now, the default method for `dbFetch()` calls `fetch()`. * `dbBegin()` begins a transaction (#17). If not supported, DB specific methods should throw an error (as should `dbCommit()` and `dbRollback()`). ## New default methods * `dbGetStatement()`, `dbGetRowsAffected()`, `dbHasCompleted()`, and `dbGetRowCount()` gain default methods that extract the appropriate elements from `dbGetInfo()`. This means that most drivers should no longer need to implement these methods (#13). * `dbGetQuery()` gains a default method for `DBIConnection` which uses `dbSendQuery()`, `fetch()` and `dbClearResult()`. ## Deprecated features * The following functions are soft-deprecated. They are going away, and developers who use the DBI should begin preparing. The formal deprecation process will begin in July 2015, where these function will emit warnings on use. * `fetch()` is replaced by `dbFetch()`. * `make.db.names()`, `isSQLKeyword()` and `SQLKeywords()`: a black list based approach is fundamentally flawed; instead quote strings and identifiers with `dbQuoteIdentifier()` and `dbQuoteString()`. * `dbGetDBIVersion()` is deprecated since it's now just a thin wrapper around `packageVersion("DBI")`. * `dbSetDataMappings()` (#9) and `dbCallProc()` (#7) are deprecated as no implementations were ever provided. ## Other improvements * `dbiCheckCompliance()` makes it easier for implementors to check that their package is in compliance with the DBI specification. * All examples now use the RSQLite package so that you can easily try out the code samples (#4). * `dbDriver()` gains a more effective search mechanism that doesn't rely on packages being loaded (#1). * DBI has been converted to use roxygen2 for documentation, and now most functions have their own documentation files. I would love your feedback on how we could make the documentation better! # Version 0.2-7 * Trivial changes (updated package fields, daj) # Version 0.2-6 * Removed deprecated \synopsis in some Rd files (thanks to Prof. Ripley) # Version 0.2-5 * Code cleanups contributed by Matthias Burger: avoid partial argument name matching and use TRUE/FALSE, not T/F. * Change behavior of make.db.names.default to quote SQL keywords if allow.keywords is FALSE. Previously, SQL keywords would be name mangled with underscores and a digit. Now they are quoted using '"'. # Version 0.2-4 * Changed license from GPL to LPGL * Fixed a trivial typo in documentation # Version 0.1-10 * Fixed documentation typos. # Version 0.1-9 * Trivial changes. # Version 0.1-8 * A trivial change due to package.description() being deprecated in 1.9.0. # Version 0.1-7 * Had to do a substantial re-formatting of the documentation due to incompatibilities introduced in 1.8.0 S4 method documentation. The contents were not changed (modulo fixing a few typos). Thanks to Kurt Hornik and John Chambers for their help. # Version 0.1-6 * Trivial documentation changes (for R CMD check's sake) # Version 0.1-5 * Removed duplicated setGeneric("dbSetDataMappings") # Version 0.1-4 * Removed the "valueClass" from some generic functions, namely, dbListConnections, dbListResults, dbGetException, dbGetQuery, and dbGetInfo. The reason is that methods for these generics could potentially return different classes of objects (e.g., the call dbGetInfo(res) could return a list of name-value pairs, while dbGetInfo(res, "statement") could be a character vector). * Added 00Index to inst/doc * Added dbGetDBIVersion() (simple wrapper to package.description). # Version 0.1-3 * ??? Minor changes? # Version 0.1-2 * An implementation based on version 4 classes and methods. * Incorporated (mostly Tim Keitt's) comments. DBI/MD50000644000176200001440000004051314563656122011175 0ustar liggesusersd8e0787a54d7583166b244c8c5c4b9ec *DESCRIPTION 261c3e3ddc96347b5a8e3f19c299cc5d *NAMESPACE 27c741e92d04312e40615a0c7a340572 *NEWS.md c2218355e09634686d8efa8d6be3ed40 *R/00-Id.R df6668faefa1a555a8f9e95afeb70904 *R/01-DBIObject.R 7a3a1ecc4caadf1711bcfba9986958b1 *R/02-DBIDriver.R 1f7c9b1b7a417f97cdef15d809630ce0 *R/03-DBIConnection.R b56706702384fe74719397d7d086f585 *R/04-DBIResult.R 3ac82a661c763fbfae79e7333bd33d18 *R/06-ANSI.R 09cbb7db46c57202c3da61e0d5884d49 *R/07-DBIResultArrow.R 4fc9f615f5906a28c7d6066310f8996a *R/11-dbAppendTable.R 961227f4bbdf9bfde456d892fdd2a265 *R/12-dbCreateTable.R cf34cbfa5168be4ad5eb444630878ea7 *R/13-dbWriteTable.R d5ead71c91f1a898b1eed2344b2a10fd *R/14-dbSendQuery.R 495e39d52950fcdcf7048e33a4e64a0a *R/15-dbBind.R a5a820218b1037f6007c9f8e8cd0f7fc *R/21-dbAppendTableArrow.R af59ea8e692671b4a3999209d4f1879a *R/22-dbCreateTableArrow.R 0b880d74411eed131a9493aae28a179f *R/23-dbWriteTableArrow.R 6d4afc3ecf8f2f30704a9818c61d9c48 *R/24-dbSendQueryArrow.R cf3c78c6dd40ff0543cf9c0d9ac12bf8 *R/25-dbBindArrow.R 05042a2430f0550883d5dbdc8a1e7260 *R/DBI-package.R cdd8f252d119dd2440952a829a91d81e *R/DBIConnector.R b2f768366db7da783ad65fca06d8012f *R/SQL.R caeed8e6b8e2eb866e8d2adee097cffb *R/SQLKeywords.R 2e3f7c99fc5daf79625510e2639a5243 *R/SQLKeywords_DBIObject.R cc8c512231d31031200e31d760ad008b *R/SQLKeywords_missing.R 4d9aa53c1ba51a9cdc12438530a86b64 *R/data-types.R 19cd20ad37a89a7fd9046bd159252be1 *R/data.R d7f9de677c0017d6e0c5b544ffeada99 *R/dbAppendTableArrow_DBIConnection.R 98300895840f652eb932b566fcba37ba *R/dbAppendTable_DBIConnection.R e900a6ce7e29178aa307ca2169433da4 *R/dbBegin.R 4ec90f1ff24745365a46f8182e9f5577 *R/dbBindArrow_DBIResult.R 37fee62a4e0f1ce0b4922ca436a44978 *R/dbBindArrow_DBIResultArrowDefault.R 9641bb6f1784fab5dfe4950f42f97098 *R/dbBind_DBIResultArrow.R 4d18b71c11b50a6c736046aa8c6b5e81 *R/dbCallProc.R 9ee1e1b8b67059460420430807f368e1 *R/dbCanConnect.R 8e74ceea09e2d78e7578dec900608289 *R/dbCanConnect_DBIDriver.R 6c42dfe37ae152191e0448ccb141403a *R/dbClearResult.R 83046f3ed56c119a9e877c5b3111177b *R/dbClearResult_DBIResultArrow.R c49c0c4039f2de60588674d638adce9d *R/dbColumnInfo.R 1dabdc46053a1f642277624017c1450b *R/dbCommit.R 5e5870604695bc0349a5cb88fabc0a15 *R/dbConnect.R 2650c8652de8a83756fedc456a03d476 *R/dbConnect_DBIConnector.R f776b9958ed3b36bcb20cb14e332ef43 *R/dbCreateTableArrow_DBIConnection.R b4ca03a0e43bed3b3cb9727f60ce8972 *R/dbCreateTable_DBIConnection.R be8236ab5a53269ffba3547a24250615 *R/dbDataType.R e86feef168b8c012513dd50b015fcd9e *R/dbDataType_DBIConnector.R 0c75124e20e8fb03d107b30a27c19760 *R/dbDataType_DBIObject.R 3f01d06b2390c76fcaf31fc84ab494a1 *R/dbDisconnect.R d66a755c1bf2907a0b0e50056d145311 *R/dbDriver.R 77006a92266de53743b1b27dc2166e52 *R/dbDriver_character.R fed6e5a93011a01cfd9d15fdfc326208 *R/dbExecute.R 0ccf1a45aeaa32d7d277395b2d7c012d *R/dbExecute_DBIConnection_character.R e58fcaa3742162f31d3d29d3dfa69a48 *R/dbExistsTable.R f5c1fa86bf5c8090e849d85127669ba1 *R/dbExistsTable_DBIConnection_Id.R 9b836fc3ce8672aa6ed07e2e5a44c6c6 *R/dbFetch.R c164207c1e7f72f3140dabaa871fdd4f *R/dbFetchArrow.R 9e6952bfb89b6c7b441a8ad9a2c790ea *R/dbFetchArrowChunk.R a66560bf24f18549eeeb285777a072ad *R/dbFetchArrowChunk_DBIResultArrow.R 3b578aad710e05a8af21dd41d71bbd28 *R/dbFetchArrow_DBIResultArrow.R e98adbf9e505b36bceaaea8f3c935573 *R/dbFetch_DBIResult.R 7ade7dc6b29c0c94dff74dd8088df3f5 *R/dbFetch_DBIResultArrow.R 85a9f801cce4583dfde1b9cc8383145f *R/dbGetConnectArgs.R 115ea9a3b433f0f7e040f4eba201111e *R/dbGetConnectArgs_DBIConnector.R 2982ccce2dd23ab15b2a6b3d4e0697a3 *R/dbGetException.R 9ba3e9fba1a421f7905e16a8fa3d1e6c *R/dbGetInfo.R 2fd40282c5a9b312901ecc629586f37f *R/dbGetInfo_DBIResult.R bb4fcd50d16319130582914d62557e6f *R/dbGetInfo_DBIResultArrow.R 52227dda89977b4528636ff0acba45da *R/dbGetQuery.R 38f9d19bbe2bd106ae3ed459602ef465 *R/dbGetQueryArrow.R 41cdbf853f51ca8e8b309e3c86b84052 *R/dbGetQueryArrow_DBIConnection.R 68ae362dc37aa0d769441a1938e027e8 *R/dbGetQuery_DBIConnection_character.R 959c58cd89928b6a16f11bd9c33a027c *R/dbGetRowCount.R f3a524cf2d7e3ac9ca18ad4ec0c75ddf *R/dbGetRowCount_DBIResultArrow.R 287337484b5f094245e8980da9160737 *R/dbGetRowsAffected.R ffd293243ac1b8a5c63d5df808d47e0a *R/dbGetRowsAffected_DBIResultArrow.R 402ef1dc8c406dce2f87eddbde82d789 *R/dbGetStatement.R 13db35076155e485b92abfb02a6f8f76 *R/dbGetStatement_DBIResultArrow.R 0a5c00c7c9812cfe4c96c2d376fa2946 *R/dbHasCompleted.R a42df80d60c38958cb8b93247baccfd0 *R/dbHasCompleted_DBIResultArrow.R f5547a131754975a92f3879f86c80ed5 *R/dbIsReadOnly.R 20c1c442df9885b1dde2a79b4d5fdc52 *R/dbIsReadOnly_DBIConnector.R 083f467fd264c59ccafacef611d3429d *R/dbIsReadOnly_DBIObject.R a186bdf6d0c8d3e0b78c6a1094f26fd4 *R/dbIsValid.R 13ee3657325cf77ac02feac607cef513 *R/dbIsValid_DBIResultArrowDefault.R 0b8b92d0d78cebc2b88ba17b3ebe8574 *R/dbListConnections.R 6f1d641a9ec46c4d5e1b32be18ce1247 *R/dbListFields.R fc143f42ee66f163a2029905c0d0376f *R/dbListFields_DBIConnection_Id.R 7c220952130574853a9892960a784d1b *R/dbListFields_DBIConnection_character.R b2e22417ac3d8436b2f56fc10455dc68 *R/dbListObjects.R e2cdc2847371073a478df43ff17b5c9d *R/dbListObjects_DBIConnection_ANY.R a465bb1c64e72d5e7fc3c60e39bcacaf *R/dbListResults.R d463a14ae7878452e5f3f72001ee7e35 *R/dbListTables.R 862474d590c6846daaeb12d65ab32c45 *R/dbQuoteIdentifier.R d80f59eecd7a572ea44a7997694d939a *R/dbQuoteIdentifier_DBIConnection.R 1c63676069d58c4bf193742e2d7113b8 *R/dbQuoteLiteral.R 8b9f442229fbe6c60615bdd903ff0c51 *R/dbQuoteLiteral_DBIConnection.R 7d0c587f2e3894ba81e292c1b5d6a5d6 *R/dbQuoteString.R 0974935ea604879e4367f367d0d94bad *R/dbQuoteString_DBIConnection.R 84e13a6ada4e00a661369339993b0dc2 *R/dbReadTable.R 24a6fab62a93fa7e824ef64401a85194 *R/dbReadTableArrow.R e5ea480546bbac115d297a13e4f74177 *R/dbReadTableArrow_DBIConnection.R 1be9fdeeea4c0bfcb3321b534b80097d *R/dbReadTable_DBIConnection_Id.R 61f6bb0784e687f75a2515bd128ce84e *R/dbReadTable_DBIConnection_character.R 1c4995f9f8d32e3e5fd465739a44546f *R/dbRemoveTable.R f8b15fec3e7da5e74551779fb36d315b *R/dbRemoveTable_DBIConnection_Id.R d1bb64bedf72456c277d755dc3019bd7 *R/dbRollback.R a2445ca996660aea9a1ffd2122b85fd2 *R/dbSendQueryArrow_DBIConnection.R 252842841b9de691f29c87e3066be2d1 *R/dbSendStatement.R f6e93624dcaae0b79400b2dbd19eeff6 *R/dbSendStatement_DBIConnection_character.R ffd26e8de2efd581f655c68e19430651 *R/dbSetDataMappings.R e673e520bbf8d0c8b7635474872211f9 *R/dbUnloadDriver.R 2afffa399bf9ae54e659699187b54241 *R/dbUnquoteIdentifier.R 59d10e6057e53b02202ee69d158272cc *R/dbUnquoteIdentifier_DBIConnection.R a076d570b2ac355a5bd1bffc0cfc9eb7 *R/dbWithTransaction.R e5c2e8bbef965ec03de7a4b7d4ee783a *R/dbWithTransaction_DBIConnection.R ace89ef65de9cb028919c13f92a71c77 *R/dbWriteTableArrow_DBIConnection.R 09a5767589db14c3c3ba73553030ed23 *R/dbWriteTable_DBIConnection_Id_ANY.R 8277fb3db3b97aa958d0c4061de85f30 *R/dbiDataType.R 650d9ed6004ebf09774427ee668ed4a9 *R/dbiDataType_ANY.R 65e5f21c95d37a35f6c8e9bf26af4924 *R/dbiDataType_AsIs.R e14fcdbe5bd13075c2193fa6ffaf5725 *R/dbiDataType_Date.R ac198cf63328dbe7fd1711cb184b8676 *R/dbiDataType_POSIXct.R 94c34b67f3b9c2182a76f58b514294b9 *R/dbiDataType_character.R c83e452b5b55e1fa6a4db75c846ed422 *R/dbiDataType_data.frame.R 13b50d36a649b4b9a31210bd60334a22 *R/dbiDataType_default.R 450179c1d1f5a291ff0356d162a16dd3 *R/dbiDataType_difftime.R 6b84efab5913fff83c08e4395add3887 *R/dbiDataType_integer.R 5b77a56457bb158205ed0ba49cf09422 *R/dbiDataType_list.R 2ef2c7e953c5fe370c087dc1a47cb8cd *R/dbiDataType_logical.R 5212cee8aa1f93cb8858891aa051cd6f *R/dbiDataType_numeric.R 7b11396db0584f8dcfb58a6204ca8c4d *R/deprecated.R 1287ce9bc9bb3a7d8a6c5107427daa38 *R/fetch.R 5651cd8a666eb10359ab0a1796e3436c *R/hms.R 91b19c51abe58a6d1de6a45579350694 *R/interpolate.R 4126e52937f6f393db327b732c514ae6 *R/isSQLKeyword.R 0a88ed941faa636132ad3d52f73af8cf *R/isSQLKeyword_DBIObject_character.R c86571daef158f70da25b27202a5d650 *R/make.db.names.R b41c1f90d364dcc59258aba6b8655a11 *R/make.db.names_DBIObject_character.R d299a8067c3c4c3f324ce07324b41030 *R/methods_as_rd.R 475c479c78008458508ab9ab9100c4a5 *R/rownames.R d0f80664d65f61b3333651242759530d *R/show_AnsiConnection.R 3517272e0ee5248cb2cda618e5725e06 *R/show_DBIConnection.R 44656888881609c3aaaba36d118bd00b *R/show_DBIConnector.R c56d4e1596bc44c0b69148d3a8e75668 *R/show_DBIDriver.R ea4f9428ed80facc11f600319d096efb *R/show_DBIResult.R c55be6c2418396a61394653ab4d667aa *R/show_Id.R 5b47c215dc77c4743a76852e264e67ce *R/show_SQL.R 0571b97a57ef2f373003f52a416f0d36 *R/sqlAppendTable.R db577eb92c0f9e9e5d2b1a845f78218d *R/sqlAppendTableTemplate.R b6e559aa5ede9ec6945a695e7dab0600 *R/sqlAppendTable_DBIConnection.R fea1511aa6ef8a5b4e87572c425d60e3 *R/sqlCreateTable.R c04a2ea0203342e3790c5cd77a4ffa75 *R/sqlCreateTable_DBIConnection.R 900d01b72095344950f5854679dd84ba *R/sqlData.R 24f1bf8225b3cd27b652ecd726b0b7bf *R/sqlData_DBIConnection.R 2764379e7293fd7e2ecaa15cc11341d6 *R/sqlInterpolate.R 89177ca946708c77672ede3dc9b2d2ad *R/sqlInterpolate_DBIConnection.R f25218d24f247f5d5b8b70a3d878e082 *R/sqlParseVariables.R a0349cfd6f9eab18042640fae7fcf5c2 *R/sqlParseVariables_DBIConnection.R 42f3ac8f9e3bf2c02205e18b7be385f3 *R/summary.R 85cab3f8e3af768d579592639c24a40c *R/summary_DBIObject.R c2e81afb106abc23851775e46d795000 *R/transactions.R d0ee7781a70a796a4a25e513a69138c9 *README.md 0c6929c84389e4822c2efcea11b8832e *build/DBI.pdf e67846fc7f561cb928b3a5121e998981 *build/stage23.rdb aff3af0e759fbba0833a2663270ab330 *build/vignette.rds 4f23fe94e7b1c0e0f5d07dbe298645bf *inst/doc/DBI-1.Rmd 611b4cde1385bed160c18fa881b77f16 *inst/doc/DBI-1.html 859f982ebae9f868a6b2f50f1d8ab994 *inst/doc/DBI-advanced.R e4aea740ecb8bf1c878346b0f3f21e2d *inst/doc/DBI-advanced.Rmd 2ee9c4412d7a770114e5cc4b9e20b5e7 *inst/doc/DBI-advanced.html 95fb12f4306c5310eb1f2031de5e8a4a *inst/doc/DBI-arrow.R 75540b51f9123b5f2d12716079a4900e *inst/doc/DBI-arrow.Rmd 55698281e871393cceed25188aa964e4 *inst/doc/DBI-arrow.html 0cb90dc5f9e5b0a9b289f70dfe997079 *inst/doc/DBI-history.Rmd a08e730c0c2f3c4f7bb370540800f70f *inst/doc/DBI-history.html 1d63a9a39439cf84d18d2ef16ad8c30f *inst/doc/DBI-proposal.Rmd 2a3245bfc9423a379175736fa58d4f89 *inst/doc/DBI-proposal.html 84a71bc3aeea989ef8332b9737f78e63 *inst/doc/DBI.R 7273e8ea9b40598970cbcd5d99778ce5 *inst/doc/DBI.Rmd 5f09a586cec2f3b0d9ff282b7beca6f0 *inst/doc/DBI.html 9c78777c778e752aa9c7b00e0276d7ed *inst/doc/backend.R 079397ec63b690111df65842436e40ad *inst/doc/backend.Rmd 9faff0018e87a7a07c7bd58e906ba2ac *inst/doc/backend.html 79a10903a9332c71d8092d7859073f1f *inst/doc/spec.R 55510128b0e7e531f19c4229874cfd0e *inst/doc/spec.Rmd df4793ce291bf6fda0545147825f1ee7 *inst/doc/spec.html 3414b76d8057e97cfd58968b7a7ac837 *man/ANSI.Rd ca1f4924bbe96b29d4232c3d5790bc3e *man/DBI-package.Rd ab80a97af0eaf4830ffb5a9461b74641 *man/DBIConnection-class.Rd fbbc951da774063bd0e2136b46142a29 *man/DBIConnector-class.Rd d6bab15f03567bc5047491d1b1de9ac2 *man/DBIDriver-class.Rd 95b414ddf62b52d5e3991ebde2bb9bd8 *man/DBIObject-class.Rd 73f7e24e72271377afe15a0d32772fe5 *man/DBIResult-class.Rd 410ef6f7cebf63c23f1c529abfed78b2 *man/DBIResultArrow-class.Rd 3a90727203cd716586e82c69e8af3717 *man/Id.Rd 0abe5e81e5b910eb92f501e0d12102f5 *man/SQL.Rd 9ca08a779d4dc555682b818c64a72ea6 *man/dbAppendTable.Rd 83eb878e2fda73b7043893a138810ee1 *man/dbAppendTableArrow.Rd 269ffa6560d49a04493bb4cf70ddd0a5 *man/dbBind.Rd f087a3da11250b3d4671313d3218da0c *man/dbCallProc.Rd d51f7887d3d93354845348e6c0d41ae0 *man/dbCanConnect.Rd 2db5ab546ad5886af01d2cdd2abee2c7 *man/dbClearResult.Rd 891d46c3f777cffacf07ea61b21f3e45 *man/dbColumnInfo.Rd 0b5b91df5d762f6c66217df381c006f8 *man/dbConnect.Rd 202feaea29c6ac07bcf18011c60908d2 *man/dbCreateTable.Rd 98e3fea5a3ef7c02fa03ed9d6a8c59d2 *man/dbCreateTableArrow.Rd 49ca842dac22bb37338ae741b3aa5818 *man/dbDataType.Rd e43371bad14fe49155cd7f3a19726e13 *man/dbDisconnect.Rd 39cfe00271b1b9bf943383c9effcad85 *man/dbDriver.Rd 07a25413e45b3b7a016b52f438f653c7 *man/dbExecute.Rd 3413e28ba265fb4b5a2e9bf5323bc3a6 *man/dbExistsTable.Rd 5df6c705e3909ea3f654c689b49c5aec *man/dbFetch.Rd 9f6a96f8af9adad24e217e89d57fddee *man/dbFetchArrow.Rd ff966e7324f57067bde27f3d35805a80 *man/dbFetchArrowChunk.Rd 05ffd824319d21145d084e7c150fd5f6 *man/dbGetConnectArgs.Rd 600709b1318e882e99b98e90fa8ba7e7 *man/dbGetDBIVersion.Rd 5407452897fa0a555cd2a693f45bbf87 *man/dbGetException.Rd 9c2f75af96fd527356fbad93e7fc9d2b *man/dbGetInfo.Rd 9787f179ba0245776c5dc761cadc0b03 *man/dbGetQuery.Rd dfe041c29e196dc1dc419c872cd9ef0d *man/dbGetQueryArrow.Rd 04dfeaa19769335d9a1888a04e9fd6c5 *man/dbGetRowCount.Rd 67fef2da3f284238891678ba8ef1bd56 *man/dbGetRowsAffected.Rd 7d3e5a17a2e866bae80b132757c77495 *man/dbGetStatement.Rd 0bbc869549227e50e4c87c9e7c76d07b *man/dbHasCompleted.Rd 12718205b9dd838dfcea973df6a99197 *man/dbIsReadOnly.Rd 7ec84eb5a3c6199b606f93eaf5b67b85 *man/dbIsValid.Rd 45195aabed941c5835837ef3944a48f6 *man/dbListConnections.Rd cea3c825675995991fe650cbffc35310 *man/dbListFields.Rd 01ced763517ec2131d1a3856276969ca *man/dbListObjects.Rd 58732b4fa70cf51a2770513b2ad54e8f *man/dbListResults.Rd ade0fee9405cf8a697bb7d38ad8b1656 *man/dbListTables.Rd be7f0c0ff7401f6eb68a22b08cfe1fb9 *man/dbQuoteIdentifier.Rd 2df8574f499bb96b4175811d03c2ac11 *man/dbQuoteLiteral.Rd abf1f4b79010ac0f23838b9defac307d *man/dbQuoteString.Rd 5d71a9b592d439f4f3e5643c41fad49c *man/dbReadTable.Rd 008c622b6c04ad85d9677d19318f3197 *man/dbReadTableArrow.Rd 12ed8873608e8406cf034334cebe950a *man/dbRemoveTable.Rd 41f4b815f477ac1526287df025f2bb3e *man/dbSendQuery.Rd 041e7bd404116507511fe5d540dd9cfe *man/dbSendQueryArrow.Rd 944d7e3df0fb8502b2d22d4c42c4ce08 *man/dbSendStatement.Rd 62847b9c4d0251dd8ba14ab4d1f2005f *man/dbSetDataMappings.Rd e2c6e3ec488402badefce8f72fd70e3c *man/dbUnquoteIdentifier.Rd 1bb104fe3f9c9bf64e54224d1149f966 *man/dbWithTransaction.Rd 9996f068a8772f32f8d962938541767c *man/dbWriteTable.Rd 2b0c3b2302f6d9770fb31b350cb50779 *man/dbWriteTableArrow.Rd eeb064c9b0e28e5263755b8b2b8fbf13 *man/dot-SQL92Keywords.Rd a1cbaf3f328e8d74e747faacf640c7fc *man/figures/lifecycle-archived.svg 6f521fb1819410630e279d1abf88685a *man/figures/lifecycle-defunct.svg 391f696f961e28914508628a7af31b74 *man/figures/lifecycle-deprecated.svg 691b1eb2aec9e1bec96b79d11ba5e631 *man/figures/lifecycle-experimental.svg 405e252e54a79b33522e9699e4e9051c *man/figures/lifecycle-maturing.svg f41ed996be135fb35afe00641621da61 *man/figures/lifecycle-questioning.svg 306bef67d1c636f209024cf2403846fd *man/figures/lifecycle-soft-deprecated.svg ed42e3fbd7cc30bc6ca8fa9b658e24a8 *man/figures/lifecycle-stable.svg bf2f1ad432ecccee3400afe533404113 *man/figures/lifecycle-superseded.svg 3bbccfce9273099763a85541a3f653d5 *man/hidden_aliases.Rd ffba08bcb57becb6455b5165b6ef441d *man/make.db.names.Rd 4a7f8a265551b2f3dea24c3692721638 *man/rownames.Rd 5a453dec45fc5446ff0f2fe79c2c8e47 *man/sqlAppendTable.Rd 68107961a34d4649f3a65a98ffaed1da *man/sqlCreateTable.Rd 8e60c9fd9089f329a66109bcb33762a6 *man/sqlData.Rd 7ffb373db05e03d2408935888800d8d3 *man/sqlInterpolate.Rd f0d18acb231943d6f25691e6d1558492 *man/sqlParseVariables.Rd 0304b917fc8a3c45937ba0a85adc9515 *man/transactions.Rd bf33e807cc16ea1b4376f48ebde12861 *tests/testthat.R 72e4e900b434270afacf30c871276669 *tests/testthat/_snaps/00-Id.md a607e1deab234336d12e88ad2b80fd80 *tests/testthat/helper-dummy.R 6d7152ea22dc498b844cb6d912b1c771 *tests/testthat/setup.R 513ea56d219dfe4e417f9eb46e2ad904 *tests/testthat/test-00-Id.R 4812b88c1f17717cd89d9c3bfe279b4f *tests/testthat/test-DBItest.R 4c1320f3b7ceeb77d067450f0421991f *tests/testthat/test-arrow.R c85afd831e2fdf9e4cbb9a8ebb73671e *tests/testthat/test-data-type.R 3f714565f149898283b4521d6363c4e9 *tests/testthat/test-dbUnquoteIdentifier_DBIConnection.R a715746851715628777aa126e248c956 *tests/testthat/test-interpolate.R 7413bb46ce0b157be435b7fe17523d59 *tests/testthat/test-methods.R e701a57076d59ecf60767f3a61bba1c2 *tests/testthat/test-quote.R 0c6dc973642147f079d15e0477aa63d4 *tests/testthat/test-quoting.R 7895ec58f5c8d1e39634cbe839439283 *tests/testthat/test-rownames.R d6fd2ea45be6ac9ebf2643f2ea29dcdf *tests/testthat/test-sql-df.R bda1a87eaadd2fa466b451a36be1bf7a *tests/testthat/test-table-insert.R 4f23fe94e7b1c0e0f5d07dbe298645bf *vignettes/DBI-1.Rmd e4aea740ecb8bf1c878346b0f3f21e2d *vignettes/DBI-advanced.Rmd 75540b51f9123b5f2d12716079a4900e *vignettes/DBI-arrow.Rmd 0cb90dc5f9e5b0a9b289f70dfe997079 *vignettes/DBI-history.Rmd 1d63a9a39439cf84d18d2ef16ad8c30f *vignettes/DBI-proposal.Rmd 7273e8ea9b40598970cbcd5d99778ce5 *vignettes/DBI.Rmd 079397ec63b690111df65842436e40ad *vignettes/backend.Rmd 67cca7009a40f5c6bab58418607deb57 *vignettes/biblio.bib 16facd043de5250ab88f5b3badef9ab0 *vignettes/hierarchy.png 55510128b0e7e531f19c4229874cfd0e *vignettes/spec.Rmd 601db5347a1ea8cfee3e11f964a53644 *vignettes/spec.md DBI/inst/0000755000176200001440000000000014561352217011633 5ustar liggesusersDBI/inst/doc/0000755000176200001440000000000014561352217012400 5ustar liggesusersDBI/inst/doc/DBI-advanced.R0000644000176200001440000001326214561352215014666 0ustar liggesusers## ----setup, include=FALSE----------------------------------------------------- library(knitr) opts_chunk$set( echo = TRUE, error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5"), # FIXME: Bring back when relational.fit clone is up eval = FALSE ) knit_print.data.frame <- function(x, ...) { print(head(x, 3)) if (nrow(x) > 3) { cat("Showing 3 out of", nrow(x), "rows.\n") } invisible(x) } registerS3method("knit_print", "data.frame", "knit_print.data.frame") ## ----------------------------------------------------------------------------- # library(DBI) # # con <- dbConnect( # RMariaDB::MariaDB(), # host = "relational.fit.cvut.cz", # port = 3306, # username = "guest", # password = "relational", # dbname = "sakila" # ) # # res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = 'G'") # df <- dbFetch(res, n = 3) # dbClearResult(res) # # head(df, 3) ## ----------------------------------------------------------------------------- # res <- dbSendQuery(con, "SELECT * FROM film") # while (!dbHasCompleted(res)) { # chunk <- dbFetch(res, n = 300) # print(nrow(chunk)) # } # dbClearResult(res) ## ----quote-------------------------------------------------------------------- # # safe_id <- dbQuoteIdentifier(con, "rating") # safe_param <- dbQuoteLiteral(con, "G") # # query <- paste0("SELECT title, ", safe_id, " FROM film WHERE ", safe_id, " = ", safe_param) # query # # res <- dbSendQuery(con, query) # dbFetch(res) # dbClearResult(res) ## ----------------------------------------------------------------------------- # id <- "rating" # param <- "G" # query <- glue::glue_sql("SELECT title, {`id`} FROM film WHERE {`id`} = {param}", .con = con) # # df <- dbGetQuery(con, query) # head(df, 3) ## ----params------------------------------------------------------------------- # params <- list("G") # safe_id <- dbQuoteIdentifier(con, "rating") # # query <- paste0("SELECT * FROM film WHERE ", safe_id, " = ?") # query # # res <- dbSendQuery(con, query, params = params) # dbFetch(res, n = 3) # dbClearResult(res) ## ----multi-param-------------------------------------------------------------- # q_params <- list("G", 90) # query <- "SELECT title, rating, length FROM film WHERE rating = ? AND length >= ?" # # res <- dbSendQuery(con, query, params = q_params) # dbFetch(res, n = 3) # dbClearResult(res) ## ----dbbind------------------------------------------------------------------- # res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = ?") # dbBind(res, list("G")) # dbFetch(res, n = 3) # dbBind(res, list("PG")) # dbFetch(res, n = 3) # dbClearResult(res) ## ----bind_quotestring--------------------------------------------------------- # res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = ?") # dbBind(res, list(c("G", "PG"))) # dbFetch(res, n = 3) # dbClearResult(res) ## ----bind-multi-param--------------------------------------------------------- # q_params <- list(c("G", "PG"), c(90, 120)) # query <- "SELECT title, rating, length FROM film WHERE rating = ? AND length >= ?" # # res <- dbSendQuery(con, query, params = q_params) # dbFetch(res, n = 3) # dbClearResult(res) ## ----disconnect--------------------------------------------------------------- # dbDisconnect(con) ## ----------------------------------------------------------------------------- # library(DBI) # con <- dbConnect(RSQLite::SQLite(), ":memory:") # # dbWriteTable(con, "cars", head(cars, 3)) # # dbExecute( # con, # "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" # ) # # rs <- dbSendStatement( # con, # "INSERT INTO cars (speed, dist) VALUES (4, 4), (5, 5), (6, 6)" # ) # dbGetRowsAffected(rs) # dbClearResult(rs) # # dbReadTable(con, "cars") ## ----------------------------------------------------------------------------- # dbDisconnect(con) ## ----------------------------------------------------------------------------- # con <- dbConnect(RSQLite::SQLite(), ":memory:") # # dbWriteTable(con, "cash", data.frame(amount = 100)) # dbWriteTable(con, "account", data.frame(amount = 2000)) # # withdraw <- function(amount) { # # All operations must be carried out as logical unit: # dbExecute(con, "UPDATE cash SET amount = amount + ?", list(amount)) # dbExecute(con, "UPDATE account SET amount = amount - ?", list(amount)) # } # # withdraw_transacted <- function(amount) { # # Ensure atomicity # dbBegin(con) # # # Perform operation # withdraw(amount) # # # Persist results # dbCommit(con) # } # # withdraw_transacted(300) ## ----------------------------------------------------------------------------- # dbReadTable(con, "cash") # dbReadTable(con, "account") ## ----------------------------------------------------------------------------- # withdraw_if_funds <- function(amount) { # dbBegin(con) # withdraw(amount) # # Rolling back after detecting negative value on account: # if (dbReadTable(con, "account")$amount >= 0) { # dbCommit(con) # TRUE # } else { # message("Insufficient funds") # dbRollback(con) # FALSE # } # } # # withdraw_if_funds(5000) # dbReadTable(con, "cash") # dbReadTable(con, "account") ## ----error = TRUE------------------------------------------------------------- # withdraw_safely <- function(amount) { # dbWithTransaction(con, { # withdraw(amount) # if (dbReadTable(con, "account")$amount < 0) { # stop("Error: insufficient funds", call. = FALSE) # } # }) # } # # withdraw_safely(5000) # dbReadTable(con, "cash") # dbReadTable(con, "account") ## ----------------------------------------------------------------------------- # dbDisconnect(con) DBI/inst/doc/backend.html0000644000176200001440000007315014561352217014663 0ustar liggesusersImplementing a new backend

Implementing a new backend

Hadley Wickham, Kirill Müller

The goal of this document is to help you implement a new backend for DBI.

If you are writing a package that connects a database to R, I highly recommend that you make it DBI compatible because it makes your life easier by spelling out exactly what you need to do. The consistent interface provided by DBI makes it easier for you to implement the package (because you have fewer arbitrary choices to make), and easier for your users (because it follows a familiar pattern). In addition, the DBItest package provides test cases which you can easily incorporate in your package.

I’ll illustrate the process using a fictional database called Kazam.

Getting started

Start by creating a package. It’s up to you what to call the package, but following the existing pattern of RSQLite, RMySQL, RPostgres and ROracle will make it easier for people to find it. For this example, I’ll call my package RKazam.

A ready-to-use template package is available at https://github.com/r-dbi/RKazam/. You can start by creating a new GitHub repository from this template, or by copying the package code. Rename “Kazam” to your desired name everywhere. The template package already contains dummy implementations for all classes and methods.

If you chose to create the package manually, make sure to include in your DESCRIPTION:

Imports:
  DBI (>= 0.3.0),
  methods
Suggests:
  DBItest, testthat

Importing DBI is fine, because your users are not supposed to attach your package anyway; the preferred method is to attach DBI and use explicit qualification via :: to access the driver in your package (which needs to be done only once).

Testing

Why testing at this early stage? Because testing should be an integral part of the software development cycle. Test right from the start, add automated tests as you go, finish faster (because tests are automated) while maintaining superb code quality (because tests also check corner cases that you might not be aware of). Don’t worry: if some test cases are difficult or impossible to satisfy, or take too long to run, you can just turn them off.

Take the time now to head over to the DBItest vignette at vignette("test", package = "DBItest"). You will find a vast amount of ready-to-use test cases that will help you in the process of implementing your new DBI backend.

Add custom tests that are not covered by DBItest at your discretion, or enhance DBItest and file a pull request if the test is generic enough to be useful for many DBI backends.

Driver

Start by making a driver class which inherits from DBIDriver. This class doesn’t need to do anything, it’s just used to dispatch other generics to the right method. Users don’t need to know about this, so you can remove it from the default help listing with @keywords internal:

#' Driver for Kazam database.
#'
#' @keywords internal
#' @export
#' @import DBI
#' @import methods
setClass("KazamDriver", contains = "DBIDriver")

The driver class was more important in older versions of DBI, so you should also provide a dummy dbUnloadDriver() method.

#' @export
#' @rdname Kazam-class
setMethod("dbUnloadDriver", "KazamDriver", function(drv, ...) {
  TRUE
})

If your package needs global setup or tear down, do this in the .onLoad() and .onUnload() functions.

You might also want to add a show method so the object prints nicely:

setMethod("show", "KazamDriver", function(object) {
  cat("<KazamDriver>\n")
})

Next create Kazam() which instantiates this class.

#' @export
Kazam <- function() {
  new("KazamDriver")
}

Kazam()
#> <KazamDriver>

Connection

Next create a connection class that inherits from DBIConnection. This should store all the information needed to connect to the database. If you’re talking to a C api, this will include a slot that holds an external pointer.

#' Kazam connection class.
#'
#' @export
#' @keywords internal
setClass("KazamConnection",
  contains = "DBIConnection",
  slots = list(
    host = "character",
    username = "character",
    # and so on
    ptr = "externalptr"
  )
)

Now you have some of the boilerplate out of the way, you can start work on the connection. The most important method here is dbConnect() which allows you to connect to a specified instance of the database. Note the use of @rdname Kazam. This ensures that Kazam() and the connect method are documented together.

#' @param drv An object created by \code{Kazam()}
#' @rdname Kazam
#' @export
#' @examples
#' \dontrun{
#' db <- dbConnect(RKazam::Kazam())
#' dbWriteTable(db, "mtcars", mtcars)
#' dbGetQuery(db, "SELECT * FROM mtcars WHERE cyl == 4")
#' }
setMethod("dbConnect", "KazamDriver", function(drv, ...) {
  # ...

  new("KazamConnection", host = host, ...)
})

  • Replace ... with the arguments needed to connect to your database. You’ll always need to include ... in the arguments, even if you don’t use it, for compatibility with the generic.

  • This is likely to be where people first come for help, so the examples should show how to connect to the database, and how to query it. (Obviously these examples won’t work yet.) Ideally, include examples that can be run right away (perhaps relying on a publicly hosted database), but failing that surround in \dontrun{} so people can at least see the code.

Next, implement show() and dbDisconnect() methods.

Results

Finally, you’re ready to implement the meat of the system: fetching results of a query into a data frame. First define a results class:

#' Kazam results class.
#'
#' @keywords internal
#' @export
setClass("KazamResult",
  contains = "DBIResult",
  slots = list(ptr = "externalptr")
)

Then write a dbSendQuery() method. This takes a connection and SQL string as arguments, and returns a result object. Again ... is needed for compatibility with the generic, but you can add other arguments if you need them.

#' Send a query to Kazam.
#'
#' @export
#' @examples
#' # This is another good place to put examples
setMethod("dbSendQuery", "KazamConnection", function(conn, statement, ...) {
  # some code
  new("KazamResult", ...)
})

Next, implement dbClearResult(), which should close the result set and free all resources associated with it:

#' @export
setMethod("dbClearResult", "KazamResult", function(res, ...) {
  # free resources
  TRUE
})

The hardest part of every DBI package is writing the dbFetch() method. This needs to take a result set and (optionally) number of records to return, and create a dataframe. Mapping R’s data types to those of your database may require a custom implementation of the dbDataType() method for your connection class:

#' Retrieve records from Kazam query
#' @export
setMethod("dbFetch", "KazamResult", function(res, n = -1, ...) {
  ...
})

# (optionally)

#' Find the database data type associated with an R object
#' @export
setMethod("dbDataType", "KazamConnection", function(dbObj, obj, ...) {
  ...
})

Next, implement dbHasCompleted() which should return a logical indicating if there are any rows remaining to be fetched.

#' @export
setMethod("dbHasCompleted", "KazamResult", function(res, ...) {

})

With these four methods in place, you can now use the default dbGetQuery() to send a query to the database, retrieve results if available and then clean up. Spend some time now making sure this works with an existing database, or relax and let the DBItest package do the work for you.

SQL methods

You’re now on the home stretch, and can make your wrapper substantially more useful by implementing methods that wrap around variations in SQL across databases:

  • dbQuoteString() and dbQuoteIdentifer() are used to safely quote strings and identifiers to avoid SQL injection attacks. Note that the former must be vectorized, but not the latter.

  • dbWriteTable() creates a database table given an R dataframe. I’d recommend using the functions prefixed with sql in this package to generate the SQL. These functions are still a work in progress so please let me know if you have problems.

  • dbReadTable(): a simple wrapper around SELECT * FROM table. Use dbQuoteIdentifer() to safely quote the table name and prevent mismatches between the names allowed by R and the database.

  • dbListTables() and dbExistsTable() let you determine what tables are available. If not provided by your database’s API, you may need to generate sql that inspects the system tables.

  • dbListFields() shows which fields are available in a given table.

  • dbRemoveTable() wraps around DROP TABLE. Start with SQL::sqlTableDrop().

  • dbBegin(), dbCommit() and dbRollback(): implement these three functions to provide basic transaction support. This functionality is currently not tested in the DBItest package.

Metadata methods

There are a lot of extra metadata methods for result sets (and one for the connection) that you might want to implement. They are described in the following.

  • dbIsValid() returns if a connection or a result set is open (TRUE) or closed (FALSE). All further methods in this section are valid for result sets only.

  • dbGetStatement() returns the issued query as a character value.

  • dbColumnInfo() lists the names and types of the result set’s columns.

  • dbGetRowCount() and dbGetRowsAffected() returns the number of rows returned or altered in a SELECT or INSERT/UPDATE query, respectively.

  • dbBind() allows using parametrised queries. Take a look at sqlInterpolate() and sqlParseVariables() if your SQL engine doesn’t offer native parametrised queries.

Full DBI compliance

By now, your package should implement all methods defined in the DBI specification. If you want to walk the extra mile, offer a read-only mode that allows your users to be sure that their valuable data doesn’t get destroyed inadvertently.

DBI/inst/doc/DBI.R0000644000176200001440000000402514561352216013121 0ustar liggesusers## ----setup, include=FALSE----------------------------------------------------- knitr::opts_chunk$set( echo = TRUE, error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5"), # FIXME: Bring back when relational.fit clone is up eval = FALSE ) ## ----------------------------------------------------------------------------- # library(DBI) # # con <- dbConnect( # RMariaDB::MariaDB(), # host = "relational.fit.cvut.cz", # port = 3306, # username = "guest", # password = "relational", # dbname = "sakila" # ) # # dbListTables(con) # dbDisconnect(con) ## ----eval = FALSE------------------------------------------------------------- # con <- dbConnect( # RMariaDB::MariaDB(), # host = "relational.fit.cvut.cz", # port = 3306, # username = "guest", # password = keyring::key_get("relational.fit.cvut.cz", "guest"), # dbname = "sakila" # ) ## ----------------------------------------------------------------------------- # con <- dbConnect(RMariaDB::MariaDB(), username = "guest", password = "relational", host = "relational.fit.cvut.cz", port = 3306, dbname = "sakila") # dbListFields(con, "film") ## ----------------------------------------------------------------------------- # df <- dbReadTable(con, "film") # head(df, 3) ## ----------------------------------------------------------------------------- # df <- dbGetQuery(con, "SELECT film_id, title, description FROM film WHERE release_year = 2006") # head(df, 3) ## ----------------------------------------------------------------------------- # df <- dbGetQuery(con, "SELECT film_id, title, description FROM film WHERE release_year = 2006 AND rating = 'G'") # head(df, 3) ## ----message=FALSE------------------------------------------------------------ # library(dplyr) # # lazy_df <- # tbl(con, "film") %>% # filter(release_year == 2006 & rating == "G") %>% # select(film_id, title, description) # head(lazy_df, 3) ## ----------------------------------------------------------------------------- # dbDisconnect(con) DBI/inst/doc/DBI-1.Rmd0000644000176200001440000006004014552712323013576 0ustar liggesusers--- title: "A Common Database Interface (DBI)" author: "R-Databases Special Interest Group" date: "16 June 2003" output: rmarkdown::html_vignette bibliography: biblio.bib vignette: > %\VignetteIndexEntry{A Common Database Interface (DBI)} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- This document describes a common interface between the S language (in its R and S-Plus implementations) and database management systems (DBMS). The interface defines a small set of classes and methods similar in spirit to Perl’s DBI, Java’s JDBC, Python’s DB-API, and Microsoft’s ODBC. # Version {#sec:version} This document describes version 0.1-6 of the database interface API (application programming interface). # Introduction {#sec:intro} The database interface (DBI) separates the connectivity to the DBMS into a “front-end” and a “back-end”. Applications use only the exposed “front-end” API. The facilities that communicate with specific DBMS (Oracle, PostgreSQL, etc.) are provided by “device drivers” that get invoked automatically by the S language evaluator. The following example illustrates some of the DBI capabilities: ```R ## Choose the proper DBMS driver and connect to the server drv <- dbDriver("ODBC") con <- dbConnect(drv, "dsn", "usr", "pwd") ## The interface can work at a higher level importing tables ## as data.frames and exporting data.frames as DBMS tables. dbListTables(con) dbListFields(con, "quakes") if(dbExistsTable(con, "new_results")) dbRemoveTable(con, "new_results") dbWriteTable(con, "new_results", new.output) ## The interface allows lower-level interface to the DBMS res <- dbSendQuery(con, paste( "SELECT g.id, g.mirror, g.diam, e.voltage", "FROM geom_table as g, elec_measures as e", "WHERE g.id = e.id and g.mirrortype = 'inside'", "ORDER BY g.diam")) out <- NULL while(!dbHasCompleted(res)){ chunk <- fetch(res, n = 10000) out <- c(out, doit(chunk)) } ## Free up resources dbClearResult(res) dbDisconnect(con) dbUnloadDriver(drv) ``` (only the first 2 expressions are DBMS-specific – all others are independent of the database engine itself). Individual DBI drivers need not implement all the features we list below (we indicate those that are optional). Furthermore, drivers may extend the core DBI facilities, but we suggest to have these extensions clearly indicated and documented. The following are the elements of the DBI: 1. A set of classes and methods (Section [sec:DBIClasses]) that defines what operations are possible and how they are defined, e.g.: - connect/disconnect to the DBMS - create and execute statements in the DBMS - extract results/output from statements - error/exception handling - information (meta-data) from database objects - transaction management (optional) Some things are left explicitly unspecified, e.g., authentication and even the query language, although it is hard to avoid references to SQL and relational database management systems (RDBMS). 2. Drivers Drivers are collection of functions that implement the functionality defined above in the context of specific DBMS, e.g., mSQL, Informix. 3. Data type mappings (Section [sec:data-mappings].) Mappings and conversions between DBMS data types and R/S objects. All drivers should implement the “basic” primitives (see below), but may chose to add user-defined conversion function to handle more generic objects (e.g., factors, ordered factors, time series, arrays, images). 4. Utilities (Section [sec:utilities].) These facilities help with details such as mapping of identifiers between S and DBMS (e.g., `_` is illegal in R/S names, and `.` is used for constructing compound SQL identifiers), etc. # DBI Classes and Methods {#sec:DBIClasses} The following are the main DBI classes. They need to be extended by individual database back-ends (Sybase, Oracle, etc.) Individual drivers need to provide methods for the generic functions listed here (those methods that are optional are so indicated). *Note: Although R releases prior to 1.4 do not have a formal concept of classes, we will use the syntax of the S Version 4 classes and methods (available in R releases 1.4 and later as library `methods`) to convey precisely the DBI class hierarchy, its methods, and intended behavior.* The DBI classes are `DBIObject`, `DBIDriver`, `DBIConnection` and `DBIResult`. All these are *virtual* classes. Drivers define new classes that extend these, e.g., `PgSQLDriver`, `PgSQLConnection`, and so on. ![Class hierarchy for the DBI. The top two layers are comprised of virtual classes and each lower layer represents a set of driver-specific implementation classes that provide the functionality defined by the virtual classes above.](hierarchy.png) `DBIObject`: : Virtual class[^1] that groups all other DBI classes. `DBIDriver`: : Virtual class that groups all DBMS drivers. Each DBMS driver extends this class. Typically generator functions instantiate the actual driver objects, e.g., `PgSQL`, `HDF5`, `BerkeleyDB`. `DBIConnection`: : Virtual class that encapsulates connections to DBMS. `DBIResult`: : Virtual class that describes the result of a DBMS query or statement. [Q: Should we distinguish between a simple result of DBMS statements e.g., as `delete` from DBMS queries (i.e., those that generate data).] The methods `format`, `print`, `show`, `dbGetInfo`, and `summary` are defined (and *implemented* in the `DBI` package) for the `DBIObject` base class, thus available to all implementations; individual drivers, however, are free to override them as they see fit. `format(x, ...)`: : produces a concise character representation (label) for the `DBIObject` `x`. `print(x, ...)`/`show(x)`: : prints a one-line identification of the object `x`. `summary(object, ...)`: : produces a concise description of the object. The default method for `DBIObject` simply invokes `dbGetInfo(dbObj)` and prints the name-value pairs one per line. Individual implementations may tailor this appropriately. `dbGetInfo(dbObj, ...)`: : extracts information (meta-data) relevant for the `DBIObject` `dbObj`. It may return a list of key/value pairs, individual meta-data if supplied in the call, or `NULL` if the requested meta-data is not available. *Hint:* Driver implementations may choose to allow an argument `what` to specify individual meta-data, e.g., `dbGetInfo(drv, what = max.connections)`. In the next few sub-sections we describe in detail each of these classes and their methods. ## Class `DBIObject` {#sec:DBIObject} This class simply groups all DBI classes, and thus all extend it. ## Class `DBIDriver` {#sec:DBIDriver} This class identifies the database management system. It needs to be extended by individual back-ends (Oracle, PostgreSQL, etc.) The DBI provides the generator `dbDriver(driverName)` which simply invokes the function `driverName`, which in turn instantiates the corresponding driver object. The `DBIDriver` class defines the following methods: `driverName`: : [meth:driverName] initializes the driver code. The name `driverName` refers to the actual generator function for the DBMS, e.g., `RPgSQL`, `RODBC`, `HDF5`. The driver instance object is used with `dbConnect` (see page ) for opening one or possibly more connections to one or more DBMS. `dbListConnections(drv, ...)`: : list of current connections being handled by the `drv` driver. May be `NULL` if there are no open connections. Drivers that do not support multiple connections may return the one open connection. `dbGetInfo(dbObj, ...)`: : returns a list of name-value pairs of information about the driver. *Hint:* Useful entries could include `name`: : the driver name (e.g., `RODBC`, `RPgSQL`); `driver.version`: : version of the driver; `DBI.version`: : the version of the DBI that the driver implements, e.g., `0.1-2`; `client.version`: : of the client DBMS libraries (e.g., version of the `libpq` library in the case of `RPgSQL`); `max.connections`: : maximum number of simultaneous connections; plus any other relevant information about the implementation, for instance, how the driver handles upper/lower case in identifiers. `dbUnloadDriver(driverName)` (optional): : frees all resources (local and remote) used by the driver. Returns a logical to indicate if it succeeded or not. ## Class `DBIConnection` {#sec:DBIConnection} This virtual class encapsulates the connection to a DBMS, and it provides access to dynamic queries, result sets, DBMS session management (transactions), etc. *Note:* Individual drivers are free to implement single or multiple simultaneous connections. The methods defined by the `DBIConnection` class include: `dbConnect(drv, ...)`: : [meth:dbConnect] creates and opens a connection to the database implemented by the driver `drv` (see Section [sec:DBIDriver]). Each driver will define what other arguments are required, e.g., `dbname` or `dsn` for the database name, `user`, and `password`. It returns an object that extends `DBIConnection` in a driver-specific manner (e.g., the MySQL implementation could create an object of class `MySQLConnection` that extends `DBIConnection`). `dbDisconnect(conn, ...)`: : closes the connection, discards all pending work, and frees resources (e.g., memory, sockets). Returns a logical indicating whether it succeeded or not. `dbSendQuery(conn, statement, ...)`: : submits one statement to the DBMS. It returns a `DBIResult` object. This object is needed for fetching data in case the statement generates output (see `fetch` on page ), and it may be used for querying the state of the operation; see `dbGetInfo` and other meta-data methods on page . `dbGetQuery(conn, statement, ...)`: : submit, execute, and extract output in one operation. The resulting object may be a `data.frame` if the `statement` generates output. Otherwise the return value should be a logical indicating whether the query succeeded or not. `dbGetException(conn, ...)`: : returns a list with elements `errNum` and `errMsg` with the status of the last DBMS statement sent on a given connection (this information may also be provided by the `dbGetInfo` meta-data function on the `conn` object. *Hint:* The ANSI SQL-92 defines both a status code and an status message that could be return as members of the list. `dbGetInfo(dbObj, ...)`: : returns a list of name-value pairs describing the state of the connection; it may return one or more meta-data, the actual driver method allows to specify individual pieces of meta-data (e.g., maximum number of open results/cursors). *Hint:* Useful entries could include `dbname`: : the name of the database in use; `db.version`: : the DBMS server version (e.g., “Oracle 8.1.7 on Solaris”; `host`: : host where the database server resides; `user`: : user name; `password`: : password (is this safe?); plus any other arguments related to the connection (e.g., thread id, socket or TCP connection type). `dbListResults(conn, ...)`: : list of `DBIResult` objects currently active on the connection `conn`. May be `NULL` if no result set is active on `conn`. Drivers that implement only one result set per connection could return that one object (no need to wrap it in a list). *Note: The following are convenience methods that simplify the import/export of (mainly) data.frames. The first five methods implement the core methods needed to `attach` remote DBMS to the S search path. (For details, see @data-management:1991 [@database-classes:1999].)* *Hint:* For relational DBMS these methods may be easily implemented using the core DBI methods `dbConnect`, `dbSendQuery`, and `fetch`, due to SQL reflectance (i.e., one easily gets this meta-data by querying the appropriate tables on the RDBMS). `dbListTables(conn, ...)`: : returns a character vector (possibly of zero-length) of object (table) names available on the `conn` connection. `dbReadTable(conn, name, ...)`: : imports the data stored remotely in the table `name` on connection `conn`. Use the field `row.names` as the `row.names` attribute of the output data.frame. Returns a `data.frame`. [Q: should we spell out how row.names should be created? E.g., use a field (with unique values) as row.names? Also, should `dbReadTable` reproduce a data.frame exported with `dbWriteTable`?] `dbWriteTable(conn, name, value, ...)`: : write the object `value` (perhaps after coercing it to data.frame) into the remote object `name` in connection `conn`. Returns a logical indicating whether the operation succeeded or not. `dbExistsTable(conn, name, ...)`: : does remote object `name` exist on `conn`? Returns a logical. `dbRemoveTable(conn, name, ...)`: : removes remote object `name` on connection `conn`. Returns a logical indicating whether the operation succeeded or not. `dbListFields(conn, name, ...)`: : returns a character vector listing the field names of the remote table `name` on connection `conn` (see `dbColumnInfo()` for extracting data type on a table). *Note: The following methods deal with transactions and stored procedures. All these functions are optional.* `dbCommit(conn, ...)`(optional): : commits pending transaction on the connection and returns `TRUE` or `FALSE` depending on whether the operation succeeded or not. `dbRollback(conn, ...)`(optional): : undoes current transaction on the connection and returns `TRUE` or `FALSE` depending on whether the operation succeeded or not. `dbCallProc(conn, storedProc, ...)`(optional): : invokes a stored procedure in the DBMS and returns a `DBIResult` object. [Stored procedures are *not* part of the ANSI SQL-92 standard and vary substantially from one RDBMS to another.] **Deprecated since 2014:** The recommended way of calling a stored procedure is now - `dbGetQuery` if a result set is returned and - `dbExecute` for data manipulation and other cases that do not return a result set. ## Class `DBIResult` {#sec:DBIResult} This virtual class describes the result and state of execution of a DBMS statement (any statement, query or non-query). The result set `res` keeps track of whether the statement produces output for R/S, how many rows were affected by the operation, how many rows have been fetched (if statement is a query), whether there are more rows to fetch, etc. *Note: Individual drivers are free to allow single or multiple active results per connection.* [Q: Should we distinguish between results that return no data from those that return data?] The class `DBIResult` defines the following methods: `fetch(res, n, ...)`: : [meth:fetch] fetches the next `n` elements (rows) from the result set `res` and return them as a data.frame. A value of `n=-1` is interpreted as “return all elements/rows”. `dbClearResult(res, ...)`: : flushes any pending data and frees all resources (local and remote) used by the object `res` on both sides of the connection. Returns a logical indicating success or not. `dbGetInfo(dbObj, ...)`: : returns a name-value list with the state of the result set. *Hint:* Useful entries could include `statement`: : a character string representation of the statement being executed; `rows.affected`: : number of affected records (changed, deleted, inserted, or extracted); `row.count`: : number of rows fetched so far; `has.completed`: : has the statement (query) finished? `is.select`: : a logical describing whether or not the statement generates output; plus any other relevant driver-specific meta-data. `dbColumnInfo(res, ...)`: : produces a data.frame that describes the output of a query. The data.frame should have as many rows as there are output fields in the result set, and each column in the data.frame should describe an aspect of the result set field (field name, type, etc.) *Hint:* The data.frame columns could include `field.name`: : DBMS field label; `field.type`: : DBMS field type (implementation-specific); `data.type`: : corresponding R/S data type, e.g., `integer`; `precision`/`scale`: : (as in ODBC terminology), display width and number of decimal digits, respectively; `nullable`: : whether the corresponding field may contain (DBMS) `NULL` values; plus other driver-specific information. `dbSetDataMappings(flds, ...)`(optional): : defines a conversion between internal DBMS data types and R/S classes. We expect the default mappings (see Section [sec:data-mappings]) to be by far the most common ones, but users that need more control may specify a class generator for individual fields in the result set. [This topic needs further discussion.] *Note: The following are convenience methods that extract information from the result object (they may be implemented by invoking `dbGetInfo` with appropriate arguments).* `dbGetStatement(res, ...)`(optional): : returns the DBMS statement (as a character string) associated with the result `res`. `dbGetRowsAffected(res, ...)`(optional): : returns the number of rows affected by the executed statement (number of records deleted, modified, extracted, etc.) `dbHasCompleted(res, ...)`(optional): : returns a logical that indicates whether the operation has been completed (e.g., are there more records to be fetched?). `dbGetRowCount(res, ...)`(optional): : returns the number of rows fetched so far. # Data Type Mappings {#sec:data-mappings} The data types supported by databases are different than the data types in R and S, but the mapping between the “primitive” types is straightforward: Any of the many fixed and varying length character types are mapped to R/S `character`. Fixed-precision (non-IEEE) numbers are mapped into either doubles (`numeric`) or long (`integer`). Notice that many DBMS do not follow the so-called IEEE arithmetic, so there are potential problems with under/overflows and loss of precision, but given the R/S primitive types we cannot do too much but identify these situations and warn the application (how?). By default dates and date-time objects are mapped to character using the appropriate `TO_CHAR` function in the DBMS (which should take care of any locale information). Some RDBMS support the type `CURRENCY` or `MONEY` which should be mapped to `numeric` (again with potential round off errors). Large objects (character, binary, file, etc.) also need to be mapped. User-defined functions may be specified to do the actual conversion (as has been done in other inter-systems packages [^2]). Specifying user-defined conversion functions still needs to be defined. # Utilities {#sec:utilities} The core DBI implementation should make available to all drivers some common basic utilities. For instance: `dbGetDBIVersion`: : returns the version of the currently attached DBI as a string. `dbDataType(dbObj, obj, ...)`: : returns a string with the (approximately) appropriate data type for the R/S object `obj`. The DBI can implement this following the ANSI-92 standard, but individual drivers may want/need to extend it to make use of DBMS-specific types. `make.db.names(dbObj, snames, ...)`: : maps R/S names (identifiers) to SQL identifiers replacing illegal characters (as `.`) by the legal SQL `_`. `SQLKeywords(dbObj, ...)`: : returns a character vector of SQL keywords (reserved words). The default method returns the list of `.SQL92Keywords`, but drivers should update this vector with the DBMS-specific additional reserved words. `isSQLKeyword(dbObj, name, ...)`: : for each element in the character vector `name` determine whether or not it is an SQL keyword, as reported by the generic function `SQLKeywords`. Returns a logical vector parallel to the input object `name`. # Open Issues and Limitations {#sec:open-issues} There are a number of issues and limitations that the current DBI conscientiously does not address on the interest of simplicity. We do list here the most important ones. Non-SQL: : Is it realistic to attempt to encompass non-relational databases, like HDF5, Berkeley DB, etc.? Security: : allowing users to specify their passwords on R/S scripts may be unacceptable for some applications. We need to consider alternatives where users could store authentication on files (perhaps similar to ODBC’s `odbc.ini`) with more stringent permissions. Exceptions: : the exception mechanism is a bit too simple, and it does not provide for information when problems stem from the DBMS interface itself. For instance, under/overflow or loss of precision as we move numeric data from DBMS to the more limited primitives in R/S. Asynchronous communication: : most DBMS support both synchronous and asynchronous communications, allowing applications to submit a query and proceed while the database server process the query. The application is then notified (or it may need to poll the server) when the query has completed. For large computations, this could be very useful, but the DBI would need to specify how to interrupt the server (if necessary) plus other details. Also, some DBMS require applications to use threads to implement asynchronous communication, something that neither R nor S-Plus currently addresses. SQL scripts: : the DBI only defines how to execute one SQL statement at a time, forcing users to split SQL scripts into individual statements. We need a mechanism by which users can submit SQL scripts that could possibly generate multiple result sets; in this case we may need to introduce new methods to loop over multiple results (similar to Python’s `nextResultSet`). BLOBS/CLOBS: : large objects (both character and binary) present some challenges both to R and S-Plus. It is becoming more common to store images, sounds, and other data types as binary objects in DBMS, some of which can be in principle quite large. The SQL-92 ANSI standard allows up to 2 gigabytes for some of these objects. We need to carefully plan how to deal with binary objects. Transactions: : transaction management is not fully described. Additional methods: : Do we need any additional methods? (e.g., `dbListDatabases(conn)`, `dbListTableIndices(conn, name)`, how do we list all available drivers?) Bind variables: : the interface is heavily biased towards queries, as opposed to general purpose database development. In particular we made no attempt to define “bind variables”; this is a mechanism by which the contents of R/S objects are implicitly moved to the database during SQL execution. For instance, the following embedded SQL statement /* SQL */ SELECT * from emp_table where emp_id = :sampleEmployee would take the vector `sampleEmployee` and iterate over each of its elements to get the result. Perhaps the DBI could at some point in the future implement this feature. # Resources {#sec:resources} The idea of a common interface to databases has been successfully implemented in various environments, for instance: Java’s Database Connectivity (JDBC) ([www.javasoft.com](https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/)). In C through the Open Database Connectivity (ODBC) ([www.unixodbc.org](https://www.unixodbc.org/)). Python’s Database Application Programming Interface ([www.python.org](https://wiki.python.org/moin/DatabaseProgramming)). Perl’s Database Interface ([dbi.perl.org](https://dbi.perl.org)). [^1]: A virtual class allows us to group classes that share some common characteristics, even if their implementations are radically different. [^2]: Duncan Temple Lang has volunteered to port the data conversion code found in R-Java, R-Perl, and R-Python packages to the DBI DBI/inst/doc/DBI-arrow.html0000644000176200001440000006164614561352216015030 0ustar liggesusersUsing DBI with Arrow

Using DBI with Arrow

Kirill Müller

25/12/2023

Who this tutorial is for

This tutorial is for you if you want to leverage Apache Arrow for accessing and manipulating data on databases. See vignette("DBI", package = "DBI") and vignette("DBI-advanced", package = "DBI") for tutorials on accessing data using R’s data frames instead of Arrow’s structures.

Rationale

Apache Arrow is

a cross-language development platform for in-memory analytics,

suitable for large and huge data, with support for out-of-memory operation. Arrow is also a data exchange format, the data types covered by Arrow align well with the data types supported by SQL databases.

DBI 1.2.0 introduced support for Arrow as a format for exchanging data between R and databases. The aim is to:

  • accelerate data retrieval and loading, by using fewer costly data conversions;
  • better support reading and summarizing data from a database that is larger than memory;
  • provide better type fidelity with workflows centered around Arrow.

This allows existing code to be used with Arrow, and it allows new code to be written that is more efficient and more flexible than code that uses R’s data frames.

The interface is built around the {nanoarrow} R package, with nanoarrow::as_nanoarrow_array and nanoarrow::as_nanoarrow_array_stream as fundamental data structures.

New classes and generics

DBI 1.2.0 introduces new classes and generics for working with Arrow data:

  • dbReadTableArrow()
  • dbWriteTableArrow()
  • dbCreateTableArrow()
  • dbAppendTableArrow()
  • dbGetQueryArrow()
  • dbSendQueryArrow()
  • dbBindArrow()
  • dbFetchArrow()
  • dbFetchArrowChunk()
  • DBIResultArrow-class
  • DBIResultArrowDefault-class

Compatibility is important for DBI, and implementing new generics and classes greatly reduces the risk of breaking existing code. The DBI package comes with a fully functional fallback implementation for all existing DBI backends. The fallback is not improving performance, but it allows existing code to be used with Arrow before switching to a backend with native Arrow support. Backends with native support, like the adbi package, implement the new generics and classes for direct support and improved performance.

In the remainder of this tutorial, we will demonstrate the new generics and classes using the RSQLite package. SQLite is an in-memory database, this code does not need a database server to be installed and running.

Prepare

We start by setting up a database connection and creating a table with some data, using the original dbWriteTable() method.

library(DBI)

con <- dbConnect(RSQLite::SQLite())

data <- data.frame(
  a = 1:3,
  b = 4.5,
  c = "five"
)

dbWriteTable(con, "tbl", data)

Read all rows from a table

The dbReadTableArrow() method reads all rows from a table into an Arrow stream, similarly to dbReadTable(). Arrow objects implement the as.data.frame() method, so we can convert the stream to a data frame.

stream <- dbReadTableArrow(con, "tbl")
stream
## <nanoarrow_array_stream struct<a: int32, b: double, c: string>>
##  $ get_schema:function ()  
##  $ get_next  :function (schema = x$get_schema(), validate = TRUE)  
##  $ release   :function ()
as.data.frame(stream)
##   a   b    c
## 1 1 4.5 five
## 2 2 4.5 five
## 3 3 4.5 five

Run queries

The dbGetQueryArrow() method runs a query and returns the result as an Arrow stream. This stream can be turned into an arrow::RecordBatchReader object and processed further, without bringing it into R.

stream <- dbGetQueryArrow(con, "SELECT COUNT(*) AS n FROM tbl WHERE a < 3")
stream
## <nanoarrow_array_stream struct<n: int32>>
##  $ get_schema:function ()  
##  $ get_next  :function (schema = x$get_schema(), validate = TRUE)  
##  $ release   :function ()
path <- tempfile(fileext = ".parquet")
arrow::write_parquet(arrow::as_record_batch_reader(stream), path)
arrow::read_parquet(path)
##   n
## 1 2

Prepared queries

The dbGetQueryArrow() method supports prepared queries, using the params argument which accepts a data frame or a list.

params <- data.frame(a = 3L)
stream <- dbGetQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a", params = params)
as.data.frame(stream)
##   batch a   b    c
## 1     3 1 4.5 five
## 2     3 2 4.5 five
params <- data.frame(a = c(2L, 4L))
# Equivalent to dbBind()
stream <- dbGetQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a", params = params)
as.data.frame(stream)
##   batch a   b    c
## 1     2 1 4.5 five
## 2     4 1 4.5 five
## 3     4 2 4.5 five
## 4     4 3 4.5 five

Manual flow

For the manual flow, use dbSendQueryArrow() to send a query to the database, and dbFetchArrow() to fetch the result. This also allows using the new dbBindArrow() method to bind data in Arrow format to a prepared query. Result objects must be cleared with dbClearResult().

rs <- dbSendQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a")

in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 1L))
dbBindArrow(rs, in_arrow)
as.data.frame(dbFetchArrow(rs))
## [1] batch a     b     c    
## <0 rows> (or 0-length row.names)
in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 2L))
dbBindArrow(rs, in_arrow)
as.data.frame(dbFetchArrow(rs))
##   batch a   b    c
## 1     2 1 4.5 five
in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 3L))
dbBindArrow(rs, in_arrow)
as.data.frame(dbFetchArrow(rs))
##   batch a   b    c
## 1     3 1 4.5 five
## 2     3 2 4.5 five
in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 1:4L))
dbBindArrow(rs, in_arrow)
as.data.frame(dbFetchArrow(rs))
##   batch a   b    c
## 1     2 1 4.5 five
## 2     3 1 4.5 five
## 3     3 2 4.5 five
## 4     4 1 4.5 five
## 5     4 2 4.5 five
## 6     4 3 4.5 five
dbClearResult(rs)

Writing data

Streams returned by dbGetQueryArrow() and dbReadTableArrow() can be written to a table using dbWriteTableArrow().

stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a < 3")
dbWriteTableArrow(con, "tbl_new", stream)
dbReadTable(con, "tbl_new")
##   a   b    c
## 1 1 4.5 five
## 2 2 4.5 five

Appending data

For more control over the writing process, use dbCreateTableArrow() and dbAppendTableArrow().

stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a < 3")
dbCreateTableArrow(con, "tbl_split", stream)
dbAppendTableArrow(con, "tbl_split", stream)
## [1] 2
stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a >= 3")
dbAppendTableArrow(con, "tbl_split", stream)
## [1] 1
dbReadTable(con, "tbl_split")
##   a   b    c
## 1 1 4.5 five
## 2 2 4.5 five
## 3 3 4.5 five

Conclusion

Do not forget to disconnect from the database when done.

dbDisconnect(con)

That concludes the major features of DBI’s new Arrow interface. For more details on the library functions covered in this tutorial see the DBI specification at vignette("spec", package = "DBI"). See the adbi package for a backend with native Arrow support, and nanoarrow and arrow for packages to work with the Arrow format.

DBI/inst/doc/spec.html0000644000176200001440000057110414561352217014230 0ustar liggesusersDBI specification

DBI specification

Kirill Müller

Abstract

The DBI package defines the generic DataBase Interface for R. The connection to individual DBMS is provided by other packages that import DBI (so-called DBI backends). This document formalizes the behavior expected by the methods declared in DBI and implemented by the individual backends. To ensure maximum portability and exchangeability, and to reduce the effort for implementing a new DBI backend, the DBItest package defines a comprehensive set of test cases that test conformance to the DBI specification. This document is derived from comments in the test definitions of the DBItest package. Any extensions or updates to the tests will be reflected in this document.

DBI: R Database Interface

DBI defines an interface for communication between R and relational database management systems. All classes in this package are virtual and need to be extended by the various R/DBMS implementations (so-called DBI backends).

Definition

A DBI backend is an R package which imports the DBI and methods packages. For better or worse, the names of many existing backends start with ‘R’, e.g., RSQLite, RMySQL, RSQLServer; it is up to the backend author to adopt this convention or not.

DBI classes and methods

A backend defines three classes, which are subclasses of DBIDriver, DBIConnection, and DBIResult. The backend provides implementation for all methods of these base classes that are defined but not implemented by DBI. All methods defined in DBI are reexported (so that the package can be used without having to attach DBI), and have an ellipsis ... in their formals for extensibility.

Construction of the DBIDriver object

The backend must support creation of an instance of its DBIDriver subclass with a constructor function. By default, its name is the package name without the leading ‘R’ (if it exists), e.g., SQLite for the RSQLite package. However, backend authors may choose a different name. The constructor must be exported, and it must be a function that is callable without arguments. DBI recommends to define a constructor with an empty argument list.

Examples

RSQLite::SQLite()

Determine the SQL data type of an object

This section describes the behavior of the following method:

dbDataType(dbObj, obj, ...)

Description

Returns an SQL string that describes the SQL data type to be used for an object. The default implementation of this generic determines the SQL type of an R object according to the SQL 92 specification, which may serve as a starting point for driver implementations. DBI also provides an implementation for data.frame which will return a character vector giving the type for each column in the dataframe.

Arguments

dbObj A object inheriting from DBIDriver or DBIConnection
obj An R object whose SQL type we want to determine.
... Other arguments passed on to methods.

Details

The data types supported by databases are different than the data types in R, but the mapping between the primitive types is straightforward:

  • Any of the many fixed and varying length character types are mapped to character vectors

  • Fixed-precision (non-IEEE) numbers are mapped into either numeric or integer vectors.

Notice that many DBMS do not follow IEEE arithmetic, so there are potential problems with under/overflows and loss of precision.

Value

dbDataType() returns the SQL type that corresponds to the obj argument as a non-empty character string. For data frames, a character vector with one element per column is returned.

Failure modes

An error is raised for invalid values for the obj argument such as a NULL value.

Specification

The backend can override the dbDataType() generic for its driver class.

This generic expects an arbitrary object as second argument. To query the values returned by the default implementation, run example(dbDataType, package = "DBI"). If the backend needs to override this generic, it must accept all basic R data types as its second argument, namely logical, integer, numeric, character, dates (see Dates), date-time (see DateTimeClasses), and difftime. If the database supports blobs, this method also must accept lists of raw vectors, and blob::blob objects. As-is objects (i.e., wrapped by I()) must be supported and return the same results as their unwrapped counterparts. The SQL data type for factor and ordered is the same as for character. The behavior for other object types is not specified.

All data types returned by dbDataType() are usable in an SQL statement of the form "CREATE TABLE test (a ...)".

Examples

dbDataType(ANSI(), 1:5)
dbDataType(ANSI(), 1)
dbDataType(ANSI(), TRUE)
dbDataType(ANSI(), Sys.Date())
dbDataType(ANSI(), Sys.time())
dbDataType(ANSI(), Sys.time() - as.POSIXct(Sys.Date()))
dbDataType(ANSI(), c("x", "abc"))
dbDataType(ANSI(), list(raw(10), raw(20)))
dbDataType(ANSI(), I(3))

dbDataType(ANSI(), iris)


con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbDataType(con, 1:5)
dbDataType(con, 1)
dbDataType(con, TRUE)
dbDataType(con, Sys.Date())
dbDataType(con, Sys.time())
dbDataType(con, Sys.time() - as.POSIXct(Sys.Date()))
dbDataType(con, c("x", "abc"))
dbDataType(con, list(raw(10), raw(20)))
dbDataType(con, I(3))

dbDataType(con, iris)

dbDisconnect(con)

Create a connection to a DBMS

This section describes the behavior of the following method:

dbConnect(drv, ...)

Description

Connect to a DBMS going through the appropriate authentication procedure. Some implementations may allow you to have multiple connections open, so you may invoke this function repeatedly assigning its output to different objects. The authentication mechanism is left unspecified, so check the documentation of individual drivers for details. Use dbCanConnect() to check if a connection can be established.

Arguments

drv an object that inherits from DBIDriver, or an existing DBIConnection object (in order to clone an existing connection).
... authentication arguments needed by the DBMS instance; these typically include user, password, host, port, dbname, etc. For details see the appropriate DBIDriver.

Value

dbConnect() returns an S4 object that inherits from DBIConnection. This object is used to communicate with the database engine.

A format() method is defined for the connection object. It returns a string that consists of a single line of text.

Specification

DBI recommends using the following argument names for authentication parameters, with NULL default:

  • user for the user name (default: current user)

  • password for the password

  • host for the host name (default: local connection)

  • port for the port number (default: local connection)

  • dbname for the name of the database on the host, or the database file name

The defaults should provide reasonable behavior, in particular a local connection for host = NULL. For some DBMS (e.g., PostgreSQL), this is different to a TCP/IP connection to localhost.

In addition, DBI supports the bigint argument that governs how 64-bit integer data is returned. The following values are supported:

  • "integer": always return as integer, silently overflow

  • "numeric": always return as numeric, silently round

  • "character": always return the decimal representation as character

  • "integer64": return as a data type that can be coerced using as.integer() (with warning on overflow), as.numeric() and as.character()

Examples

# SQLite only needs a path to the database. (Here, ":memory:" is a special
# path that creates an in-memory database.) Other database drivers
# will require more details (like user, password, host, port, etc.)
con <- dbConnect(RSQLite::SQLite(), ":memory:")
con

dbListTables(con)

dbDisconnect(con)

# Bad, for subtle reasons:
# This code fails when RSQLite isn't loaded yet,
# because dbConnect() doesn't know yet about RSQLite.
dbListTables(con <- dbConnect(RSQLite::SQLite(), ":memory:"))

Disconnect (close) a connection

This section describes the behavior of the following method:

dbDisconnect(conn, ...)

Description

This closes the connection, discards all pending work, and frees resources (e.g., memory, sockets).

Arguments

conn A DBIConnection object, as returned by dbConnect().
... Other parameters passed on to methods.

Value

dbDisconnect() returns TRUE, invisibly.

Failure modes

A warning is issued on garbage collection when a connection has been released without calling dbDisconnect(), but this cannot be tested automatically. A warning is issued immediately when calling dbDisconnect() on an already disconnected or invalid connection.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")
dbDisconnect(con)

Execute a query on a given database connection

This section describes the behavior of the following method:

dbSendQuery(conn, statement, ...)

Description

The dbSendQuery() method only submits and synchronously executes the SQL query to the database engine. It does not extract any records — for that you need to use the dbFetch() method, and then you must call dbClearResult() when you finish fetching the records you need. For interactive use, you should almost always prefer dbGetQuery(). Use dbSendQueryArrow() or dbGetQueryArrow() instead to retrieve the results as an Arrow object.

Arguments

conn A DBIConnection object, as returned by dbConnect().
statement a character string containing SQL.
... Other parameters passed on to methods.

Additional arguments

The following arguments are not part of the dbSendQuery() generic (to improve compatibility across backends) but are part of the DBI specification:

  • params (default: NULL)

  • immediate (default: NULL)

They must be provided as named arguments. See the “Specification” sections for details on their usage.

Specification

No warnings occur under normal conditions. When done, the DBIResult object must be cleared with a call to dbClearResult(). Failure to clear the result set leads to a warning when the connection is closed.

If the backend supports only one open result set per connection, issuing a second query invalidates an already open result set and raises a warning. The newly opened result set is valid and must be cleared with dbClearResult().

The param argument allows passing query parameters, see dbBind() for details.

Specification for the immediate argument

The immediate argument supports distinguishing between “direct” and “prepared” APIs offered by many database drivers. Passing immediate = TRUE leads to immediate execution of the query or statement, via the “direct” API (if supported by the driver). The default NULL means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct immediate argument. Examples for possible behaviors:

  1. DBI backend defaults to immediate = TRUE internally

    1. A query without parameters is passed: query is executed

    2. A query with parameters is passed:

      1. params not given: rejected immediately by the database because of a syntax error in the query, the backend tries immediate = FALSE (and gives a message)

      2. params given: query is executed using immediate = FALSE

  2. DBI backend defaults to immediate = FALSE internally

    1. A query without parameters is passed:

      1. simple query: query is executed

      2. “special” query (such as setting a config options): fails, the backend tries immediate = TRUE (and gives a message)

    2. A query with parameters is passed:

      1. params not given: waiting for parameters via dbBind()

      2. params given: query is executed

Details

This method is for SELECT queries only. Some backends may support data manipulation queries through this method for compatibility reasons. However, callers are strongly encouraged to use dbSendStatement() for data manipulation statements.

The query is submitted to the database server and the DBMS executes it, possibly generating vast amounts of data. Where these data live is driver-specific: some drivers may choose to leave the output on the server and transfer them piecemeal to R, others may transfer all the data to the client – but not necessarily to the memory that R manages. See individual drivers’ dbSendQuery() documentation for details.

Value

dbSendQuery() returns an S4 object that inherits from DBIResult. The result set can be used with dbFetch() to extract records. Once you have finished using a result, make sure to clear it with dbClearResult().

The data retrieval flow

This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames.

Most of this flow, except repeated calling of dbBind() or dbBindArrow(), is implemented by dbGetQuery(), which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendQuery() to create a result set object of class DBIResult.

  2. Optionally, bind query parameters with dbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbColumnInfo() to retrieve the structure of the result set without retrieving actual data.

  4. Use dbFetch() to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards.

  5. Use dbHasCompleted() to tell when you’re done. This method returns TRUE if no more rows are available for fetching.

  6. Repeat the last four steps as necessary.

  7. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

Failure modes

An error is raised when issuing a query over a closed or invalid connection, or if the query is not a non-NA string. An error is also raised if the syntax of the query is invalid and all query parameters are given (by passing the params argument) or the immediate argument is set to TRUE.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars)
rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4")
dbFetch(rs)
dbClearResult(rs)

# Pass one set of values with the param argument:
rs <- dbSendQuery(
  con,
  "SELECT * FROM mtcars WHERE cyl = ?",
  params = list(4L)
)
dbFetch(rs)
dbClearResult(rs)

# Pass multiple sets of values with dbBind():
rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = ?")
dbBind(rs, list(6L))
dbFetch(rs)
dbBind(rs, list(8L))
dbFetch(rs)
dbClearResult(rs)

dbDisconnect(con)

Fetch records from a previously executed query

This section describes the behavior of the following methods:

dbFetch(res, n = -1, ...)

fetch(res, n = -1, ...)

Description

Fetch the next n elements (rows) from the result set and return them as a data.frame.

Arguments

res An object inheriting from DBIResult, created by dbSendQuery().
n maximum number of records to retrieve per fetch. Use n = -1 or n = Inf to retrieve all pending records. Some implementations may recognize other special values.
... Other arguments passed on to methods.

Details

fetch() is provided for compatibility with older DBI clients - for all new code you are strongly encouraged to use dbFetch(). The default implementation for dbFetch() calls fetch() so that it is compatible with existing code. Modern backends should implement for dbFetch() only.

Value

dbFetch() always returns a data.frame with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows. Passing n = NA is supported and returns an arbitrary number of rows (at least one) as specified by the driver, but at most the remaining rows in the result set.

The data retrieval flow

This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames.

Most of this flow, except repeated calling of dbBind() or dbBindArrow(), is implemented by dbGetQuery(), which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendQuery() to create a result set object of class DBIResult.

  2. Optionally, bind query parameters with dbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbColumnInfo() to retrieve the structure of the result set without retrieving actual data.

  4. Use dbFetch() to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards.

  5. Use dbHasCompleted() to tell when you’re done. This method returns TRUE if no more rows are available for fetching.

  6. Repeat the last four steps as necessary.

  7. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

Failure modes

An attempt to fetch from a closed result set raises an error. If the n argument is not an atomic whole number greater or equal to -1 or Inf, an error is raised, but a subsequent call to dbFetch() with proper n argument succeeds.

Calling dbFetch() on a result set from a data manipulation query created by dbSendStatement() can be fetched and return an empty data frame, with a warning.

Specification

Fetching multi-row queries with one or more columns by default returns the entire result. Multi-row queries can also be fetched progressively by passing a whole number (integer or numeric) as the n argument. A value of Inf for the n argument is supported and also returns the full result. If more rows than available are fetched, the result is returned in full without warning. If fewer rows than requested are returned, further fetches will return a data frame with zero rows. If zero rows are fetched, the columns of the data frame are still fully typed. Fetching fewer rows than available is permitted, no warning is issued when clearing the result set.

A column named row_names is treated like any other column.

The column types of the returned data frame depend on the data returned:

  • integer (or coercible to an integer) for integer values between -2^31 and 2^31 - 1, with NA for SQL NULL values

  • numeric for numbers with a fractional component, with NA for SQL NULL values

  • logical for Boolean values (some backends may return an integer); with NA for SQL NULL values

  • character for text, with NA for SQL NULL values

  • lists of raw for blobs with NULL entries for SQL NULL values

  • coercible using as.Date() for dates, with NA for SQL NULL values (also applies to the return value of the SQL function current_date)

  • coercible using hms::as_hms() for times, with NA for SQL NULL values (also applies to the return value of the SQL function current_time)

  • coercible using as.POSIXct() for timestamps, with NA for SQL NULL values (also applies to the return value of the SQL function current_timestamp)

If dates and timestamps are supported by the backend, the following R types are used:

  • Date for dates (also applies to the return value of the SQL function current_date)

  • POSIXct for timestamps (also applies to the return value of the SQL function current_timestamp)

R has no built-in type with lossless support for the full range of 64-bit or larger integers. If 64-bit integers are returned from a query, the following rules apply:

  • Values are returned in a container with support for the full range of valid 64-bit values (such as the integer64 class of the bit64 package)

  • Coercion to numeric always returns a number that is as close as possible to the true value

  • Loss of precision when converting to numeric gives a warning

  • Conversion to character always returns a lossless decimal representation of the data

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars)

# Fetch all results
rs <- dbSendQuery(con, "SELECT * FROM mtcars WHERE cyl = 4")
dbFetch(rs)
dbClearResult(rs)

# Fetch in chunks
rs <- dbSendQuery(con, "SELECT * FROM mtcars")
while (!dbHasCompleted(rs)) {
  chunk <- dbFetch(rs, 10)
  print(nrow(chunk))
}

dbClearResult(rs)
dbDisconnect(con)

Clear a result set

This section describes the behavior of the following method:

dbClearResult(res, ...)

Description

Frees all resources (local and remote) associated with a result set. This step is mandatory for all objects obtained by calling dbSendQuery() or dbSendStatement().

Arguments

res An object inheriting from DBIResult.
... Other arguments passed on to methods.

Value

dbClearResult() returns TRUE, invisibly, for result sets obtained from dbSendQuery(), dbSendStatement(), or dbSendQueryArrow(),

The data retrieval flow

This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames.

Most of this flow, except repeated calling of dbBind() or dbBindArrow(), is implemented by dbGetQuery(), which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendQuery() to create a result set object of class DBIResult.

  2. Optionally, bind query parameters with dbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbColumnInfo() to retrieve the structure of the result set without retrieving actual data.

  4. Use dbFetch() to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards.

  5. Use dbHasCompleted() to tell when you’re done. This method returns TRUE if no more rows are available for fetching.

  6. Repeat the last four steps as necessary.

  7. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

The command execution flow

This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of dbBindArrow(), is implemented by dbExecute(), which should be sufficient for non-parameterized queries. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendStatement() to create a result set object of class DBIResult. For some queries you need to pass immediate = TRUE.

  2. Optionally, bind query parameters withdbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbGetRowsAffected() to retrieve the number of rows affected by the query.

  4. Repeat the last two steps as necessary.

  5. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

Failure modes

An attempt to close an already closed result set issues a warning for dbSendQuery(), dbSendStatement(), and dbSendQueryArrow(),

Specification

dbClearResult() frees all resources associated with retrieving the result of a query or update operation. The DBI backend can expect a call to dbClearResult() for each dbSendQuery() or dbSendStatement() call.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

rs <- dbSendQuery(con, "SELECT 1")
print(dbFetch(rs))

dbClearResult(rs)
dbDisconnect(con)

Bind values to a parameterized/prepared statement

This section describes the behavior of the following methods:

dbBind(res, params, ...)

dbBindArrow(res, params, ...)

Description

For parametrized or prepared statements, the dbSendQuery(), dbSendQueryArrow(), and dbSendStatement() functions can be called with statements that contain placeholders for values. The dbBind() and dbBindArrow() functions bind these placeholders to actual values, and are intended to be called on the result set before calling dbFetch() or dbFetchArrow(). The values are passed to dbBind() as lists or data frames, and to dbBindArrow() as a stream created by nanoarrow::as_nanoarrow_array_stream().

lifecycle: experimental lifecycle experimental

dbBindArrow() is experimental, as are the other ⁠*Arrow⁠ functions. dbSendQuery() is compatible with dbBindArrow(), and dbSendQueryArrow() is compatible with dbBind().

Arguments

res An object inheriting from DBIResult.
params For dbBind(), a list of values, named or unnamed, or a data frame, with one element/column per query parameter. For dbBindArrow(), values as a nanoarrow stream, with one column per query parameter.
... Other arguments passed on to methods.

Details

DBI supports parametrized (or prepared) queries and statements via the dbBind() and dbBindArrow() generics. Parametrized queries are different from normal queries in that they allow an arbitrary number of placeholders, which are later substituted by actual values. Parametrized queries (and statements) serve two purposes:

  • The same query can be executed more than once with different values. The DBMS may cache intermediate information for the query, such as the execution plan, and execute it faster.

  • Separation of query syntax and parameters protects against SQL injection.

The placeholder format is currently not specified by DBI; in the future, a uniform placeholder syntax may be supported. Consult the backend documentation for the supported formats. For automated testing, backend authors specify the placeholder syntax with the placeholder_pattern tweak. Known examples are:

  • ⁠?⁠ (positional matching in order of appearance) in RMariaDB and RSQLite

  • ⁠\$1⁠ (positional matching by index) in RPostgres and RSQLite

  • ⁠:name⁠ and ⁠\$name⁠ (named matching) in RSQLite

Value

dbBind() returns the result set, invisibly, for queries issued by dbSendQuery() or dbSendQueryArrow() and also for data manipulation statements issued by dbSendStatement().

The data retrieval flow

This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames.

Most of this flow, except repeated calling of dbBind() or dbBindArrow(), is implemented by dbGetQuery(), which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendQuery() to create a result set object of class DBIResult.

  2. Optionally, bind query parameters with dbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbColumnInfo() to retrieve the structure of the result set without retrieving actual data.

  4. Use dbFetch() to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards.

  5. Use dbHasCompleted() to tell when you’re done. This method returns TRUE if no more rows are available for fetching.

  6. Repeat the last four steps as necessary.

  7. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

The data retrieval flow for Arrow streams

This section gives a complete overview over the flow for the execution of queries that return tabular data as an Arrow stream.

Most of this flow, except repeated calling of dbBindArrow() or dbBind(), is implemented by dbGetQueryArrow(), which should be sufficient unless you have a parameterized query that you want to reuse. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendQueryArrow() to create a result set object of class DBIResultArrow.

  2. Optionally, bind query parameters with dbBindArrow() or dbBind(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Use dbFetchArrow() to get a data stream.

  4. Repeat the last two steps as necessary.

  5. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

The command execution flow

This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of dbBindArrow(), is implemented by dbExecute(), which should be sufficient for non-parameterized queries. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendStatement() to create a result set object of class DBIResult. For some queries you need to pass immediate = TRUE.

  2. Optionally, bind query parameters withdbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbGetRowsAffected() to retrieve the number of rows affected by the query.

  4. Repeat the last two steps as necessary.

  5. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

Failure modes

Calling dbBind() for a query without parameters raises an error.

Binding too many or not enough values, or parameters with wrong names or unequal length, also raises an error. If the placeholders in the query are named, all parameter values must have names (which must not be empty or NA), and vice versa, otherwise an error is raised. The behavior for mixing placeholders of different types (in particular mixing positional and named placeholders) is not specified.

Calling dbBind() on a result set already cleared by dbClearResult() also raises an error.

Specification

DBI clients execute parametrized statements as follows:

  1. Call dbSendQuery(), dbSendQueryArrow() or dbSendStatement() with a query or statement that contains placeholders, store the returned DBIResult object in a variable. Mixing placeholders (in particular, named and unnamed ones) is not recommended. It is good practice to register a call to dbClearResult() via on.exit() right after calling dbSendQuery() or dbSendStatement() (see the last enumeration item). Until dbBind() or dbBindArrow() have been called, the returned result set object has the following behavior:

    • dbFetch() raises an error (for dbSendQuery() and dbSendQueryArrow())

    • dbGetRowCount() returns zero (for dbSendQuery() and dbSendQueryArrow())

    • dbGetRowsAffected() returns an integer NA (for dbSendStatement())

    • dbIsValid() returns TRUE

    • dbHasCompleted() returns FALSE

  2. Call dbBind() or dbBindArrow():

    • For dbBind(), the params argument must be a list where all elements have the same lengths and contain values supported by the backend. A data.frame is internally stored as such a list.

    • For dbBindArrow(), the params argument must be a nanoarrow array stream, with one column per query parameter.

  3. Retrieve the data or the number of affected rows from the DBIResult object.

    • For queries issued by dbSendQuery() or dbSendQueryArrow(), call dbFetch().

    • For statements issued by dbSendStatements(), call dbGetRowsAffected(). (Execution begins immediately after the dbBind() call, the statement is processed entirely before the function returns.)

  4. Repeat 2. and 3. as necessary.

  5. Close the result set via dbClearResult().

The elements of the params argument do not need to be scalars, vectors of arbitrary length (including length 0) are supported. For queries, calling dbFetch() binding such parameters returns concatenated results, equivalent to binding and fetching for each set of values and connecting via rbind(). For data manipulation statements, dbGetRowsAffected() returns the total number of rows affected if binding non-scalar parameters. dbBind() also accepts repeated calls on the same result set for both queries and data manipulation statements, even if no results are fetched between calls to dbBind(), for both queries and data manipulation statements.

If the placeholders in the query are named, their order in the params argument is not important.

At least the following data types are accepted on input (including NA):

  • integer

  • numeric

  • logical for Boolean values

  • character (also with special characters such as spaces, newlines, quotes, and backslashes)

  • factor (bound as character, with warning)

  • Date (also when stored internally as integer)

  • POSIXct timestamps

  • POSIXlt timestamps

  • difftime values (also with units other than seconds and with the value stored as integer)

  • lists of raw for blobs (with NULL entries for SQL NULL values)

  • objects of type blob::blob

Examples

# Data frame flow:
con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "iris", iris)

# Using the same query for different values
iris_result <- dbSendQuery(con, "SELECT * FROM iris WHERE [Petal.Width] > ?")
dbBind(iris_result, list(2.3))
dbFetch(iris_result)
dbBind(iris_result, list(3))
dbFetch(iris_result)
dbClearResult(iris_result)

# Executing the same statement with different values at once
iris_result <- dbSendStatement(con, "DELETE FROM iris WHERE [Species] = \$species")
dbBind(iris_result, list(species = c("setosa", "versicolor", "unknown")))
dbGetRowsAffected(iris_result)
dbClearResult(iris_result)

nrow(dbReadTable(con, "iris"))

dbDisconnect(con)



# Arrow flow:
con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "iris", iris)

# Using the same query for different values
iris_result <- dbSendQueryArrow(con, "SELECT * FROM iris WHERE [Petal.Width] > ?")
dbBindArrow(
  iris_result,
  nanoarrow::as_nanoarrow_array_stream(data.frame(2.3, fix.empty.names = FALSE))
)
as.data.frame(dbFetchArrow(iris_result))
dbBindArrow(
  iris_result,
  nanoarrow::as_nanoarrow_array_stream(data.frame(3, fix.empty.names = FALSE))
)
as.data.frame(dbFetchArrow(iris_result))
dbClearResult(iris_result)

# Executing the same statement with different values at once
iris_result <- dbSendStatement(con, "DELETE FROM iris WHERE [Species] = \$species")
dbBindArrow(iris_result, nanoarrow::as_nanoarrow_array_stream(data.frame(
  species = c("setosa", "versicolor", "unknown")
)))
dbGetRowsAffected(iris_result)
dbClearResult(iris_result)

nrow(dbReadTable(con, "iris"))

dbDisconnect(con)

Retrieve results from a query

This section describes the behavior of the following method:

dbGetQuery(conn, statement, ...)

Description

Returns the result of a query as a data frame. dbGetQuery() comes with a default implementation (which should work with most backends) that calls dbSendQuery(), then dbFetch(), ensuring that the result is always freed by dbClearResult(). For retrieving chunked/paged results or for passing query parameters, see dbSendQuery(), in particular the “The data retrieval flow” section. For retrieving results as an Arrow object, see dbGetQueryArrow().

Arguments

conn A DBIConnection object, as returned by dbConnect().
statement a character string containing SQL.
... Other parameters passed on to methods.

Additional arguments

The following arguments are not part of the dbGetQuery() generic (to improve compatibility across backends) but are part of the DBI specification:

  • n (default: -1)

  • params (default: NULL)

  • immediate (default: NULL)

They must be provided as named arguments. See the “Specification” and “Value” sections for details on their usage.

Specification

A column named row_names is treated like any other column.

The n argument specifies the number of rows to be fetched. If omitted, fetching multi-row queries with one or more columns returns the entire result. A value of Inf for the n argument is supported and also returns the full result. If more rows than available are fetched (by passing a too large value for n), the result is returned in full without warning. If zero rows are requested, the columns of the data frame are still fully typed. Fetching fewer rows than available is permitted, no warning is issued.

The param argument allows passing query parameters, see dbBind() for details.

Specification for the immediate argument

The immediate argument supports distinguishing between “direct” and “prepared” APIs offered by many database drivers. Passing immediate = TRUE leads to immediate execution of the query or statement, via the “direct” API (if supported by the driver). The default NULL means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct immediate argument. Examples for possible behaviors:

  1. DBI backend defaults to immediate = TRUE internally

    1. A query without parameters is passed: query is executed

    2. A query with parameters is passed:

      1. params not given: rejected immediately by the database because of a syntax error in the query, the backend tries immediate = FALSE (and gives a message)

      2. params given: query is executed using immediate = FALSE

  2. DBI backend defaults to immediate = FALSE internally

    1. A query without parameters is passed:

      1. simple query: query is executed

      2. “special” query (such as setting a config options): fails, the backend tries immediate = TRUE (and gives a message)

    2. A query with parameters is passed:

      1. params not given: waiting for parameters via dbBind()

      2. params given: query is executed

Details

This method is for SELECT queries only (incl. other SQL statements that return a SELECT-alike result, e.g., execution of a stored procedure or data manipulation queries like ⁠INSERT INTO ... RETURNING ...⁠). To execute a stored procedure that does not return a result set, use dbExecute().

Some backends may support data manipulation statements through this method for compatibility reasons. However, callers are strongly advised to use dbExecute() for data manipulation statements.

Value

dbGetQuery() always returns a data.frame, with as many rows as records were fetched and as many columns as fields in the result set, even if the result is a single value or has one or zero rows.

Implementation notes

Subclasses should override this method only if they provide some sort of performance optimization.

Failure modes

An error is raised when issuing a query over a closed or invalid connection, if the syntax of the query is invalid, or if the query is not a non-NA string. If the n argument is not an atomic whole number greater or equal to -1 or Inf, an error is raised, but a subsequent call to dbGetQuery() with proper n argument succeeds.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars)
dbGetQuery(con, "SELECT * FROM mtcars")
dbGetQuery(con, "SELECT * FROM mtcars", n = 6)

# Pass values using the param argument:
# (This query runs eight times, once for each different
# parameter. The resulting rows are combined into a single
# data frame.)
dbGetQuery(
  con,
  "SELECT COUNT(*) FROM mtcars WHERE cyl = ?",
  params = list(1:8)
)

dbDisconnect(con)

Execute a data manipulation statement on a given database connection

This section describes the behavior of the following method:

dbSendStatement(conn, statement, ...)

Description

The dbSendStatement() method only submits and synchronously executes the SQL data manipulation statement (e.g., UPDATE, DELETE, ⁠INSERT INTO⁠, ⁠DROP TABLE⁠, …) to the database engine. To query the number of affected rows, call dbGetRowsAffected() on the returned result object. You must also call dbClearResult() after that. For interactive use, you should almost always prefer dbExecute().

Arguments

conn A DBIConnection object, as returned by dbConnect().
statement a character string containing SQL.
... Other parameters passed on to methods.

Additional arguments

The following arguments are not part of the dbSendStatement() generic (to improve compatibility across backends) but are part of the DBI specification:

  • params (default: NULL)

  • immediate (default: NULL)

They must be provided as named arguments. See the “Specification” sections for details on their usage.

Specification

No warnings occur under normal conditions. When done, the DBIResult object must be cleared with a call to dbClearResult(). Failure to clear the result set leads to a warning when the connection is closed. If the backend supports only one open result set per connection, issuing a second query invalidates an already open result set and raises a warning. The newly opened result set is valid and must be cleared with dbClearResult().

The param argument allows passing query parameters, see dbBind() for details.

Specification for the immediate argument

The immediate argument supports distinguishing between “direct” and “prepared” APIs offered by many database drivers. Passing immediate = TRUE leads to immediate execution of the query or statement, via the “direct” API (if supported by the driver). The default NULL means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct immediate argument. Examples for possible behaviors:

  1. DBI backend defaults to immediate = TRUE internally

    1. A query without parameters is passed: query is executed

    2. A query with parameters is passed:

      1. params not given: rejected immediately by the database because of a syntax error in the query, the backend tries immediate = FALSE (and gives a message)

      2. params given: query is executed using immediate = FALSE

  2. DBI backend defaults to immediate = FALSE internally

    1. A query without parameters is passed:

      1. simple query: query is executed

      2. “special” query (such as setting a config options): fails, the backend tries immediate = TRUE (and gives a message)

    2. A query with parameters is passed:

      1. params not given: waiting for parameters via dbBind()

      2. params given: query is executed

Details

dbSendStatement() comes with a default implementation that simply forwards to dbSendQuery(), to support backends that only implement the latter.

Value

dbSendStatement() returns an S4 object that inherits from DBIResult. The result set can be used with dbGetRowsAffected() to determine the number of rows affected by the query. Once you have finished using a result, make sure to clear it with dbClearResult().

The command execution flow

This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of dbBindArrow(), is implemented by dbExecute(), which should be sufficient for non-parameterized queries. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendStatement() to create a result set object of class DBIResult. For some queries you need to pass immediate = TRUE.

  2. Optionally, bind query parameters withdbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbGetRowsAffected() to retrieve the number of rows affected by the query.

  4. Repeat the last two steps as necessary.

  5. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

Failure modes

An error is raised when issuing a statement over a closed or invalid connection, or if the statement is not a non-NA string. An error is also raised if the syntax of the query is invalid and all query parameters are given (by passing the params argument) or the immediate argument is set to TRUE.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "cars", head(cars, 3))

rs <- dbSendStatement(
  con,
  "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)"
)
dbHasCompleted(rs)
dbGetRowsAffected(rs)
dbClearResult(rs)
dbReadTable(con, "cars")   # there are now 6 rows

# Pass one set of values directly using the param argument:
rs <- dbSendStatement(
  con,
  "INSERT INTO cars (speed, dist) VALUES (?, ?)",
  params = list(4L, 5L)
)
dbClearResult(rs)

# Pass multiple sets of values using dbBind():
rs <- dbSendStatement(
  con,
  "INSERT INTO cars (speed, dist) VALUES (?, ?)"
)
dbBind(rs, list(5:6, 6:7))
dbBind(rs, list(7L, 8L))
dbClearResult(rs)
dbReadTable(con, "cars")   # there are now 10 rows

dbDisconnect(con)

Change database state

This section describes the behavior of the following method:

dbExecute(conn, statement, ...)

Description

Executes a statement and returns the number of rows affected. dbExecute() comes with a default implementation (which should work with most backends) that calls dbSendStatement(), then dbGetRowsAffected(), ensuring that the result is always freed by dbClearResult(). For passing query parameters, see dbBind(), in particular the “The command execution flow” section.

Arguments

conn A DBIConnection object, as returned by dbConnect().
statement a character string containing SQL.
... Other parameters passed on to methods.

Additional arguments

The following arguments are not part of the dbExecute() generic (to improve compatibility across backends) but are part of the DBI specification:

  • params (default: NULL)

  • immediate (default: NULL)

They must be provided as named arguments. See the “Specification” sections for details on their usage.

Specification

The param argument allows passing query parameters, see dbBind() for details.

Specification for the immediate argument

The immediate argument supports distinguishing between “direct” and “prepared” APIs offered by many database drivers. Passing immediate = TRUE leads to immediate execution of the query or statement, via the “direct” API (if supported by the driver). The default NULL means that the backend should choose whatever API makes the most sense for the database, and (if relevant) tries the other API if the first attempt fails. A successful second attempt should result in a message that suggests passing the correct immediate argument. Examples for possible behaviors:

  1. DBI backend defaults to immediate = TRUE internally

    1. A query without parameters is passed: query is executed

    2. A query with parameters is passed:

      1. params not given: rejected immediately by the database because of a syntax error in the query, the backend tries immediate = FALSE (and gives a message)

      2. params given: query is executed using immediate = FALSE

  2. DBI backend defaults to immediate = FALSE internally

    1. A query without parameters is passed:

      1. simple query: query is executed

      2. “special” query (such as setting a config options): fails, the backend tries immediate = TRUE (and gives a message)

    2. A query with parameters is passed:

      1. params not given: waiting for parameters via dbBind()

      2. params given: query is executed

Details

You can also use dbExecute() to call a stored procedure that performs data manipulation or other actions that do not return a result set. To execute a stored procedure that returns a result set, or a data manipulation query that also returns a result set such as ⁠INSERT INTO ... RETURNING ...⁠, use dbGetQuery() instead.

Value

dbExecute() always returns a scalar numeric that specifies the number of rows affected by the statement.

Implementation notes

Subclasses should override this method only if they provide some sort of performance optimization.

Failure modes

An error is raised when issuing a statement over a closed or invalid connection, if the syntax of the statement is invalid, or if the statement is not a non-NA string.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "cars", head(cars, 3))
dbReadTable(con, "cars")   # there are 3 rows
dbExecute(
  con,
  "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)"
)
dbReadTable(con, "cars")   # there are now 6 rows

# Pass values using the param argument:
dbExecute(
  con,
  "INSERT INTO cars (speed, dist) VALUES (?, ?)",
  params = list(4:7, 5:8)
)
dbReadTable(con, "cars")   # there are now 10 rows

dbDisconnect(con)

Quote literal strings

This section describes the behavior of the following method:

dbQuoteString(conn, x, ...)

Description

Call this method to generate a string that is suitable for use in a query as a string literal, to make sure that you generate valid SQL and protect against SQL injection attacks.

Arguments

conn A DBIConnection object, as returned by dbConnect().
x A character vector to quote as string.
... Other arguments passed on to methods.

Value

dbQuoteString() returns an object that can be coerced to character, of the same length as the input. For an empty character vector this function returns a length-0 object.

When passing the returned object again to dbQuoteString() as x argument, it is returned unchanged. Passing objects of class SQL should also return them unchanged. (For backends it may be most convenient to return SQL objects to achieve this behavior, but this is not required.)

Failure modes

Passing a numeric, integer, logical, or raw vector, or a list for the x argument raises an error.

Specification

The returned expression can be used in a ⁠SELECT ...⁠ query, and for any scalar character x the value of dbGetQuery(paste0("SELECT ", dbQuoteString(x)))[[1]] must be identical to x, even if x contains spaces, tabs, quotes (single or double), backticks, or newlines (in any combination) or is itself the result of a dbQuoteString() call coerced back to character (even repeatedly). If x is NA, the result must merely satisfy is.na(). The strings "NA" or "NULL" are not treated specially.

NA should be translated to an unquoted SQL NULL, so that the query ⁠SELECT * FROM (SELECT 1) a WHERE ... IS NULL⁠ returns one row.

Examples

# Quoting ensures that arbitrary input is safe for use in a query
name <- "Robert'); DROP TABLE Students;--"
dbQuoteString(ANSI(), name)

# NAs become NULL
dbQuoteString(ANSI(), c("x", NA))

# SQL vectors are always passed through as is
var_name <- SQL("select")
var_name
dbQuoteString(ANSI(), var_name)

# This mechanism is used to prevent double escaping
dbQuoteString(ANSI(), dbQuoteString(ANSI(), name))

Quote identifiers

This section describes the behavior of the following method:

dbQuoteIdentifier(conn, x, ...)

Description

Call this method to generate a string that is suitable for use in a query as a column or table name, to make sure that you generate valid SQL and protect against SQL injection attacks. The inverse operation is dbUnquoteIdentifier().

Arguments

conn A DBIConnection object, as returned by dbConnect().
x A character vector, SQL or Id object to quote as identifier.
... Other arguments passed on to methods.

Value

dbQuoteIdentifier() returns an object that can be coerced to character, of the same length as the input. For an empty character vector this function returns a length-0 object. The names of the input argument are preserved in the output. When passing the returned object again to dbQuoteIdentifier() as x argument, it is returned unchanged. Passing objects of class SQL should also return them unchanged. (For backends it may be most convenient to return SQL objects to achieve this behavior, but this is not required.)

Failure modes

An error is raised if the input contains NA, but not for an empty string.

Specification

Calling dbGetQuery() for a query of the format ⁠SELECT 1 AS ...⁠ returns a data frame with the identifier, unquoted, as column name. Quoted identifiers can be used as table and column names in SQL queries, in particular in queries like ⁠SELECT 1 AS ...⁠ and ⁠SELECT * FROM (SELECT 1) ...⁠. The method must use a quoting mechanism that is unambiguously different from the quoting mechanism used for strings, so that a query like ⁠SELECT ... FROM (SELECT 1 AS ...)⁠ throws an error if the column names do not match.

The method can quote column names that contain special characters such as a space, a dot, a comma, or quotes used to mark strings or identifiers, if the database supports this. In any case, checking the validity of the identifier should be performed only when executing a query, and not by dbQuoteIdentifier().

Examples

# Quoting ensures that arbitrary input is safe for use in a query
name <- "Robert'); DROP TABLE Students;--"
dbQuoteIdentifier(ANSI(), name)

# Use Id() to specify other components such as the schema
id_name <- Id(schema = "schema_name", table = "table_name")
id_name
dbQuoteIdentifier(ANSI(), id_name)

# SQL vectors are always passed through as is
var_name <- SQL("select")
var_name
dbQuoteIdentifier(ANSI(), var_name)

# This mechanism is used to prevent double escaping
dbQuoteIdentifier(ANSI(), dbQuoteIdentifier(ANSI(), name))

Read database tables as data frames

This section describes the behavior of the following method:

dbReadTable(conn, name, ...)

Description

Reads a database table to a data frame, optionally converting a column to row names and converting the column names to valid R identifiers. Use dbReadTableArrow() instead to obtain an Arrow object.

Arguments

conn

A DBIConnection object, as returned by dbConnect().

name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. “table_name”,

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = “my_schema”, table = “table_name”)

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL(‘“my_schema”.”table_name”’)

…

Other parameters passed on to methods.

Additional arguments

The following arguments are not part of the dbReadTable() generic (to improve compatibility across backends) but are part of the DBI specification:

  • row.names (default: FALSE)

  • check.names

They must be provided as named arguments. See the “Value” section 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: dbReadTable() will do the quoting, perhaps by calling dbQuoteIdentifier(conn, x = name)

  • If the result of a call to dbQuoteIdentifier(): no more quoting is done

Details

This function returns a data frame. Use dbReadTableArrow() to obtain an Arrow object.

Value

dbReadTable() returns a data frame that contains the complete data from the remote table, effectively the result of calling dbGetQuery() with ⁠SELECT * FROM <name>⁠.

An empty table is returned as a data frame with zero rows.

The presence of rownames depends on the row.names argument, see sqlColumnToRownames() for details:

  • If FALSE or NULL, the returned data frame doesn’t have row names.

  • If TRUE, a column named “row_names” is converted to row names.

  • If NA, a column named “row_names” is converted to row names if it exists, otherwise no translation occurs.

  • If a string, this specifies the name of the column in the remote table that contains the row names.

The default is row.names = FALSE.

If the database supports identifiers with special characters, the columns in the returned data frame are converted to valid R identifiers if the check.names argument is TRUE, If check.names = FALSE, the returned table has non-syntactic column names without quotes.

Failure modes

An error is raised if the table does not exist.

An error is raised if row.names is TRUE and no “row_names” column exists,

An error is raised if row.names is set to a string and no corresponding column exists.

An error is raised when calling this method for a closed or invalid connection. An error is raised if name cannot be processed with dbQuoteIdentifier() or if this results in a non-scalar. Unsupported values for row.names and check.names (non-scalars, unsupported data types, NA for check.names) also raise an error.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars[1:10, ])
dbReadTable(con, "mtcars")

dbDisconnect(con)

Copy data frames to database tables

This section describes the behavior of the following method:

dbWriteTable(conn, name, value, ...)

Description

Writes, overwrites or appends a data frame to a database table, optionally converting row names to a column and specifying SQL data types for fields.

Arguments

conn

A DBIConnection object, as returned by dbConnect().

name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. “table_name”,

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = “my_schema”, table = “table_name”)

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL(‘“my_schema”.”table_name”’)

value

A data.frame (or coercible to data.frame).

…

Other parameters passed on to methods.

Additional arguments

The following arguments are not part of the dbWriteTable() generic (to improve compatibility across backends) but are part of the DBI specification:

  • row.names (default: FALSE)

  • overwrite (default: FALSE)

  • append (default: FALSE)

  • field.types (default: NULL)

  • 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: dbWriteTable() will do the quoting, perhaps by calling dbQuoteIdentifier(conn, x = name)

  • If the result of a call to dbQuoteIdentifier(): no more quoting is done

The value argument must be a data frame with a subset of the columns of the existing table if append = TRUE. The order of the columns does not matter with append = TRUE.

If the overwrite argument is TRUE, an existing table of the same name will be overwritten. This argument doesn’t change behavior if the table does not exist yet.

If the append argument is TRUE, the rows in an existing table are preserved, and the new data are appended. If the table doesn’t exist yet, it is created.

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, spaces, and other special characters such as newlines and tabs, can also be used in the data, and, if the database supports non-syntactic identifiers, also for table names and column names.

The following data types must be supported at least, and be read identically with dbReadTable():

  • integer

  • numeric (the behavior for Inf and NaN is not specified)

  • logical

  • NA as NULL

  • 64-bit values (using "bigint" as field type); the result can be

    • converted to a numeric, which may lose precision,

    • converted a character vector, which gives the full decimal representation

    • written to another table and read again unchanged

  • character (in both UTF-8 and native encodings), supporting empty strings before and after a non-empty string

  • factor (returned as character)

  • list of raw (if supported by the database)

  • objects of type blob::blob (if supported by the database)

  • date (if supported by the database; returned as Date), also for dates prior to 1970 or 1900 or after 2038

  • time (if supported by the database; returned as objects that inherit from difftime)

  • timestamp (if supported by the database; returned as POSIXct respecting the time zone but not necessarily preserving the input time zone), also for timestamps prior to 1970 or 1900 or after 2038 respecting the time zone but not necessarily preserving the input time zone)

Mixing column types in the same table is supported.

The field.types argument must be a named character vector with at most one entry for each column. It indicates the SQL data type to be used for a new column. If a column is missed from field.types, the type is inferred from the input data with dbDataType().

The interpretation of rownames depends on the row.names argument, see sqlRownamesToColumn() for details:

  • If FALSE or NULL, row names are ignored.

  • If TRUE, row names are converted to a column named “row_names”, even if the input data frame only has natural row names from 1 to nrow(...).

  • If NA, a column named “row_names” is created if the data has custom row names, no extra column is created in the case of natural row names.

  • If a string, this specifies the name of the column in the remote table that contains the row names, even if the input data frame only has natural row names.

The default is row.names = FALSE.

Details

This function expects a data frame. Use dbWriteTableArrow() to write an Arrow object.

This function is useful if you want to create and load a table at the same time. Use dbAppendTable() or dbAppendTableArrow() for appending data to an existing table, dbCreateTable() or dbCreateTableArrow() for creating a table, and dbExistsTable() and dbRemoveTable() for overwriting tables.

DBI only standardizes writing data frames with dbWriteTable(). Some backends might implement methods that can consume CSV files or other data formats. For details, see the documentation for the individual methods.

Value

dbWriteTable() returns TRUE, invisibly.

Failure modes

If the table exists, and both append and overwrite arguments are unset, or append = TRUE and the data frame with the new data has different column names, 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 dbQuoteIdentifier() or if this results in a non-scalar. Invalid values for the additional arguments row.names, overwrite, append, field.types, and temporary (non-scalars, unsupported data types, NA, incompatible values, duplicate or missing names, incompatible columns) also raise an error.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars[1:5, ])
dbReadTable(con, "mtcars")

dbWriteTable(con, "mtcars", mtcars[6:10, ], append = TRUE)
dbReadTable(con, "mtcars")

dbWriteTable(con, "mtcars", mtcars[1:10, ], overwrite = TRUE)
dbReadTable(con, "mtcars")

# No row names
dbWriteTable(con, "mtcars", mtcars[1:10, ], overwrite = TRUE, row.names = FALSE)
dbReadTable(con, "mtcars")

List remote tables

This section describes the behavior of the following method:

dbListTables(conn, ...)

Description

Returns the unquoted names of remote tables accessible through this connection. This should include views and temporary objects, but not all database backends (in particular RMariaDB and RMySQL) support this.

Arguments

conn A DBIConnection object, as returned by dbConnect().
... Other parameters passed on to methods.

Value

dbListTables() returns a character vector that enumerates all tables and views in the database. Tables added with dbWriteTable() are part of the list. As soon a table is removed from the database, it is also removed from the list of database tables.

The same applies to temporary tables if supported by the database.

The returned names are suitable for quoting with dbQuoteIdentifier().

Failure modes

An error is raised when calling this method for a closed or invalid connection.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbListTables(con)
dbWriteTable(con, "mtcars", mtcars)
dbListTables(con)

dbDisconnect(con)

Does a table exist?

This section describes the behavior of the following method:

dbExistsTable(conn, name, ...)

Description

Returns if a table given by name exists in the database.

Arguments

conn

A DBIConnection object, as returned by dbConnect().

name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. “table_name”,

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = “my_schema”, table = “table_name”)

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL(‘“my_schema”.”table_name”’)

…

Other parameters passed on to methods.

Value

dbExistsTable() returns a logical scalar, TRUE if the table or view specified by the name argument exists, FALSE otherwise.

This includes temporary tables if supported by the database.

Failure modes

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 dbQuoteIdentifier() or if this results in a non-scalar.

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: dbExistsTable() will do the quoting, perhaps by calling dbQuoteIdentifier(conn, x = name)

  • If the result of a call to dbQuoteIdentifier(): no more quoting is done

For all tables listed by dbListTables(), dbExistsTable() returns TRUE.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbExistsTable(con, "iris")
dbWriteTable(con, "iris", iris)
dbExistsTable(con, "iris")

dbDisconnect(con)

Remove a table from the database

This section describes the behavior of the following method:

dbRemoveTable(conn, name, ...)

Description

Remove a remote table (e.g., created by dbWriteTable()) from the database.

Arguments

conn

A DBIConnection object, as returned by dbConnect().

name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. “table_name”,

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = “my_schema”, table = “table_name”)

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL(‘“my_schema”.”table_name”’)

…

Other parameters passed on to methods.

Additional arguments

The following arguments are not part of the dbRemoveTable() generic (to improve compatibility across backends) but are part of the DBI specification:

  • temporary (default: FALSE)

  • fail_if_missing (default: TRUE)

These arguments must be provided as named arguments.

If temporary is TRUE, the call to dbRemoveTable() will consider only temporary tables. Not all backends support this argument. In particular, permanent tables of the same name are left untouched.

If fail_if_missing is FALSE, the call to dbRemoveTable() succeeds if the table does not exist.

Specification

A table removed by dbRemoveTable() doesn’t appear in the list of tables returned by dbListTables(), and dbExistsTable() returns FALSE. The removal propagates immediately to other connections to the same database. This function can also be used to remove a temporary table.

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: dbRemoveTable() will do the quoting, perhaps by calling dbQuoteIdentifier(conn, x = name)

  • If the result of a call to dbQuoteIdentifier(): no more quoting is done

Value

dbRemoveTable() returns TRUE, invisibly.

Failure modes

If the table does not exist, an error is raised. An attempt to remove a view with this function may result in an error.

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 dbQuoteIdentifier() or if this results in a non-scalar.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbExistsTable(con, "iris")
dbWriteTable(con, "iris", iris)
dbExistsTable(con, "iris")
dbRemoveTable(con, "iris")
dbExistsTable(con, "iris")

dbDisconnect(con)

List field names of a remote table

This section describes the behavior of the following method:

dbListFields(conn, name, ...)

Description

Returns the field names of a remote table as a character vector.

Arguments

conn

A DBIConnection object, as returned by dbConnect().

name

The table name, passed on to dbQuoteIdentifier(). Options are:

  • a character string with the unquoted DBMS table name, e.g. “table_name”,

  • a call to Id() with components to the fully qualified table name, e.g. Id(schema = “my_schema”, table = “table_name”)

  • a call to SQL() with the quoted and fully qualified table name given verbatim, e.g. SQL(‘“my_schema”.”table_name”’)

…

Other parameters passed on to methods.

Value

dbListFields() returns a character vector that enumerates all fields in the table in the correct order. This also works for temporary tables if supported by the database. The returned names are suitable for quoting with dbQuoteIdentifier().

Failure modes

If the table does not exist, an error is raised. Invalid types for the name argument (e.g., character of length not equal to one, or numeric) lead to an error. An error is also raised when calling this method for a closed or invalid connection.

Specification

The name argument can be

  • a string

  • the return value of dbQuoteIdentifier()

  • a value from the table column from the return value of dbListObjects() where is_prefix is FALSE

A column named row_names is treated like any other column.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars)
dbListFields(con, "mtcars")

dbDisconnect(con)

Is this DBMS object still valid?

This section describes the behavior of the following method:

dbIsValid(dbObj, ...)

Description

This generic tests whether a database object is still valid (i.e. it hasn’t been disconnected or cleared).

Arguments

dbObj An object inheriting from DBIObject, i.e. DBIDriver, DBIConnection, or a DBIResult
... Other arguments to methods.

Value

dbIsValid() returns a logical scalar, TRUE if the object specified by dbObj is valid, FALSE otherwise. A DBIConnection object is initially valid, and becomes invalid after disconnecting with dbDisconnect(). For an invalid connection object (e.g., for some drivers if the object is saved to a file and then restored), the method also returns FALSE. A DBIResult object is valid after a call to dbSendQuery(), and stays valid even after all rows have been fetched; only clearing it with dbClearResult() invalidates it. A DBIResult object is also valid after a call to dbSendStatement(), and stays valid after querying the number of rows affected; only clearing it with dbClearResult() invalidates it. If the connection to the database system is dropped (e.g., due to connectivity problems, server failure, etc.), dbIsValid() should return FALSE. This is not tested automatically.

Examples

dbIsValid(RSQLite::SQLite())

con <- dbConnect(RSQLite::SQLite(), ":memory:")
dbIsValid(con)

rs <- dbSendQuery(con, "SELECT 1")
dbIsValid(rs)

dbClearResult(rs)
dbIsValid(rs)

dbDisconnect(con)
dbIsValid(con)

Completion status

This section describes the behavior of the following method:

dbHasCompleted(res, ...)

Description

This method returns if the operation has completed. A SELECT query is completed if all rows have been fetched. A data manipulation statement is always completed.

Arguments

res An object inheriting from DBIResult.
... Other arguments passed on to methods.

Value

dbHasCompleted() returns a logical scalar. For a query initiated by dbSendQuery() with non-empty result set, dbHasCompleted() returns FALSE initially and TRUE after calling dbFetch() without limit. For a query initiated by dbSendStatement(), dbHasCompleted() always returns TRUE.

The data retrieval flow

This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames.

Most of this flow, except repeated calling of dbBind() or dbBindArrow(), is implemented by dbGetQuery(), which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendQuery() to create a result set object of class DBIResult.

  2. Optionally, bind query parameters with dbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbColumnInfo() to retrieve the structure of the result set without retrieving actual data.

  4. Use dbFetch() to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards.

  5. Use dbHasCompleted() to tell when you’re done. This method returns TRUE if no more rows are available for fetching.

  6. Repeat the last four steps as necessary.

  7. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

Failure modes

Attempting to query completion status for a result set cleared with dbClearResult() gives an error.

Specification

The completion status for a query is only guaranteed to be set to FALSE after attempting to fetch past the end of the entire result. Therefore, for a query with an empty result set, the initial return value is unspecified, but the result value is TRUE after trying to fetch only one row.

Similarly, for a query with a result set of length n, the return value is unspecified after fetching n rows, but the result value is TRUE after trying to fetch only one more row.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars)
rs <- dbSendQuery(con, "SELECT * FROM mtcars")

dbHasCompleted(rs)
ret1 <- dbFetch(rs, 10)
dbHasCompleted(rs)
ret2 <- dbFetch(rs)
dbHasCompleted(rs)

dbClearResult(rs)
dbDisconnect(con)

Get the statement associated with a result set

This section describes the behavior of the following method:

dbGetStatement(res, ...)

Description

Returns the statement that was passed to dbSendQuery() or dbSendStatement().

Arguments

res An object inheriting from DBIResult.
... Other arguments passed on to methods.

Value

dbGetStatement() returns a string, the query used in either dbSendQuery() or dbSendStatement().

Failure modes

Attempting to query the statement for a result set cleared with dbClearResult() gives an error.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars)
rs <- dbSendQuery(con, "SELECT * FROM mtcars")
dbGetStatement(rs)

dbClearResult(rs)
dbDisconnect(con)

The number of rows fetched so far

This section describes the behavior of the following method:

dbGetRowCount(res, ...)

Description

Returns the total number of rows actually fetched with calls to dbFetch() for this result set.

Arguments

res An object inheriting from DBIResult.
... Other arguments passed on to methods.

Value

dbGetRowCount() returns a scalar number (integer or numeric), the number of rows fetched so far. After calling dbSendQuery(), the row count is initially zero. After a call to dbFetch() without limit, the row count matches the total number of rows returned. Fetching a limited number of rows increases the number of rows by the number of rows returned, even if fetching past the end of the result set. For queries with an empty result set, zero is returned even after fetching. For data manipulation statements issued with dbSendStatement(), zero is returned before and after calling dbFetch().

Failure modes

Attempting to get the row count for a result set cleared with dbClearResult() gives an error.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars)
rs <- dbSendQuery(con, "SELECT * FROM mtcars")

dbGetRowCount(rs)
ret1 <- dbFetch(rs, 10)
dbGetRowCount(rs)
ret2 <- dbFetch(rs)
dbGetRowCount(rs)
nrow(ret1) + nrow(ret2)

dbClearResult(rs)
dbDisconnect(con)

The number of rows affected

This section describes the behavior of the following method:

dbGetRowsAffected(res, ...)

Description

This method returns the number of rows that were added, deleted, or updated by a data manipulation statement.

Arguments

res An object inheriting from DBIResult.
... Other arguments passed on to methods.

Value

dbGetRowsAffected() returns a scalar number (integer or numeric), the number of rows affected by a data manipulation statement issued with dbSendStatement(). The value is available directly after the call and does not change after calling dbFetch(). NA_integer_ or NA_numeric_ are allowed if the number of rows affected is not known.

For queries issued with dbSendQuery(), zero is returned before and after the call to dbFetch(). NA values are not allowed.

The command execution flow

This section gives a complete overview over the flow for the execution of SQL statements that have side effects such as stored procedures, inserting or deleting data, or setting database or connection options. Most of this flow, except repeated calling of dbBindArrow(), is implemented by dbExecute(), which should be sufficient for non-parameterized queries. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendStatement() to create a result set object of class DBIResult. For some queries you need to pass immediate = TRUE.

  2. Optionally, bind query parameters withdbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbGetRowsAffected() to retrieve the number of rows affected by the query.

  4. Repeat the last two steps as necessary.

  5. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

Failure modes

Attempting to get the rows affected for a result set cleared with dbClearResult() gives an error.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "mtcars", mtcars)
rs <- dbSendStatement(con, "DELETE FROM mtcars")
dbGetRowsAffected(rs)
nrow(mtcars)

dbClearResult(rs)
dbDisconnect(con)

Information about result types

This section describes the behavior of the following method:

dbColumnInfo(res, ...)

Description

Produces a data.frame that describes the output of a query. The data.frame should have as many rows as there are output fields in the result set, and each column in the data.frame describes an aspect of the result set field (field name, type, etc.)

Arguments

res An object inheriting from DBIResult.
... Other arguments passed on to methods.

Value

dbColumnInfo() returns a data frame with at least two columns "name" and "type" (in that order) (and optional columns that start with a dot). The "name" and "type" columns contain the names and types of the R columns of the data frame that is returned from dbFetch(). The "type" column is of type character and only for information. Do not compute on the "type" column, instead use dbFetch(res, n = 0) to create a zero-row data frame initialized with the correct data types.

The data retrieval flow

This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames.

Most of this flow, except repeated calling of dbBind() or dbBindArrow(), is implemented by dbGetQuery(), which should be sufficient unless you want to access the results in a paged way or you have a parameterized query that you want to reuse. This flow requires an active connection established by dbConnect(). See also vignette("dbi-advanced") for a walkthrough.

  1. Use dbSendQuery() to create a result set object of class DBIResult.

  2. Optionally, bind query parameters with dbBind() or dbBindArrow(). This is required only if the query contains placeholders such as ⁠?⁠ or ⁠\$1⁠, depending on the database backend.

  3. Optionally, use dbColumnInfo() to retrieve the structure of the result set without retrieving actual data.

  4. Use dbFetch() to get the entire result set, a page of results, or the remaining rows. Fetching zero rows is also possible to retrieeve the structure of the result set as a data frame. This step can be called multiple times. Only forward paging is supported, you need to cache previous pages if you need to navigate backwards.

  5. Use dbHasCompleted() to tell when you’re done. This method returns TRUE if no more rows are available for fetching.

  6. Repeat the last four steps as necessary.

  7. Use dbClearResult() to clean up the result set object. This step is mandatory even if no rows have been fetched or if an error has occurred during the processing. It is good practice to use on.exit() or withr::defer() to ensure that this step is always executed.

Failure modes

An attempt to query columns for a closed result set raises an error.

Specification

A column named row_names is treated like any other column.

The column names are always consistent with the data returned by dbFetch().

If the query returns unnamed columns, non-empty and non-NA names are assigned.

Column names that correspond to SQL or R keywords are left unchanged.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

rs <- dbSendQuery(con, "SELECT 1 AS a, 2 AS b")
dbColumnInfo(rs)
dbFetch(rs)

dbClearResult(rs)
dbDisconnect(con)

Begin/commit/rollback SQL transactions

This section describes the behavior of the following methods:

dbBegin(conn, ...)

dbCommit(conn, ...)

dbRollback(conn, ...)

Description

A transaction encapsulates several SQL statements in an atomic unit. It is initiated with dbBegin() and either made persistent with dbCommit() or undone with dbRollback(). In any case, the DBMS guarantees that either all or none of the statements have a permanent effect. This helps ensuring consistency of write operations to multiple tables.

Arguments

conn A DBIConnection object, as returned by dbConnect().
... Other parameters passed on to methods.

Details

Not all database engines implement transaction management, in which case these methods should not be implemented for the specific DBIConnection subclass.

Value

dbBegin(), dbCommit() and dbRollback() return TRUE, invisibly.

Failure modes

The implementations are expected to raise an error in case of failure, but this is not tested. In any way, all generics throw an error with a closed or invalid connection. In addition, a call to dbCommit() or dbRollback() without a prior call to dbBegin() raises an error. Nested transactions are not supported by DBI, an attempt to call dbBegin() twice yields an error.

Specification

Actual support for transactions may vary between backends. A transaction is initiated by a call to dbBegin() and committed by a call to dbCommit(). Data written in a transaction must persist after the transaction is committed. For example, a record that is missing when the transaction is started but is created during the transaction must exist both during and after the transaction, and also in a new connection.

A transaction can also be aborted with dbRollback(). All data written in such a transaction must be removed after the transaction is rolled back. For example, a record that is missing when the transaction is started but is created during the transaction must not exist anymore after the rollback.

Disconnection from a connection with an open transaction effectively rolls back the transaction. All data written in such a transaction must be removed after the transaction is rolled back.

The behavior is not specified if other arguments are passed to these functions. In particular, RSQLite issues named transactions with support for nesting if the name argument is set.

The transaction isolation level is not specified by DBI.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "cash", data.frame(amount = 100))
dbWriteTable(con, "account", data.frame(amount = 2000))

# All operations are carried out as logical unit:
dbBegin(con)
withdrawal <- 300
dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal))
dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal))
dbCommit(con)

dbReadTable(con, "cash")
dbReadTable(con, "account")

# Rolling back after detecting negative value on account:
dbBegin(con)
withdrawal <- 5000
dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal))
dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal))
if (dbReadTable(con, "account")\$amount >= 0) {
  dbCommit(con)
} else {
  dbRollback(con)
}

dbReadTable(con, "cash")
dbReadTable(con, "account")

dbDisconnect(con)

Self-contained SQL transactions

This section describes the behavior of the following methods:

dbWithTransaction(conn, code, ...)

dbBreak()

Description

Given that transactions are implemented, this function allows you to pass in code that is run in a transaction. The default method of dbWithTransaction() calls dbBegin() before executing the code, and dbCommit() after successful completion, or dbRollback() in case of an error. The advantage is that you don’t have to remember to do dbBegin() and dbCommit() or dbRollback() – that is all taken care of. The special function dbBreak() allows an early exit with rollback, it can be called only inside dbWithTransaction().

Arguments

conn A DBIConnection object, as returned by dbConnect().
code An arbitrary block of R code.
... Other parameters passed on to methods.

Details

DBI implements dbWithTransaction(), backends should need to override this generic only if they implement specialized handling.

Value

dbWithTransaction() returns the value of the executed code.

Failure modes

Failure to initiate the transaction (e.g., if the connection is closed or invalid of if dbBegin() has been called already) gives an error.

Specification

dbWithTransaction() initiates a transaction with dbBegin(), executes the code given in the code argument, and commits the transaction with dbCommit(). If the code raises an error, the transaction is instead aborted with dbRollback(), and the error is propagated. If the code calls dbBreak(), execution of the code stops and the transaction is silently aborted. All side effects caused by the code (such as the creation of new variables) propagate to the calling environment.

Examples

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "cash", data.frame(amount = 100))
dbWriteTable(con, "account", data.frame(amount = 2000))

# All operations are carried out as logical unit:
dbWithTransaction(
  con,
  {
    withdrawal <- 300
    dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal))
    dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal))
  }
)

# The code is executed as if in the curent environment:
withdrawal

# The changes are committed to the database after successful execution:
dbReadTable(con, "cash")
dbReadTable(con, "account")

# Rolling back with dbBreak():
dbWithTransaction(
  con,
  {
    withdrawal <- 5000
    dbExecute(con, "UPDATE cash SET amount = amount + ?", list(withdrawal))
    dbExecute(con, "UPDATE account SET amount = amount - ?", list(withdrawal))
    if (dbReadTable(con, "account")\$amount < 0) {
      dbBreak()
    }
  }
)

# These changes were not committed to the database:
dbReadTable(con, "cash")
dbReadTable(con, "account")

dbDisconnect(con)
DBI/inst/doc/DBI-advanced.Rmd0000644000176200001440000002657714552712323015224 0ustar liggesusers--- title: "Advanced DBI Usage" author: "James Wondrasek, Kirill Müller" date: "17/03/2020" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{Advanced DBI Usage} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r setup, include=FALSE} library(knitr) opts_chunk$set( echo = TRUE, error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5"), # FIXME: Bring back when relational.fit clone is up eval = FALSE ) knit_print.data.frame <- function(x, ...) { print(head(x, 3)) if (nrow(x) > 3) { cat("Showing 3 out of", nrow(x), "rows.\n") } invisible(x) } registerS3method("knit_print", "data.frame", "knit_print.data.frame") ``` ## Who this tutorial is for This tutorial is for you if you need to use a richer set of SQL features such as data manipulation queries, parameterized queries and queries performed using SQL's transaction features. See `vignette("DBI", package = "DBI")` for a more basic tutorial covering connecting to DBMS and executing simple queries. ## How to run more complex queries using DBI `dbGetQuery()` works by calling a number of functions behind the scenes. If you need more control you can manually build your own query, retrieve results at your selected rate, and release the resources involved by calling the same functions. These functions are: - `dbSendQuery()` sends the SQL query to the DBMS and returns a `result` object. The query is limited to `SELECT` statements. If you want to send other statements, such as `INSERT`, `UPDATE`, `DELETE`, etc, use `dbSendStatement()`. - `dbFetch()` is called with the `result` object returned by `dbSendQuery()`. It also accepts an argument specifying the number of rows to be returned, e.g. `n = 200`. If you want to fetch all the rows, use `n = -1`. - `dbClearResult()` is called when you have finished retrieving data. It releases the resources associated with the `result` object. ```{r} library(DBI) con <- dbConnect( RMariaDB::MariaDB(), host = "relational.fit.cvut.cz", port = 3306, username = "guest", password = "relational", dbname = "sakila" ) res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = 'G'") df <- dbFetch(res, n = 3) dbClearResult(res) head(df, 3) ``` ## How to read part of a table from a database If your dataset is large you may want to fetch a limited number of rows at a time. As demonstrated below, this can be accomplished by using a while loop where the function `dbHasCompleted()` is used to check for ongoing rows, and `dbFetch()` is used with the `n = X` argument, specifying how many rows to return on each iteration. Again, we call `dbClearResult()` at the end to release resources. ```{r} res <- dbSendQuery(con, "SELECT * FROM film") while (!dbHasCompleted(res)) { chunk <- dbFetch(res, n = 300) print(nrow(chunk)) } dbClearResult(res) ``` ## How to use parameters (safely) in SQL queries `dbSendQuery()` can be used with parameterized SQL queries. DBI supports two ways to avoid SQL injection attacks from user-supplied parameters: quoting and parameterized queries. ### Quoting Quoting of parameter values is performed using the function `dbQuoteLiteral()`, which supports many R data types, including date and time.[^quote-string] [^quote-string]: An older method, `dbQuoteString()`, was used to quote string values only. The `dbQuoteLiteral()` method forwards to `dbQuoteString()` for character vectors. Users do not need to distinguish between these two cases. In cases where users may be supplying table or column names to use in the query for data retrieval, those names or identifiers must also be escaped. As there may be DBMS-specific rules for escaping these identifiers, DBI provides the function `dbQuoteIdentifier()` to generate a safe string representation. ```{r quote} safe_id <- dbQuoteIdentifier(con, "rating") safe_param <- dbQuoteLiteral(con, "G") query <- paste0("SELECT title, ", safe_id, " FROM film WHERE ", safe_id, " = ", safe_param) query res <- dbSendQuery(con, query) dbFetch(res) dbClearResult(res) ``` The same result can be had by using `glue::glue_sql()`. It performs the same safe quoting on any variable or R statement appearing between braces within the query string. ```{r} id <- "rating" param <- "G" query <- glue::glue_sql("SELECT title, {`id`} FROM film WHERE {`id`} = {param}", .con = con) df <- dbGetQuery(con, query) head(df, 3) ``` ### Parameterized queries Rather than performing the parameter substitution ourselves, we can push it to the DBMS by including placeholders in the query. Different DBMS use different placeholder schemes, DBI passes through the SQL expression unchanged. MariaDB uses a question mark (?) as placeholder and expects an unnamed list of parameter values. Other DBMS may use named parameters. We recommend consulting the documentation for the DBMS you are using. As an example, a web search for "mariadb parameterized queries" leads to the documentation for the [`PREPARE` statement](https://mariadb.com/kb/en/prepare-statement/) which mentions: > Within the statement, "?" characters can be used as parameter markers to indicate where data values are to be bound to the query later when you execute it. Currently there is no list of which placeholder scheme a particular DBMS supports. Placeholders only work for literal values. Other parts of the query, e.g. table or column identifiers, still need to be quoted with `dbQuoteIdentifier()`. For a single set of parameters, the `params` argument to `dbSendQuery()` or `dbGetQuery()` can be used. It takes a list and its members are substituted in order for the placeholders within the query. ```{r params} params <- list("G") safe_id <- dbQuoteIdentifier(con, "rating") query <- paste0("SELECT * FROM film WHERE ", safe_id, " = ?") query res <- dbSendQuery(con, query, params = params) dbFetch(res, n = 3) dbClearResult(res) ``` Below is an example query using multiple placeholders with the MariaDB driver. The placeholders are supplied as a list of values ordered to match the position of the placeholders in the query. ```{r multi-param} q_params <- list("G", 90) query <- "SELECT title, rating, length FROM film WHERE rating = ? AND length >= ?" res <- dbSendQuery(con, query, params = q_params) dbFetch(res, n = 3) dbClearResult(res) ``` When you wish to perform the same query with different sets of parameter values, `dbBind()` is used. There are two ways to use `dbBind()`. Firstly, it can be used multiple times with same query. ```{r dbbind} res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = ?") dbBind(res, list("G")) dbFetch(res, n = 3) dbBind(res, list("PG")) dbFetch(res, n = 3) dbClearResult(res) ``` Secondly, `dbBind()` can be used to execute the same statement with multiple values at once. ```{r bind_quotestring} res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = ?") dbBind(res, list(c("G", "PG"))) dbFetch(res, n = 3) dbClearResult(res) ``` Use a list of vectors if your query has multiple parameters: ```{r bind-multi-param} q_params <- list(c("G", "PG"), c(90, 120)) query <- "SELECT title, rating, length FROM film WHERE rating = ? AND length >= ?" res <- dbSendQuery(con, query, params = q_params) dbFetch(res, n = 3) dbClearResult(res) ``` Always disconnect from the database when done. ```{r disconnect} dbDisconnect(con) ``` ## SQL data manipulation - UPDATE, DELETE and friends For SQL queries that affect the underlying database, such as UPDATE, DELETE, INSERT INTO, and DROP TABLE, DBI provides two functions. `dbExecute()` passes the SQL statement to the DBMS for execution and returns the number of rows affected. `dbSendStatement()` performs in the same manner, but returns a result object. Call `dbGetRowsAffected()` with the result object to get the count of the affected rows. You then need to call `dbClearResult()` with the result object afterwards to release resources. In actuality, `dbExecute()` is a convenience function that calls `dbSendStatement()`, `dbGetRowsAffected()`, and `dbClearResult()`. You can use these functions if you need more control over the query process. The subsequent examples use an in-memory SQL database provided by `RSQLite::SQLite()`, because the remote database used in above examples does not allow writing. ```{r} library(DBI) con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cars", head(cars, 3)) dbExecute( con, "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)" ) rs <- dbSendStatement( con, "INSERT INTO cars (speed, dist) VALUES (4, 4), (5, 5), (6, 6)" ) dbGetRowsAffected(rs) dbClearResult(rs) dbReadTable(con, "cars") ``` Do not forget to disconnect from the database at the end. ```{r} dbDisconnect(con) ``` ## SQL transactions with DBI DBI allows you to group multiple queries into a single atomic transaction. Transactions are initiated with `dbBegin()` and either made persistent with `dbCommit()` or undone with `dbRollback()`. The example below updates two tables and ensures that either both tables are updated, or no changes are persisted to the database and an error is thrown. ```{r} con <- dbConnect(RSQLite::SQLite(), ":memory:") dbWriteTable(con, "cash", data.frame(amount = 100)) dbWriteTable(con, "account", data.frame(amount = 2000)) withdraw <- function(amount) { # All operations must be carried out as logical unit: dbExecute(con, "UPDATE cash SET amount = amount + ?", list(amount)) dbExecute(con, "UPDATE account SET amount = amount - ?", list(amount)) } withdraw_transacted <- function(amount) { # Ensure atomicity dbBegin(con) # Perform operation withdraw(amount) # Persist results dbCommit(con) } withdraw_transacted(300) ``` After withdrawing 300 credits, the cash is increased and the account is decreased by this amount. The transaction ensures that either both operations succeed, or no change occurs. ```{r} dbReadTable(con, "cash") dbReadTable(con, "account") ``` We can roll back changes manually if necessary. Do not forget to call `dbRollback()` in case of error, otherwise the transaction remains open indefinitely. ```{r} withdraw_if_funds <- function(amount) { dbBegin(con) withdraw(amount) # Rolling back after detecting negative value on account: if (dbReadTable(con, "account")$amount >= 0) { dbCommit(con) TRUE } else { message("Insufficient funds") dbRollback(con) FALSE } } withdraw_if_funds(5000) dbReadTable(con, "cash") dbReadTable(con, "account") ``` `dbWithTransaction()` simplifies using transactions. Pass it a connection and the code you want to run as a transaction. It will execute the code and call `dbCommit()` on success and call `dbRollback()` if an error is thrown. ```{r error = TRUE} withdraw_safely <- function(amount) { dbWithTransaction(con, { withdraw(amount) if (dbReadTable(con, "account")$amount < 0) { stop("Error: insufficient funds", call. = FALSE) } }) } withdraw_safely(5000) dbReadTable(con, "cash") dbReadTable(con, "account") ``` As usual, do not forget to disconnect from the database when done. ```{r} dbDisconnect(con) ``` ## Conclusion That concludes the major features of DBI. For more details on the library functions covered in this tutorial and the `vignette("DBI", package = "DBI")` introductory tutorial see the DBI specification at `vignette("spec", package = "DBI")`. If you are after a data manipulation library that works at a higher level of abstraction, check out [dplyr](https://dplyr.tidyverse.org). It is a grammar of data manipulation that can work with local dataframes and remote databases and uses DBI under the hood. DBI/inst/doc/DBI-1.html0000644000176200001440000042557114561352215014036 0ustar liggesusers A Common Database Interface (DBI)

A Common Database Interface (DBI)

R-Databases Special Interest Group

16 June 2003

This document describes a common interface between the S language (in its R and S-Plus implementations) and database management systems (DBMS). The interface defines a small set of classes and methods similar in spirit to Perl’s DBI, Java’s JDBC, Python’s DB-API, and Microsoft’s ODBC.

Version

This document describes version 0.1-6 of the database interface API (application programming interface).

Introduction

The database interface (DBI) separates the connectivity to the DBMS into a “front-end” and a “back-end”. Applications use only the exposed “front-end” API. The facilities that communicate with specific DBMS (Oracle, PostgreSQL, etc.) are provided by “device drivers” that get invoked automatically by the S language evaluator. The following example illustrates some of the DBI capabilities:

## Choose the proper DBMS driver and connect to the server

drv <- dbDriver("ODBC")
con <- dbConnect(drv, "dsn", "usr", "pwd")

## The interface can work at a higher level importing tables
## as data.frames and exporting data.frames as DBMS tables.

dbListTables(con)
dbListFields(con, "quakes")
if(dbExistsTable(con, "new_results"))
   dbRemoveTable(con, "new_results")
dbWriteTable(con, "new_results", new.output)

## The interface allows lower-level interface to the DBMS
res <- dbSendQuery(con, paste(
            "SELECT g.id, g.mirror, g.diam, e.voltage",
            "FROM geom_table as g, elec_measures as e",
            "WHERE g.id = e.id and g.mirrortype = 'inside'",
            "ORDER BY g.diam"))
out <- NULL
while(!dbHasCompleted(res)){
   chunk <- fetch(res, n = 10000)
   out <- c(out, doit(chunk))
}

## Free up resources
dbClearResult(res)
dbDisconnect(con)
dbUnloadDriver(drv)

(only the first 2 expressions are DBMS-specific – all others are independent of the database engine itself).

Individual DBI drivers need not implement all the features we list below (we indicate those that are optional). Furthermore, drivers may extend the core DBI facilities, but we suggest to have these extensions clearly indicated and documented.

The following are the elements of the DBI:

  1. A set of classes and methods (Section [sec:DBIClasses]) that defines what operations are possible and how they are defined, e.g.:

    • connect/disconnect to the DBMS

    • create and execute statements in the DBMS

    • extract results/output from statements

    • error/exception handling

    • information (meta-data) from database objects

    • transaction management (optional)

    Some things are left explicitly unspecified, e.g., authentication and even the query language, although it is hard to avoid references to SQL and relational database management systems (RDBMS).

  2. Drivers

    Drivers are collection of functions that implement the functionality defined above in the context of specific DBMS, e.g., mSQL, Informix.

  3. Data type mappings (Section [sec:data-mappings].)

    Mappings and conversions between DBMS data types and R/S objects. All drivers should implement the “basic” primitives (see below), but may chose to add user-defined conversion function to handle more generic objects (e.g., factors, ordered factors, time series, arrays, images).

  4. Utilities (Section [sec:utilities].)

    These facilities help with details such as mapping of identifiers between S and DBMS (e.g., _ is illegal in R/S names, and . is used for constructing compound SQL identifiers), etc.

DBI Classes and Methods

The following are the main DBI classes. They need to be extended by individual database back-ends (Sybase, Oracle, etc.) Individual drivers need to provide methods for the generic functions listed here (those methods that are optional are so indicated).

Note: Although R releases prior to 1.4 do not have a formal concept of classes, we will use the syntax of the S Version 4 classes and methods (available in R releases 1.4 and later as library methods) to convey precisely the DBI class hierarchy, its methods, and intended behavior.

The DBI classes are DBIObject, DBIDriver, DBIConnection and DBIResult. All these are virtual classes. Drivers define new classes that extend these, e.g., PgSQLDriver, PgSQLConnection, and so on.

Class hierarchy for the DBI. The top two layers are comprised of virtual classes and each lower layer represents a set of driver-specific implementation classes that provide the functionality defined by the virtual classes above.
Class hierarchy for the DBI. The top two layers are comprised of virtual classes and each lower layer represents a set of driver-specific implementation classes that provide the functionality defined by the virtual classes above.
DBIObject:

Virtual class1 that groups all other DBI classes.

DBIDriver:

Virtual class that groups all DBMS drivers. Each DBMS driver extends this class. Typically generator functions instantiate the actual driver objects, e.g., PgSQL, HDF5, BerkeleyDB.

DBIConnection:

Virtual class that encapsulates connections to DBMS.

DBIResult:

Virtual class that describes the result of a DBMS query or statement.

[Q: Should we distinguish between a simple result of DBMS statements e.g., as delete from DBMS queries (i.e., those that generate data).]

The methods format, print, show, dbGetInfo, and summary are defined (and implemented in the DBI package) for the DBIObject base class, thus available to all implementations; individual drivers, however, are free to override them as they see fit.

format(x, ...):

produces a concise character representation (label) for the DBIObject x.

print(x, ...)/show(x):

prints a one-line identification of the object x.

summary(object, ...):

produces a concise description of the object. The default method for DBIObject simply invokes dbGetInfo(dbObj) and prints the name-value pairs one per line. Individual implementations may tailor this appropriately.

dbGetInfo(dbObj, ...):

extracts information (meta-data) relevant for the DBIObject dbObj. It may return a list of key/value pairs, individual meta-data if supplied in the call, or NULL if the requested meta-data is not available.

Hint: Driver implementations may choose to allow an argument what to specify individual meta-data, e.g., dbGetInfo(drv, what = max.connections).

In the next few sub-sections we describe in detail each of these classes and their methods.

Class DBIObject

This class simply groups all DBI classes, and thus all extend it.

Class DBIDriver

This class identifies the database management system. It needs to be extended by individual back-ends (Oracle, PostgreSQL, etc.)

The DBI provides the generator dbDriver(driverName) which simply invokes the function driverName, which in turn instantiates the corresponding driver object.

The DBIDriver class defines the following methods:

driverName:

[meth:driverName] initializes the driver code. The name driverName refers to the actual generator function for the DBMS, e.g., RPgSQL, RODBC, HDF5. The driver instance object is used with dbConnect (see page ) for opening one or possibly more connections to one or more DBMS.

dbListConnections(drv, ...):

list of current connections being handled by the drv driver. May be NULL if there are no open connections. Drivers that do not support multiple connections may return the one open connection.

dbGetInfo(dbObj, ...):

returns a list of name-value pairs of information about the driver.

Hint: Useful entries could include

name:

the driver name (e.g., RODBC, RPgSQL);

driver.version:

version of the driver;

DBI.version:

the version of the DBI that the driver implements, e.g., 0.1-2;

client.version:

of the client DBMS libraries (e.g., version of the libpq library in the case of RPgSQL);

max.connections:

maximum number of simultaneous connections;

plus any other relevant information about the implementation, for instance, how the driver handles upper/lower case in identifiers.

dbUnloadDriver(driverName) (optional):

frees all resources (local and remote) used by the driver. Returns a logical to indicate if it succeeded or not.

Class DBIConnection

This virtual class encapsulates the connection to a DBMS, and it provides access to dynamic queries, result sets, DBMS session management (transactions), etc.

Note: Individual drivers are free to implement single or multiple simultaneous connections.

The methods defined by the DBIConnection class include:

dbConnect(drv, ...):

[meth:dbConnect] creates and opens a connection to the database implemented by the driver drv (see Section [sec:DBIDriver]). Each driver will define what other arguments are required, e.g., dbname or dsn for the database name, user, and password. It returns an object that extends DBIConnection in a driver-specific manner (e.g., the MySQL implementation could create an object of class MySQLConnection that extends DBIConnection).

dbDisconnect(conn, ...):

closes the connection, discards all pending work, and frees resources (e.g., memory, sockets). Returns a logical indicating whether it succeeded or not.

dbSendQuery(conn, statement, ...):

submits one statement to the DBMS. It returns a DBIResult object. This object is needed for fetching data in case the statement generates output (see fetch on page ), and it may be used for querying the state of the operation; see dbGetInfo and other meta-data methods on page .

dbGetQuery(conn, statement, ...):

submit, execute, and extract output in one operation. The resulting object may be a data.frame if the statement generates output. Otherwise the return value should be a logical indicating whether the query succeeded or not.

dbGetException(conn, ...):

returns a list with elements errNum and errMsg with the status of the last DBMS statement sent on a given connection (this information may also be provided by the dbGetInfo meta-data function on the conn object.

Hint: The ANSI SQL-92 defines both a status code and an status message that could be return as members of the list.

dbGetInfo(dbObj, ...):

returns a list of name-value pairs describing the state of the connection; it may return one or more meta-data, the actual driver method allows to specify individual pieces of meta-data (e.g., maximum number of open results/cursors).

Hint: Useful entries could include

dbname:

the name of the database in use;

db.version:

the DBMS server version (e.g., “Oracle 8.1.7 on Solaris”;

host:

host where the database server resides;

user:

user name;

password:

password (is this safe?);

plus any other arguments related to the connection (e.g., thread id, socket or TCP connection type).

dbListResults(conn, ...):

list of DBIResult objects currently active on the connection conn. May be NULL if no result set is active on conn. Drivers that implement only one result set per connection could return that one object (no need to wrap it in a list).

Note: The following are convenience methods that simplify the import/export of (mainly) data.frames. The first five methods implement the core methods needed to attach remote DBMS to the S search path. (For details, see Chambers (1991, 1998).)

Hint: For relational DBMS these methods may be easily implemented using the core DBI methods dbConnect, dbSendQuery, and fetch, due to SQL reflectance (i.e., one easily gets this meta-data by querying the appropriate tables on the RDBMS).

dbListTables(conn, ...):

returns a character vector (possibly of zero-length) of object (table) names available on the conn connection.

dbReadTable(conn, name, ...):

imports the data stored remotely in the table name on connection conn. Use the field row.names as the row.names attribute of the output data.frame. Returns a data.frame.

[Q: should we spell out how row.names should be created? E.g., use a field (with unique values) as row.names? Also, should dbReadTable reproduce a data.frame exported with dbWriteTable?]

dbWriteTable(conn, name, value, ...):

write the object value (perhaps after coercing it to data.frame) into the remote object name in connection conn. Returns a logical indicating whether the operation succeeded or not.

dbExistsTable(conn, name, ...):

does remote object name exist on conn? Returns a logical.

dbRemoveTable(conn, name, ...):

removes remote object name on connection conn. Returns a logical indicating whether the operation succeeded or not.

dbListFields(conn, name, ...):

returns a character vector listing the field names of the remote table name on connection conn (see dbColumnInfo() for extracting data type on a table).

Note: The following methods deal with transactions and stored procedures. All these functions are optional.

dbCommit(conn, ...)(optional):

commits pending transaction on the connection and returns TRUE or FALSE depending on whether the operation succeeded or not.

dbRollback(conn, ...)(optional):

undoes current transaction on the connection and returns TRUE or FALSE depending on whether the operation succeeded or not.

dbCallProc(conn, storedProc, ...)(optional):

invokes a stored procedure in the DBMS and returns a DBIResult object.

[Stored procedures are not part of the ANSI SQL-92 standard and vary substantially from one RDBMS to another.]

Deprecated since 2014:

The recommended way of calling a stored procedure is now

  • dbGetQuery if a result set is returned and
  • dbExecute for data manipulation and other cases that do not return a result set.

Class DBIResult

This virtual class describes the result and state of execution of a DBMS statement (any statement, query or non-query). The result set res keeps track of whether the statement produces output for R/S, how many rows were affected by the operation, how many rows have been fetched (if statement is a query), whether there are more rows to fetch, etc.

Note: Individual drivers are free to allow single or multiple active results per connection.

[Q: Should we distinguish between results that return no data from those that return data?]

The class DBIResult defines the following methods:

fetch(res, n, ...):

[meth:fetch] fetches the next n elements (rows) from the result set res and return them as a data.frame. A value of n=-1 is interpreted as “return all elements/rows”.

dbClearResult(res, ...):

flushes any pending data and frees all resources (local and remote) used by the object res on both sides of the connection. Returns a logical indicating success or not.

dbGetInfo(dbObj, ...):

returns a name-value list with the state of the result set.

Hint: Useful entries could include

statement:

a character string representation of the statement being executed;

rows.affected:

number of affected records (changed, deleted, inserted, or extracted);

row.count:

number of rows fetched so far;

has.completed:

has the statement (query) finished?

is.select:

a logical describing whether or not the statement generates output;

plus any other relevant driver-specific meta-data.

dbColumnInfo(res, ...):

produces a data.frame that describes the output of a query. The data.frame should have as many rows as there are output fields in the result set, and each column in the data.frame should describe an aspect of the result set field (field name, type, etc.)

Hint: The data.frame columns could include

field.name:

DBMS field label;

field.type:

DBMS field type (implementation-specific);

data.type:

corresponding R/S data type, e.g., integer;

precision/scale:

(as in ODBC terminology), display width and number of decimal digits, respectively;

nullable:

whether the corresponding field may contain (DBMS) NULL values;

plus other driver-specific information.

dbSetDataMappings(flds, ...)(optional):

defines a conversion between internal DBMS data types and R/S classes. We expect the default mappings (see Section [sec:data-mappings]) to be by far the most common ones, but users that need more control may specify a class generator for individual fields in the result set. [This topic needs further discussion.]

Note: The following are convenience methods that extract information from the result object (they may be implemented by invoking dbGetInfo with appropriate arguments).

dbGetStatement(res, ...)(optional):

returns the DBMS statement (as a character string) associated with the result res.

dbGetRowsAffected(res, ...)(optional):

returns the number of rows affected by the executed statement (number of records deleted, modified, extracted, etc.)

dbHasCompleted(res, ...)(optional):

returns a logical that indicates whether the operation has been completed (e.g., are there more records to be fetched?).

dbGetRowCount(res, ...)(optional):

returns the number of rows fetched so far.

Data Type Mappings

The data types supported by databases are different than the data types in R and S, but the mapping between the “primitive” types is straightforward: Any of the many fixed and varying length character types are mapped to R/S character. Fixed-precision (non-IEEE) numbers are mapped into either doubles (numeric) or long (integer). Notice that many DBMS do not follow the so-called IEEE arithmetic, so there are potential problems with under/overflows and loss of precision, but given the R/S primitive types we cannot do too much but identify these situations and warn the application (how?).

By default dates and date-time objects are mapped to character using the appropriate TO_CHAR function in the DBMS (which should take care of any locale information). Some RDBMS support the type CURRENCY or MONEY which should be mapped to numeric (again with potential round off errors). Large objects (character, binary, file, etc.) also need to be mapped. User-defined functions may be specified to do the actual conversion (as has been done in other inter-systems packages 2).

Specifying user-defined conversion functions still needs to be defined.

Utilities

The core DBI implementation should make available to all drivers some common basic utilities. For instance:

dbGetDBIVersion:

returns the version of the currently attached DBI as a string.

dbDataType(dbObj, obj, ...):

returns a string with the (approximately) appropriate data type for the R/S object obj. The DBI can implement this following the ANSI-92 standard, but individual drivers may want/need to extend it to make use of DBMS-specific types.

make.db.names(dbObj, snames, ...):

maps R/S names (identifiers) to SQL identifiers replacing illegal characters (as .) by the legal SQL _.

SQLKeywords(dbObj, ...):

returns a character vector of SQL keywords (reserved words). The default method returns the list of .SQL92Keywords, but drivers should update this vector with the DBMS-specific additional reserved words.

isSQLKeyword(dbObj, name, ...):

for each element in the character vector name determine whether or not it is an SQL keyword, as reported by the generic function SQLKeywords. Returns a logical vector parallel to the input object name.

Open Issues and Limitations

There are a number of issues and limitations that the current DBI conscientiously does not address on the interest of simplicity. We do list here the most important ones.

Non-SQL:

Is it realistic to attempt to encompass non-relational databases, like HDF5, Berkeley DB, etc.?

Security:

allowing users to specify their passwords on R/S scripts may be unacceptable for some applications. We need to consider alternatives where users could store authentication on files (perhaps similar to ODBC’s odbc.ini) with more stringent permissions.

Exceptions:

the exception mechanism is a bit too simple, and it does not provide for information when problems stem from the DBMS interface itself. For instance, under/overflow or loss of precision as we move numeric data from DBMS to the more limited primitives in R/S.

Asynchronous communication:

most DBMS support both synchronous and asynchronous communications, allowing applications to submit a query and proceed while the database server process the query. The application is then notified (or it may need to poll the server) when the query has completed. For large computations, this could be very useful, but the DBI would need to specify how to interrupt the server (if necessary) plus other details. Also, some DBMS require applications to use threads to implement asynchronous communication, something that neither R nor S-Plus currently addresses.

SQL scripts:

the DBI only defines how to execute one SQL statement at a time, forcing users to split SQL scripts into individual statements. We need a mechanism by which users can submit SQL scripts that could possibly generate multiple result sets; in this case we may need to introduce new methods to loop over multiple results (similar to Python’s nextResultSet).

BLOBS/CLOBS:

large objects (both character and binary) present some challenges both to R and S-Plus. It is becoming more common to store images, sounds, and other data types as binary objects in DBMS, some of which can be in principle quite large. The SQL-92 ANSI standard allows up to 2 gigabytes for some of these objects. We need to carefully plan how to deal with binary objects.

Transactions:

transaction management is not fully described.

Additional methods:

Do we need any additional methods? (e.g., dbListDatabases(conn), dbListTableIndices(conn, name), how do we list all available drivers?)

Bind variables:

the interface is heavily biased towards queries, as opposed to general purpose database development. In particular we made no attempt to define “bind variables”; this is a mechanism by which the contents of R/S objects are implicitly moved to the database during SQL execution. For instance, the following embedded SQL statement

  /* SQL */
  SELECT * from emp_table where emp_id = :sampleEmployee

would take the vector sampleEmployee and iterate over each of its elements to get the result. Perhaps the DBI could at some point in the future implement this feature.

Resources

The idea of a common interface to databases has been successfully implemented in various environments, for instance:

Java’s Database Connectivity (JDBC) (www.javasoft.com).

In C through the Open Database Connectivity (ODBC) (www.unixodbc.org).

Python’s Database Application Programming Interface (www.python.org).

Perl’s Database Interface (dbi.perl.org).

Chambers, John M. 1991. “Data Management in S.” Bell Labs, Lucent Technologies.
———. 1998. “Database Classes.” Bell Labs, Lucent Technologies.

  1. A virtual class allows us to group classes that share some common characteristics, even if their implementations are radically different.↩︎

  2. Duncan Temple Lang has volunteered to port the data conversion code found in R-Java, R-Perl, and R-Python packages to the DBI↩︎

DBI/inst/doc/DBI-proposal.Rmd0000644000176200001440000006640614552712323015311 0ustar liggesusers--- title: "A Common Interface to Relational Databases from R and S -- A Proposal" author: "David James" date: "March 16, 2000" output: rmarkdown::html_vignette bibliography: biblio.bib vignette: > %\VignetteIndexEntry{A Common Interface to Relational Databases from R and S -- A Proposal} %\VignetteEngine{knitr::rmarkdown} --- For too long S and similar data analysis environments have lacked good interfaces to relational database systems (RDBMS). For the last twenty years or so these RDBMS have evolved into highly optimized client-server systems for data storage and manipulation, and currently they serve as repositories for most of the business, industrial, and research “raw” data that analysts work with. Other analysis packages, such as SAS, have traditionally provided good data connectivity, but S and GNU R have relied on intermediate text files as means of importing data (but see @R.imp-exp and @R-dbms.) Although this simple approach works well for relatively modest amounts of mostly static data, it does not scale up to larger amounts of data distributed over machines and locations, nor does it scale up to data that is highly dynamic – situations that are becoming increasingly common. We want to propose a common interface between R/S and RDBMS that would allow users to access data stored on database servers in a uniform and predictable manner irrespective of the database engine. The interface defines a small set of classes and methods similar in spirit to Python’s DB-API, Java’s JDBC, Microsoft’s ODBC, Perl’s DBI, etc., but it conforms to the “whole-object” philosophy so natural in S and R. # Computing with Distributed Data {#sec:distr} As data analysts, we are increasingly faced with the challenge of larger data sources distributed over machines and locations; most of these data sources reside in relational database management systems (RDBMS). These relational databases represent a mature client-server distributed technology that we as analysts could be exploiting more that we’ve done in the past. The relational technology provides a well-defined standard, the ANSI SQL-92 @sql92, both for defining and manipulating data in a highly optimized fashion from virtually any application. In contrast, S and Splus have provided somewhat limited tools for coping with the challenges of larger and distributed data sets (Splus does provide an `import` function to import from databases, but it is quite limited in terms of SQL facilities). The R community has been more resourceful and has developed a number of good libraries for connecting to mSQL, MySQL, PostgreSQL, and ODBC; each library, however, has defined its own interface to each database engine a bit differently. We think it would be to everybody’s advantage to coordinate the definition of a common interface, an effort not unlike those taken in the Python and Perl communities. The goal of a common, seamless access to distributed data is a modest one in our evolution towards a fully distributed computing environment. We recognize the greater goal of distributed computing as the means to fully integrate diverse systems – not just databases – into a truly flexible analysis environment. Good connectivity to databases, however, is of immediate necessity both in practical terms and as a means to help us transition from monolithic, self-contained systems to those in which computations, not only the data, can be carried out in parallel over a wide number of computers and/or systems @duncan2000. Issues of reliability, security, location transparency, persistence, etc., will be new to most of us and working with distributed data may provide a more gradual change to ease in the ultimate goal of full distributed computing. # A Common Interface {#sec:rs-dbi} We believe that a common interface to databases can help users easily access data stored in RDBMS. A common interface would describe, in a uniform way, how to connect to RDBMS, extract meta-data (such as list of available databases, tables, etc.) as well as a uniform way to execute SQL statements and import their output into R and S. The current emphasis is on querying databases and not so much in a full low-level interface for database development as in JDBC or ODBC, but unlike these, we want to approach the interface from the “whole-object” perspective @S4 so natural to R/S and Python – for instance, by fetching all fields and records simultaneously into a single object. The basic idea is to split the interface into a front-end consisting of a few classes and generic functions that users invoke and a back-end set of database-specific classes and methods that implement the actual communication. (This is a very well-known pattern in software engineering, and another good verbatim is the device-independent graphics in R/S where graphics functions produce similar output on a variety of different devices, such X displays, Postscript, etc.) The following verbatim shows the front-end: ``` > mgr <- dbManager("Oracle") > con <- dbConnect(mgr, user = "user", passwd = "passwd") > rs <- dbExecStatement(con, "select fld1, fld2, fld3 from MY_TABLE") > tbls <- fetch(rs, n = 100) > hasCompleted(rs) [1] T > close(rs) > rs <- dbExecStatement(con, "select id_name, q25, q50 from liv2") > res <- fetch(rs) > getRowCount(rs) [1] 73 > close(con) ``` Such scripts should work with other RDBMS (say, MySQL) by replacing the first line with ``` > mgr <- dbManager("MySQL") ``` ## Interface Classes {#sec:rs-dbi-classes} The following are the main RS-DBI classes. They need to be extended by individual database back-ends (MySQL, Oracle, etc.) `dbManager` : Virtual class[^2] extended by actual database managers, e.g., Oracle, MySQL, Informix. `dbConnection` : Virtual class that captures a connection to a database instance[^3]. `dbResult` : Virtual class that describes the result of an SQL statement. `dbResultSet` : Virtual class, extends `dbResult` to fully describe the output of those statements that produce output records, i.e., `SELECT` (or `SELECT`-like) SQL statement. All these classes should implement the methods `show`, `describe`, and `getInfo`: `show` : (`print` in R) prints a one-line identification of the object. `describe` : prints a short summary of the meta-data of the specified object (like `summary` in R/S). `getInfo` : takes an object of one of the above classes and a string specifying a meta-data item, and it returns the corresponding information (`NULL` if unavailable). > mgr <- dbManager("MySQL") > getInfo(mgr, "version") > con <- dbConnect(mgr, ...) > getInfo(con, "type") The reason we implement the meta-data through `getInfo` in this way is to simplify the writing of database back-ends. We don’t want to overwhelm the developers of drivers (ourselves, most likely) with hundreds of methods as in the case of JDBC. In addition, the following methods should also be implemented: `getDatabases` : lists all available databases known to the `dbManager`. `getTables` : lists tables in a database. `getTableFields` : lists the fields in a table in a database. `getTableIndices` : lists the indices defined for a table in a database. These methods may be implemented using the appropriate `getInfo` method above. In the next few sections we describe in detail each of these classes and their methods. ### Class `dbManager` {#sec:dbManager} This class identifies the relational database management system. It needs to be extended by individual back-ends (Oracle, PostgreSQL, etc.) The `dbManager` class defines the following methods: `load` : initializes the driver code. We suggest having the generator, `dbManager(driver)`, automatically load the driver. `unload` : releases whatever resources the driver is using. `getVersion` : returns the version of the RS-DBI currently implemented, plus any other relevant information about the implementation itself and the RDBMS being used. ### Class `dbConnection` {#sec:dbConnection} This virtual class captures a connection to a RDBMS, and it provides access to dynamic SQL, result sets, RDBMS session management (transactions), etc. Note that the `dbManager` may or may not allow multiple simultaneous connections. The methods it defines include: `dbConnect` : opens a connection to the database `dbname`. Other likely arguments include `host`, `user`, and `password`. It returns an object that extends `dbConnection` in a driver-specific manner (e.g., the MySQL implementation creates a connection of class `MySQLConnection` that extends `dbConnection`). Note that we could separate the steps of connecting to a RDBMS and opening a database there (i.e., opening an *instance*). For simplicity we do the 2 steps in this method. If the user needs to open another instance in the same RDBMS, just open a new connection. `close` : closes the connection and discards all pending work. `dbExecStatement` : submits one SQL statement. It returns a `dbResult` object, and in the case of a `SELECT` statement, the object also inherits from `dbResultSet`. This `dbResultSet` object is needed for fetching the output rows of `SELECT` statements. The result of a non-`SELECT` statement (e.g., `UPDATE, DELETE, CREATE, ALTER`, ...) is defined as the number of rows affected (this seems to be common among RDBMS). `commit` : commits pending transaction (optional). `rollback` : undoes current transaction (optional). `callProc` : invokes a stored procedure in the RDBMS (tentative). Stored procedures are *not* part of the ANSI SQL-92 standard and possibly vary substantially from one RDBMS to another. For instance, Oracle seems to have a fairly decent implementation of stored procedures, but MySQL currently does not support them. `dbExec` : submit an SQL “script” (multiple statements). May be implemented by looping with `dbExecStatement`. `dbNextResultSet` : When running SQL scripts (multiple statements), it closes the current result set in the `dbConnection`, executes the next statement and returns its result set. ### Class `dbResult` {#sec:dbResult} This virtual class describes the result of an SQL statement (any statement) and the state of the operation. Non-query statements (e.g., `CREATE`, `UPDATE`, `DELETE`) set the “completed” state to 1, while `SELECT` statements to 0. Error conditions set this slot to a negative number. The `dbResult` class defines the following methods: `getStatement` : returns the SQL statement associated with the result set. `getDBConnection` : returns the `dbConnection` associated with the result set. `getRowsAffected` : returns the number of rows affected by the operation. `hasCompleted` : was the operation completed? `SELECT`’s, for instance, are not completed until their output rows are all fetched. `getException` : returns the status of the last SQL statement on a given connection as a list with two members, status code and status description. ### Class `dbResultSet` {#sec:dbResultSet} This virtual class extends `dbResult`, and it describes additional information from the result of a `SELECT` statement and the state of the operation. The `completed` state is set to 0 so long as there are pending rows to fetch. The `dbResultSet` class defines the following additional methods: `getRowCount` : returns the number of rows fetched so far. `getNullOk` : returns a logical vector with as many elements as there are fields in the result set, each element describing whether the corresponding field accepts `NULL` values. `getFields` : describes the `SELECT`ed fields. The description includes field names, RDBMS internal data types, internal length, internal precision and scale, null flag (i.e., column allows `NULL`’s), and corresponding S classes (which can be over-ridden with user-provided classes). The current MySQL and Oracle implementations define a `dbResultSet` as a named list with the following elements: `connection`: : the connection object associated with this result set; `statement`: : a string with the SQL statement being processed; `description`: : a field description `data.frame` with as many rows as there are fields in the `SELECT` output, and columns specifying the `name`, `type`, `length`, `precision`, `scale`, `Sclass` of the corresponding output field. `rowsAffected`: : the number of rows that were affected; `rowCount`: : the number of rows so far fetched; `completed`: : a logical value describing whether the operation has completed or not. `nullOk`: : a logical vector specifying whether the corresponding column may take NULL values. The methods above are implemented as accessor functions to this list in the obvious way. `setDataMappings` : defines a conversion between internal RDBMS data types and R/S classes. We expect the default mappings to be by far the most common ones, but users that need more control may specify a class generator for individual fields in the result set. (See Section [sec:mappings] for details.) `close` : closes the result set and frees resources both in R/S and the RDBMS. `fetch` : extracts the next `max.rec` records (-1 means all). ## Data Type Mappings {#sec:mappings} The data types supported by databases are slightly different than the data types in R and S, but the mapping between them is straightforward: Any of the many fixed and varying length character types are mapped to R/S `character`. Fixed-precision (non-IEEE) numbers are mapped into either doubles (`numeric`) or long (`integer`). Dates are mapped to character using the appropriate `TO_CHAR` function in the RDBMS (which should take care of any locale information). Some RDBMS support the type `CURRENCY` or `MONEY` which should be mapped to `numeric`. Large objects (character, binary, file, etc.) also need to be mapped. User-defined functions may be specified to do the actual conversion as follows: 1. run the query (either with `dbExec` or `dbExecStatement`): > rs <- dbExecStatement(con, "select whatever-You-need") 2. extract the output field definitions > flds <- getFields(rs) 3. replace the class generator in the, say 3rd field, by the user own generator: > flds[3, "Sclass"] # default mapping [1] "character" by > flds[3, "Sclass"] <- "myOwnGeneratorFunction" 4. set the new data mapping prior to fetching > setDataMappings(resutlSet, flds) 5. fetch the rows and store in a `data.frame` > data <- fetch(resultSet) ## Open Issues {#sec:open-issues} We may need to provide some additional utilities, for instance to convert dates, to escape characters such as quotes and slashes in query strings, to strip excessive blanks from some character fields, etc. We need to decide whether we provide hooks so these conversions are done at the C level, or do all the post-processing in R or S. Another issue is what kind of data object is the output of an SQL query. Currently the MySQL and Oracle implementations return data as a `data.frame`; data frames have the slight inconvenience that they automatically re-label the fields according to R/S syntax, changing the actual RDBMS labels of the variables; the issue of non-numeric data being coerced into factors automatically “at the drop of a hat” (as someone in s-news wrote) is also annoying. The execution of SQL scripts is not fully described. The method that executes scripts could run individual statements without returning until it encounters a query (`SELECT`-like) statement. At that point it could return that one result set. The application is then responsible for fetching these rows, and then for invoking `dbNextResultSet` on the opened `dbConnection` object to repeat the `dbExec`/`fetch` loop until it encounters the next `dbResultSet`. And so on. Another (potentially very expensive) alternative would be to run all statements sequentially and return a list of `data.frame`s, each element of the list storing the result of each statement. Binary objects and large objects present some challenges both to R and S. It is becoming more common to store images, sounds, and other data types as binary objects in RDBMS, some of which can be in principle quite large. The SQL-92 ANSI standard allows up to 2 gigabytes for some of these objects. We need to carefully plan how to deal with binary objects – perhaps tentatively not in full generality. Large objects could be fetched by repeatedly invoking a specified R/S function that takes as argument chunks of a specified number of raw bytes. In the case of S4 (and Splus5.x) the RS-DBI implementation can write into an opened connection for which the user has defined a reader (but can we guarantee that we won’t overflow the connection?). In the case of R it is not clear what data type binary large objects (BLOB) should be mapped into. ## Limitations {#sec:limitations} These are some of the limitations of the current interface definition: - we only allow one SQL statement at a time, forcing users to split SQL scripts into individual statements; - transaction management is not fully described; - the interface is heavily biased towards queries, as opposed to general purpose database development. In particular we made no attempt to define “bind variables”; this is a mechanism by which the contents of S objects are implicitly moved to the database during SQL execution. For instance, the following embedded SQL statement /* SQL */ SELECT * from emp_table where emp_id = :sampleEmployee would take the vector `sampleEmployee` and iterate over each of its elements to get the result. Perhaps RS-DBI could at some point in the future implement this feature. # Other Approaches The high-level, front-end description of RS-DBI is the more critical aspect of the interface. Details on how to actually implement this interface may change over time. The approach described in this document based on one back-end driver per RDBMS is reasonable, but not the only approach – we simply felt that a simpler approach based on well-understood and self-contained tools (R, S, and C API’s) would be a better start. Nevertheless we want to briefly mention a few alternatives that we considered and tentatively decided against, but may quite possibly re-visit in the near future. ## Open Database Connectivity (ODBC) {#sec:odbc} The ODBC protocol was developed by Microsoft to allow connectivity among C/C++ applications and RDBMS. As you would expect, originally implementations of the ODBC were only available under Windows environments. There are various effort to create a Unix implementation (see [the Unix ODBC](https://www.unixodbc.org/) web-site and @odbc.lj). This approach looks promising because it allows us to write only one back-end, instead of one per RDBMS. Since most RDBMS already provide ODBC drivers, this could greatly simplify development. Unfortunately, the Unix implementation of ODBC was not mature enough at the time we looked at it, a situation we expect will change in the next year or so. At that point we will need to re-evaluate it to make sure that such an ODBC interface does not penalize the interface in terms of performance, ease of use, portability among the various Unix versions, etc. ## Java Database Connectivity (JDBC) {#sec:jdbc} Another protocol, the Java database connectivity, is very well-done and supported by just about every RDBMS. The issue with JDBC is that as of today neither S nor R (which are written in C) interfaces cleanly with Java. There are several efforts (some in a quite fairly advanced state) to allow S and R to invoke Java methods. Once this interface is widely available in Splus5x and R we will need to re-visit this issue again and study the performance, usability, etc., of JDBC as a common back-end to the RS-DBI. ## CORBA and a 3-tier Architecture {#sec:corba} Yet another approach is to move the interface to RDBMS out of R and S altogether into a separate system or server that would serve as a proxy between R/S and databases. The communication to this middle-layer proxy could be done through CORBA [@s-corba.98, @corba:siegel.96], Java’s RMI, or some other similar technology. Such a design could be very flexible, but the CORBA facilities both in R and S are not widely available yet, and we do not know whether this will be made available to Splus5 users from MathSoft. Also, my experience with this technology is rather limited. On the other hand, this 3-tier architecture seem to offer the most flexibility to cope with very large distributed databases, not necessarily relational. # Resources {#sec:resources} The latest documentation and software on the RS-DBI was available at www.omegahat.net (link dead now: `https://www.omegahat.net/contrib/RS-DBI/index.html`). The R community has developed interfaces to some databases: [RmSQL](https://cran.r-project.org/src/contrib/Archive/RmSQL/) is an interface to the [mSQL](https://www.hughes.com.au/) database written by Torsten Hothorn; [RPgSQL](https://sites.cns.utexas.edu/keittlab/software-0) is an interface to [PostgreSQL](https://www.postgreSQL.org) and was written by Timothy H. Keitt; [RODBC](https://www.stats.ox.ac.uk/pub/bdr/) is an interface to ODBC, and it was written by [Michael Lapsley](mailto:mlapsley@sthelier.sghms.ac.uk). (For more details on all these see @R.imp-exp.) The are R and S-Plus interfaces to [MySQL](https://dev.mysql.com/) that follow the propose RS-DBI API described here; also, there’s an S-Plus interface SOracle @RS-Oracle to Oracle (we expect to have an R implementation soon.) The idea of a common interface to databases has been successfully implemented in Java’s Database Connectivity (JDBC) ([www.javasoft.com](https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/)), in C through the Open Database Connectivity (ODBC) ([www.unixodbc.org](https://www.unixodbc.org/)), in Python’s Database Application Programming Interface ([www.python.org](https://www.python.org)), and in Perl’s Database Interface ([www.cpan.org](https://www.cpan.org)). # Acknowledgements The R/S database interface came about from suggestions, comments, and discussions with [John M. Chambers](mailto:jmc@research.bell-labs.com) and [Duncan Temple Lang](mailto:duncan@research.bell-labs.com) in the context of the Omega Project for Statistical Computing. [Doug Bates](mailto:bates@stat.wisc.edu) and [Saikat DebRoy](mailto:saikat@stat.wisc.edu) ported (and greatly improved) the first MySQL implementation to R. # The S Version 4 Definitions The following code is meant to serve as a detailed description of the R/S to database interface. We decided to use S4 (instead of R or S version 3) because its clean syntax help us to describe easily the classes and methods that form the RS-DBI, and also to convey the inter-class relationships. ```R ## Define all the classes and methods to be used by an ## implementation of the RS-DataBase Interface. Mostly, ## these classes are virtual and each driver should extend ## them to provide the actual implementation. ## Class: dbManager ## This class identifies the DataBase Management System ## (Oracle, MySQL, Informix, PostgreSQL, etc.) setClass("dbManager", VIRTUAL) setGeneric("load", def = function(dbMgr,...) standardGeneric("load") ) setGeneric("unload", def = function(dbMgr,...) standardGeneric("unload") ) setGeneric("getVersion", def = function(dbMgr,...) standardGeneric("getVersion") ) ## Class: dbConnections ## This class captures a connection to a database instance. setClass("dbConnection", VIRTUAL) setGeneric("dbConnection", def = function(dbMgr, ...) standardGeneric("dbConnection") ) setGeneric("dbConnect", def = function(dbMgr, ...) standardGeneric("dbConnect") ) setGeneric("dbExecStatement", def = function(con, statement, ...) standardGeneric("dbExecStatement") ) setGeneric("dbExec", def = function(con, statement, ...) standardGeneric("dbExec") ) setGeneric("getResultSet", def = function(con, ..) standardGeneric("getResultSet") ) setGeneric("commit", def = function(con, ...) standardGeneric("commit") ) setGeneric("rollback", def = function(con, ...) standardGeneric("rollback") ) setGeneric("callProc", def = function(con, ...) standardGeneric("callProc") ) setMethod("close", signature = list(con="dbConnection", type="missing"), def = function(con, type) NULL ) ## Class: dbResult ## This is a base class for arbitrary results from the RDBMS ## (INSERT, UPDATE, DELETE). SELECTs (and SELECT-like) ## statements produce "dbResultSet" objects, which extend ## dbResult. setClass("dbResult", VIRTUAL) setMethod("close", signature = list(con="dbResult", type="missing"), def = function(con, type) NULL ) ## Class: dbResultSet ## Note that we define a resultSet as the result of a ## SELECT SQL statement. setClass("dbResultSet", "dbResult") setGeneric("fetch", def = function(resultSet,n,...) standardGeneric("fetch") ) setGeneric("hasCompleted", def = function(object, ...) standardGeneric("hasCompleted") ) setGeneric("getException", def = function(object, ...) standardGeneric("getException") ) setGeneric("getDBconnection", def = function(object, ...) standardGeneric("getDBconnection") ) setGeneric("setDataMappings", def = function(resultSet, ...) standardGeneric("setDataMappings") ) setGeneric("getFields", def = function(object, table, dbname, ...) standardGeneric("getFields") ) setGeneric("getStatement", def = function(object, ...) standardGeneric("getStatement") ) setGeneric("getRowsAffected", def = function(object, ...) standardGeneric("getRowsAffected") ) setGeneric("getRowCount", def = function(object, ...) standardGeneric("getRowCount") ) setGeneric("getNullOk", def = function(object, ...) standardGeneric("getNullOk") ) ## Meta-data: setGeneric("getInfo", def = function(object, ...) standardGeneric("getInfo") ) setGeneric("describe", def = function(object, verbose=F, ...) standardGeneric("describe") ) setGeneric("getCurrentDatabase", def = function(object, ...) standardGeneric("getCurrentDatabase") ) setGeneric("getDatabases", def = function(object, ...) standardGeneric("getDatabases") ) setGeneric("getTables", def = function(object, dbname, ...) standardGeneric("getTables") ) setGeneric("getTableFields", def = function(object, table, dbname, ...) standardGeneric("getTableFields") ) setGeneric("getTableIndices", def = function(object, table, dbname, ...) standardGeneric("getTableIndices") ) ``` [^2]: A virtual class allows us to group classes that share some common functionality, e.g., the virtual class “`dbConnection`” groups all the connection implementations by Informix, Ingres, DB/2, Oracle, etc. Although the details will vary from one RDBMS to another, the defining characteristic of these objects is what a virtual class captures. R and S version 3 do not explicitly define virtual classes, but they can easily implement the idea through inheritance. [^3]: The term “database” is sometimes (confusingly) used both to denote the RDBMS, such as Oracle, MySQL, and also to denote a particular database instance under a RDBMS, such as “opto” or “sales” databases under the same RDBMS. DBI/inst/doc/DBI-arrow.Rmd0000644000176200001440000001517214552712323014576 0ustar liggesusers--- title: "Using DBI with Arrow" author: "Kirill Müller" date: "25/12/2023" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{Using DBI with Arrow} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r setup, include=FALSE} library(knitr) opts_chunk$set(echo = TRUE) knitr::opts_chunk$set(error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5")) knit_print.data.frame <- function(x, ...) { print(head(x, 6)) if (nrow(x) > 6) { cat("Showing 6 out of", nrow(x), "rows.\n") } invisible(x) } registerS3method("knit_print", "data.frame", "knit_print.data.frame") ``` ## Who this tutorial is for This tutorial is for you if you want to leverage [Apache Arrow](https://arrow.apache.org/) for accessing and manipulating data on databases. See `vignette("DBI", package = "DBI")` and `vignette("DBI-advanced", package = "DBI")` for tutorials on accessing data using R's data frames instead of Arrow's structures. ## Rationale Apache Arrow is > a cross-language development platform for in-memory analytics, suitable for large and huge data, with support for out-of-memory operation. Arrow is also a data exchange format, the data types covered by Arrow align well with the data types supported by SQL databases. DBI 1.2.0 introduced support for Arrow as a format for exchanging data between R and databases. The aim is to: - accelerate data retrieval and loading, by using fewer costly data conversions; - better support reading and summarizing data from a database that is larger than memory; - provide better type fidelity with workflows centered around Arrow. This allows existing code to be used with Arrow, and it allows new code to be written that is more efficient and more flexible than code that uses R's data frames. The interface is built around the {nanoarrow} R package, with `nanoarrow::as_nanoarrow_array` and `nanoarrow::as_nanoarrow_array_stream` as fundamental data structures. ## New classes and generics DBI 1.2.0 introduces new classes and generics for working with Arrow data: - `dbReadTableArrow()` - `dbWriteTableArrow()` - `dbCreateTableArrow()` - `dbAppendTableArrow()` - `dbGetQueryArrow()` - `dbSendQueryArrow()` - `dbBindArrow()` - `dbFetchArrow()` - `dbFetchArrowChunk()` - `DBIResultArrow-class` - `DBIResultArrowDefault-class` Compatibility is important for DBI, and implementing new generics and classes greatly reduces the risk of breaking existing code. The DBI package comes with a fully functional fallback implementation for all existing DBI backends. The fallback is not improving performance, but it allows existing code to be used with Arrow before switching to a backend with native Arrow support. Backends with native support, like the [adbi](https://adbi.r-dbi.org/) package, implement the new generics and classes for direct support and improved performance. In the remainder of this tutorial, we will demonstrate the new generics and classes using the RSQLite package. SQLite is an in-memory database, this code does not need a database server to be installed and running. ## Prepare We start by setting up a database connection and creating a table with some data, using the original `dbWriteTable()` method. ```{r} library(DBI) con <- dbConnect(RSQLite::SQLite()) data <- data.frame( a = 1:3, b = 4.5, c = "five" ) dbWriteTable(con, "tbl", data) ``` ## Read all rows from a table The `dbReadTableArrow()` method reads all rows from a table into an Arrow stream, similarly to `dbReadTable()`. Arrow objects implement the `as.data.frame()` method, so we can convert the stream to a data frame. ```{r} stream <- dbReadTableArrow(con, "tbl") stream as.data.frame(stream) ``` ## Run queries The `dbGetQueryArrow()` method runs a query and returns the result as an Arrow stream. This stream can be turned into an `arrow::RecordBatchReader` object and processed further, without bringing it into R. ```{r} stream <- dbGetQueryArrow(con, "SELECT COUNT(*) AS n FROM tbl WHERE a < 3") stream path <- tempfile(fileext = ".parquet") arrow::write_parquet(arrow::as_record_batch_reader(stream), path) arrow::read_parquet(path) ``` ## Prepared queries The `dbGetQueryArrow()` method supports prepared queries, using the `params` argument which accepts a data frame or a list. ```{r} params <- data.frame(a = 3L) stream <- dbGetQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a", params = params) as.data.frame(stream) params <- data.frame(a = c(2L, 4L)) # Equivalent to dbBind() stream <- dbGetQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a", params = params) as.data.frame(stream) ``` ## Manual flow For the manual flow, use `dbSendQueryArrow()` to send a query to the database, and `dbFetchArrow()` to fetch the result. This also allows using the new `dbBindArrow()` method to bind data in Arrow format to a prepared query. Result objects must be cleared with `dbClearResult()`. ```{r} rs <- dbSendQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a") in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 1L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 2L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 3L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 1:4L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) dbClearResult(rs) ``` ## Writing data Streams returned by `dbGetQueryArrow()` and `dbReadTableArrow()` can be written to a table using `dbWriteTableArrow()`. ```{r} stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a < 3") dbWriteTableArrow(con, "tbl_new", stream) dbReadTable(con, "tbl_new") ``` ## Appending data For more control over the writing process, use `dbCreateTableArrow()` and `dbAppendTableArrow()`. ```{r} stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a < 3") dbCreateTableArrow(con, "tbl_split", stream) dbAppendTableArrow(con, "tbl_split", stream) stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a >= 3") dbAppendTableArrow(con, "tbl_split", stream) dbReadTable(con, "tbl_split") ``` ## Conclusion Do not forget to disconnect from the database when done. ```{r} dbDisconnect(con) ``` That concludes the major features of DBI's new Arrow interface. For more details on the library functions covered in this tutorial see the DBI specification at `vignette("spec", package = "DBI")`. See the [adbi](https://adbi.r-dbi.org/) package for a backend with native Arrow support, and [nanoarrow](https://github.com/apache/arrow-nanoarrow) and [arrow](https://arrow.apache.org/docs/r/) for packages to work with the Arrow format. DBI/inst/doc/backend.Rmd0000644000176200001440000002414014350241735014432 0ustar liggesusers --- title: "Implementing a new backend" author: "Hadley Wickham, Kirill Müller" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{Implementing a new backend} %\VignetteEngine{knitr::rmarkdown} \usepackage[utf8]{inputenc} --- ```{r, echo = FALSE} library(DBI) knitr::opts_chunk$set(collapse = TRUE, comment = "#>") ``` The goal of this document is to help you implement a new backend for DBI. If you are writing a package that connects a database to R, I highly recommend that you make it DBI compatible because it makes your life easier by spelling out exactly what you need to do. The consistent interface provided by DBI makes it easier for you to implement the package (because you have fewer arbitrary choices to make), and easier for your users (because it follows a familiar pattern). In addition, the `DBItest` package provides test cases which you can easily incorporate in your package. I'll illustrate the process using a fictional database called Kazam. ## Getting started Start by creating a package. It's up to you what to call the package, but following the existing pattern of `RSQLite`, `RMySQL`, `RPostgres` and `ROracle` will make it easier for people to find it. For this example, I'll call my package `RKazam`. A ready-to-use template package is available at https://github.com/r-dbi/RKazam/. You can start by creating a new GitHub repository from this template, or by copying the package code. Rename "Kazam" to your desired name everywhere. The template package already contains dummy implementations for all classes and methods. If you chose to create the package manually, make sure to include in your `DESCRIPTION`: ```yaml Imports: DBI (>= 0.3.0), methods Suggests: DBItest, testthat ``` Importing `DBI` is fine, because your users are not supposed to *attach* your package anyway; the preferred method is to attach `DBI` and use explicit qualification via `::` to access the driver in your package (which needs to be done only once). ## Testing Why testing at this early stage? Because testing should be an integral part of the software development cycle. Test right from the start, add automated tests as you go, finish faster (because tests are automated) while maintaining superb code quality (because tests also check corner cases that you might not be aware of). Don't worry: if some test cases are difficult or impossible to satisfy, or take too long to run, you can just turn them off. Take the time now to head over to the `DBItest` vignette at `vignette("test", package = "DBItest")`. You will find a vast amount of ready-to-use test cases that will help you in the process of implementing your new DBI backend. Add custom tests that are not covered by `DBItest` at your discretion, or enhance `DBItest` and file a pull request if the test is generic enough to be useful for many DBI backends. ## Driver Start by making a driver class which inherits from `DBIDriver`. This class doesn't need to do anything, it's just used to dispatch other generics to the right method. Users don't need to know about this, so you can remove it from the default help listing with `@keywords internal`: ```{r} #' Driver for Kazam database. #' #' @keywords internal #' @export #' @import DBI #' @import methods setClass("KazamDriver", contains = "DBIDriver") ``` The driver class was more important in older versions of DBI, so you should also provide a dummy `dbUnloadDriver()` method. ```{r} #' @export #' @rdname Kazam-class setMethod("dbUnloadDriver", "KazamDriver", function(drv, ...) { TRUE }) ``` If your package needs global setup or tear down, do this in the `.onLoad()` and `.onUnload()` functions. You might also want to add a show method so the object prints nicely: ```{r} setMethod("show", "KazamDriver", function(object) { cat("\n") }) ``` Next create `Kazam()` which instantiates this class. ```{r} #' @export Kazam <- function() { new("KazamDriver") } Kazam() ``` ## Connection Next create a connection class that inherits from `DBIConnection`. This should store all the information needed to connect to the database. If you're talking to a C api, this will include a slot that holds an external pointer. ```{r} #' Kazam connection class. #' #' @export #' @keywords internal setClass("KazamConnection", contains = "DBIConnection", slots = list( host = "character", username = "character", # and so on ptr = "externalptr" ) ) ``` Now you have some of the boilerplate out of the way, you can start work on the connection. The most important method here is `dbConnect()` which allows you to connect to a specified instance of the database. Note the use of `@rdname Kazam`. This ensures that `Kazam()` and the connect method are documented together. ```{r} #' @param drv An object created by \code{Kazam()} #' @rdname Kazam #' @export #' @examples #' \dontrun{ #' db <- dbConnect(RKazam::Kazam()) #' dbWriteTable(db, "mtcars", mtcars) #' dbGetQuery(db, "SELECT * FROM mtcars WHERE cyl == 4") #' } setMethod("dbConnect", "KazamDriver", function(drv, ...) { # ... new("KazamConnection", host = host, ...) }) ``` * Replace `...` with the arguments needed to connect to your database. You'll always need to include `...` in the arguments, even if you don't use it, for compatibility with the generic. * This is likely to be where people first come for help, so the examples should show how to connect to the database, and how to query it. (Obviously these examples won't work yet.) Ideally, include examples that can be run right away (perhaps relying on a publicly hosted database), but failing that surround in `\dontrun{}` so people can at least see the code. Next, implement `show()` and `dbDisconnect()` methods. ## Results Finally, you're ready to implement the meat of the system: fetching results of a query into a data frame. First define a results class: ```{r} #' Kazam results class. #' #' @keywords internal #' @export setClass("KazamResult", contains = "DBIResult", slots = list(ptr = "externalptr") ) ``` Then write a `dbSendQuery()` method. This takes a connection and SQL string as arguments, and returns a result object. Again `...` is needed for compatibility with the generic, but you can add other arguments if you need them. ```{r} #' Send a query to Kazam. #' #' @export #' @examples #' # This is another good place to put examples setMethod("dbSendQuery", "KazamConnection", function(conn, statement, ...) { # some code new("KazamResult", ...) }) ``` Next, implement `dbClearResult()`, which should close the result set and free all resources associated with it: ```{r} #' @export setMethod("dbClearResult", "KazamResult", function(res, ...) { # free resources TRUE }) ``` The hardest part of every DBI package is writing the `dbFetch()` method. This needs to take a result set and (optionally) number of records to return, and create a dataframe. Mapping R's data types to those of your database may require a custom implementation of the `dbDataType()` method for your connection class: ```{r} #' Retrieve records from Kazam query #' @export setMethod("dbFetch", "KazamResult", function(res, n = -1, ...) { ... }) # (optionally) #' Find the database data type associated with an R object #' @export setMethod("dbDataType", "KazamConnection", function(dbObj, obj, ...) { ... }) ``` Next, implement `dbHasCompleted()` which should return a `logical` indicating if there are any rows remaining to be fetched. ```{r} #' @export setMethod("dbHasCompleted", "KazamResult", function(res, ...) { }) ``` With these four methods in place, you can now use the default `dbGetQuery()` to send a query to the database, retrieve results if available and then clean up. Spend some time now making sure this works with an existing database, or relax and let the `DBItest` package do the work for you. ## SQL methods You're now on the home stretch, and can make your wrapper substantially more useful by implementing methods that wrap around variations in SQL across databases: * `dbQuoteString()` and `dbQuoteIdentifer()` are used to safely quote strings and identifiers to avoid SQL injection attacks. Note that the former must be vectorized, but not the latter. * `dbWriteTable()` creates a database table given an R dataframe. I'd recommend using the functions prefixed with `sql` in this package to generate the SQL. These functions are still a work in progress so please let me know if you have problems. * `dbReadTable()`: a simple wrapper around `SELECT * FROM table`. Use `dbQuoteIdentifer()` to safely quote the table name and prevent mismatches between the names allowed by R and the database. * `dbListTables()` and `dbExistsTable()` let you determine what tables are available. If not provided by your database's API, you may need to generate sql that inspects the system tables. * `dbListFields()` shows which fields are available in a given table. * `dbRemoveTable()` wraps around `DROP TABLE`. Start with `SQL::sqlTableDrop()`. * `dbBegin()`, `dbCommit()` and `dbRollback()`: implement these three functions to provide basic transaction support. This functionality is currently not tested in the `DBItest` package. ## Metadata methods There are a lot of extra metadata methods for result sets (and one for the connection) that you might want to implement. They are described in the following. * `dbIsValid()` returns if a connection or a result set is open (`TRUE`) or closed (`FALSE`). All further methods in this section are valid for result sets only. * `dbGetStatement()` returns the issued query as a character value. * `dbColumnInfo()` lists the names and types of the result set's columns. * `dbGetRowCount()` and `dbGetRowsAffected()` returns the number of rows returned or altered in a `SELECT` or `INSERT`/`UPDATE` query, respectively. * `dbBind()` allows using parametrised queries. Take a look at `sqlInterpolate()` and `sqlParseVariables()` if your SQL engine doesn't offer native parametrised queries. ## Full DBI compliance By now, your package should implement all methods defined in the DBI specification. If you want to walk the extra mile, offer a read-only mode that allows your users to be sure that their valuable data doesn't get destroyed inadvertently. DBI/inst/doc/DBI-advanced.html0000644000176200001440000011170714561352215015434 0ustar liggesusers Advanced DBI Usage

Advanced DBI Usage

James Wondrasek, Kirill Müller

17/03/2020

Who this tutorial is for

This tutorial is for you if you need to use a richer set of SQL features such as data manipulation queries, parameterized queries and queries performed using SQL’s transaction features. See vignette("DBI", package = "DBI") for a more basic tutorial covering connecting to DBMS and executing simple queries.

How to run more complex queries using DBI

dbGetQuery() works by calling a number of functions behind the scenes. If you need more control you can manually build your own query, retrieve results at your selected rate, and release the resources involved by calling the same functions.

These functions are:

  • dbSendQuery() sends the SQL query to the DBMS and returns a result object. The query is limited to SELECT statements. If you want to send other statements, such as INSERT, UPDATE, DELETE, etc, use dbSendStatement().
  • dbFetch() is called with the result object returned by dbSendQuery(). It also accepts an argument specifying the number of rows to be returned, e.g. n = 200. If you want to fetch all the rows, use n = -1.
  • dbClearResult() is called when you have finished retrieving data. It releases the resources associated with the result object.
library(DBI)

con <- dbConnect(
  RMariaDB::MariaDB(),
  host = "relational.fit.cvut.cz",
  port = 3306,
  username = "guest",
  password = "relational",
  dbname = "sakila"
)

res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = 'G'")
df <- dbFetch(res, n = 3)
dbClearResult(res)

head(df, 3)

How to read part of a table from a database

If your dataset is large you may want to fetch a limited number of rows at a time. As demonstrated below, this can be accomplished by using a while loop where the function dbHasCompleted() is used to check for ongoing rows, and dbFetch() is used with the n = X argument, specifying how many rows to return on each iteration. Again, we call dbClearResult() at the end to release resources.

res <- dbSendQuery(con, "SELECT * FROM film")
while (!dbHasCompleted(res)) {
  chunk <- dbFetch(res, n = 300)
  print(nrow(chunk))
}
dbClearResult(res)

How to use parameters (safely) in SQL queries

dbSendQuery() can be used with parameterized SQL queries. DBI supports two ways to avoid SQL injection attacks from user-supplied parameters: quoting and parameterized queries.

Quoting

Quoting of parameter values is performed using the function dbQuoteLiteral(), which supports many R data types, including date and time.1

In cases where users may be supplying table or column names to use in the query for data retrieval, those names or identifiers must also be escaped. As there may be DBMS-specific rules for escaping these identifiers, DBI provides the function dbQuoteIdentifier() to generate a safe string representation.

safe_id <- dbQuoteIdentifier(con, "rating")
safe_param <- dbQuoteLiteral(con, "G")

query <- paste0("SELECT title, ", safe_id, " FROM film WHERE ", safe_id, " = ", safe_param)
query

res <- dbSendQuery(con, query)
dbFetch(res)
dbClearResult(res)

The same result can be had by using glue::glue_sql(). It performs the same safe quoting on any variable or R statement appearing between braces within the query string.

id <- "rating"
param <- "G"
query <- glue::glue_sql("SELECT title, {`id`} FROM film WHERE {`id`} = {param}", .con = con)

df <- dbGetQuery(con, query)
head(df, 3)

Parameterized queries

Rather than performing the parameter substitution ourselves, we can push it to the DBMS by including placeholders in the query. Different DBMS use different placeholder schemes, DBI passes through the SQL expression unchanged.

MariaDB uses a question mark (?) as placeholder and expects an unnamed list of parameter values. Other DBMS may use named parameters. We recommend consulting the documentation for the DBMS you are using. As an example, a web search for “mariadb parameterized queries” leads to the documentation for the PREPARE statement which mentions:

Within the statement, “?” characters can be used as parameter markers to indicate where data values are to be bound to the query later when you execute it.

Currently there is no list of which placeholder scheme a particular DBMS supports.

Placeholders only work for literal values. Other parts of the query, e.g. table or column identifiers, still need to be quoted with dbQuoteIdentifier().

For a single set of parameters, the params argument to dbSendQuery() or dbGetQuery() can be used. It takes a list and its members are substituted in order for the placeholders within the query.

params <- list("G")
safe_id <- dbQuoteIdentifier(con, "rating")

query <- paste0("SELECT * FROM film WHERE ", safe_id, " = ?")
query

res <- dbSendQuery(con, query, params = params)
dbFetch(res, n = 3)
dbClearResult(res)

Below is an example query using multiple placeholders with the MariaDB driver. The placeholders are supplied as a list of values ordered to match the position of the placeholders in the query.

q_params <- list("G", 90)
query <- "SELECT title, rating, length FROM film WHERE rating = ? AND length >= ?"

res <- dbSendQuery(con, query, params = q_params)
dbFetch(res, n = 3)
dbClearResult(res)

When you wish to perform the same query with different sets of parameter values, dbBind() is used. There are two ways to use dbBind(). Firstly, it can be used multiple times with same query.

res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = ?")
dbBind(res, list("G"))
dbFetch(res, n = 3)
dbBind(res, list("PG"))
dbFetch(res, n = 3)
dbClearResult(res)

Secondly, dbBind() can be used to execute the same statement with multiple values at once.

res <- dbSendQuery(con, "SELECT * FROM film WHERE rating = ?")
dbBind(res, list(c("G", "PG")))
dbFetch(res, n = 3)
dbClearResult(res)

Use a list of vectors if your query has multiple parameters:

q_params <- list(c("G", "PG"), c(90, 120))
query <- "SELECT title, rating, length FROM film WHERE rating = ? AND length >= ?"

res <- dbSendQuery(con, query, params = q_params)
dbFetch(res, n = 3)
dbClearResult(res)

Always disconnect from the database when done.

dbDisconnect(con)

SQL data manipulation - UPDATE, DELETE and friends

For SQL queries that affect the underlying database, such as UPDATE, DELETE, INSERT INTO, and DROP TABLE, DBI provides two functions. dbExecute() passes the SQL statement to the DBMS for execution and returns the number of rows affected. dbSendStatement() performs in the same manner, but returns a result object. Call dbGetRowsAffected() with the result object to get the count of the affected rows. You then need to call dbClearResult() with the result object afterwards to release resources.

In actuality, dbExecute() is a convenience function that calls dbSendStatement(), dbGetRowsAffected(), and dbClearResult(). You can use these functions if you need more control over the query process.

The subsequent examples use an in-memory SQL database provided by RSQLite::SQLite(), because the remote database used in above examples does not allow writing.

library(DBI)
con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "cars", head(cars, 3))

dbExecute(
  con,
  "INSERT INTO cars (speed, dist) VALUES (1, 1), (2, 2), (3, 3)"
)

rs <- dbSendStatement(
  con,
  "INSERT INTO cars (speed, dist) VALUES (4, 4), (5, 5), (6, 6)"
)
dbGetRowsAffected(rs)
dbClearResult(rs)

dbReadTable(con, "cars")

Do not forget to disconnect from the database at the end.

dbDisconnect(con)

SQL transactions with DBI

DBI allows you to group multiple queries into a single atomic transaction. Transactions are initiated with dbBegin() and either made persistent with dbCommit() or undone with dbRollback(). The example below updates two tables and ensures that either both tables are updated, or no changes are persisted to the database and an error is thrown.

con <- dbConnect(RSQLite::SQLite(), ":memory:")

dbWriteTable(con, "cash", data.frame(amount = 100))
dbWriteTable(con, "account", data.frame(amount = 2000))

withdraw <- function(amount) {
  # All operations must be carried out as logical unit:
  dbExecute(con, "UPDATE cash SET amount = amount + ?", list(amount))
  dbExecute(con, "UPDATE account SET amount = amount - ?", list(amount))
}

withdraw_transacted <- function(amount) {
  # Ensure atomicity
  dbBegin(con)

  # Perform operation
  withdraw(amount)

  # Persist results
  dbCommit(con)
}

withdraw_transacted(300)

After withdrawing 300 credits, the cash is increased and the account is decreased by this amount. The transaction ensures that either both operations succeed, or no change occurs.

dbReadTable(con, "cash")
dbReadTable(con, "account")

We can roll back changes manually if necessary. Do not forget to call dbRollback() in case of error, otherwise the transaction remains open indefinitely.

withdraw_if_funds <- function(amount) {
  dbBegin(con)
  withdraw(amount)
  # Rolling back after detecting negative value on account:
  if (dbReadTable(con, "account")$amount >= 0) {
    dbCommit(con)
    TRUE
  } else {
    message("Insufficient funds")
    dbRollback(con)
    FALSE
  }
}

withdraw_if_funds(5000)
dbReadTable(con, "cash")
dbReadTable(con, "account")

dbWithTransaction() simplifies using transactions. Pass it a connection and the code you want to run as a transaction. It will execute the code and call dbCommit() on success and call dbRollback() if an error is thrown.

withdraw_safely <- function(amount) {
  dbWithTransaction(con, {
    withdraw(amount)
    if (dbReadTable(con, "account")$amount < 0) {
      stop("Error: insufficient funds", call. = FALSE)
    }
  })
}

withdraw_safely(5000)
dbReadTable(con, "cash")
dbReadTable(con, "account")

As usual, do not forget to disconnect from the database when done.

dbDisconnect(con)

Conclusion

That concludes the major features of DBI. For more details on the library functions covered in this tutorial and the vignette("DBI", package = "DBI") introductory tutorial see the DBI specification at vignette("spec", package = "DBI"). If you are after a data manipulation library that works at a higher level of abstraction, check out dplyr. It is a grammar of data manipulation that can work with local dataframes and remote databases and uses DBI under the hood.

  1. An older method, dbQuoteString(), was used to quote string values only. The dbQuoteLiteral() method forwards to dbQuoteString() for character vectors. Users do not need to distinguish between these two cases.↩︎

DBI/inst/doc/DBI.html0000644000176200001440000005277314561352216013701 0ustar liggesusers Introduction to DBI

Introduction to DBI

James Wondrasek, Katharina Brunner, Kirill Müller

27 February 2020

Who this tutorial is for

This tutorial is for you if you want to access or manipulate data in a database that may be on your machine or on a different computer on the internet, and you have found libraries that use a higher level of abstraction, such as dbplyr, are not suitable for your purpose. Depending on what you want to achieve, you may find it useful to have an understanding of SQL before using DBI.

The DBI (DataBase Interface) package provides a simple, consistent interface between R and database management systems (DBMS). Each supported DBMS is supported by its own R package that implements the DBI specification in vignette("spec", package = "DBI").

DBI currently supports about 30 DBMS, including:

For a more complete list of supported DBMS visit https://github.com/r-dbi/backends. You may need to install the package specific to your DBMS.

The functionality currently supported for each of these DBMS’s includes:

  • manage a connection to a database
  • list the tables in a database
  • list the column names in a table
  • read a table into a data frame

For more advanced features, such as parameterized queries, transactions, and more see vignette("DBI-advanced", package = "DBI").

How to connect to a database using DBI

The following code establishes a connection to the Sakila database hosted by the Relational Dataset Repository at https://relational.fit.cvut.cz/dataset/Sakila, lists all tables on the database, and closes the connection. The database represents a fictional movie rental business and includes tables describing films, actors, customers, stores, etc.:

library(DBI)

con <- dbConnect(
  RMariaDB::MariaDB(),
  host = "relational.fit.cvut.cz",
  port = 3306,
  username = "guest",
  password = "relational",
  dbname = "sakila"
)

dbListTables(con)
dbDisconnect(con)

Connections to databases are created using the dbConnect() function. The first argument to the function is the driver for the DBMS you are connecting to. In the example above we are connecting to a MariaDB instance, so we use the RMariaDB::MariaDB() driver. The other arguments depend on the authentication required by the DBMS. In the example host, port, username, password, and dbname are required. See the documentation for the DBMS driver package that you are using for specifics.

The function dbListTables() takes a database connection as its only argument and returns a character vector with all table and view names in the database.

After completing a session with a DBMS, always release the connection with a call to dbDisconnect().

Secure password storage

The above example contains the password in the code, which should be avoided for databases with secured access. One way to use the credentials securely is to store it in your system’s credential store and then query it with the keyring package. The code to connect to the database could then look like this:

con <- dbConnect(
  RMariaDB::MariaDB(),
  host = "relational.fit.cvut.cz",
  port = 3306,
  username = "guest",
  password = keyring::key_get("relational.fit.cvut.cz", "guest"),
  dbname = "sakila"
)

How to retrieve column names for a table

We can list the column names for a table with the function dbListFields(). It takes as arguments a database connection and a table name and returns a character vector of the column names in order.

con <- dbConnect(RMariaDB::MariaDB(), username = "guest", password = "relational", host = "relational.fit.cvut.cz", port = 3306, dbname = "sakila")
dbListFields(con, "film")

Read a table into a data frame

The function dbReadTable() reads an entire table and returns it as a data frame. It is equivalent to the SQL query SELECT * FROM <name>. The columns of the returned data frame share the same names as the columns in the table. DBI and the database backends do their best to coerce data to equivalent R data types.

df <- dbReadTable(con, "film")
head(df, 3)

Read only selected rows and columns into a data frame

To read a subset of the data in a table into a data frame, DBI provides functions to run custom SQL queries and manage the results. For small datasets where you do not need to manage the number of results being returned, the function dbGetQuery() takes a SQL SELECT query to execute and returns a data frame. Below is a basic query that specifies the columns we require (film_id, title and description) and which rows (records) we are interested in. Here we retrieve films released in the year 2006.

df <- dbGetQuery(con, "SELECT film_id, title, description FROM film WHERE release_year = 2006")
head(df, 3)

We could also retrieve movies released in 2006 that are rated “G”. Note that character strings must be quoted. As the query itself is contained within double quotes, we use single quotes around the rating. See dbQuoteLiteral() for programmatically converting arbitrary R values to SQL. This is covered in more detail in vignette("DBI-advanced", package = "DBI").

df <- dbGetQuery(con, "SELECT film_id, title, description FROM film WHERE release_year = 2006 AND rating = 'G'")
head(df, 3)

The equivalent operation using dplyr reconstructs the SQL query using three functions to specify the table (tbl()), the subset of the rows (filter()), and the columns we require (select()). Note that dplyr takes care of the quoting.

library(dplyr)

lazy_df <-
  tbl(con, "film") %>%
  filter(release_year == 2006 & rating == "G") %>%
  select(film_id, title, description)
head(lazy_df, 3)

If you want to perform other data manipulation queries such as UPDATEs and DELETEs, see dbSendStatement() in vignette("DBI-advanced", package = "DBI").

How to end a DBMS session

When finished accessing the DBMS, always close the connection using dbDisconnect().

dbDisconnect(con)

Conclusion

This tutorial has given you the basic techniques for accessing data in any supported DBMS. If you need to work with databases that will not fit in memory, or want to run more complex queries, including parameterized queries, please see vignette("DBI-advanced", package = "DBI").

Further Reading

DBI/inst/doc/backend.R0000644000176200001440000000550214561352216014113 0ustar liggesusers## ----echo = FALSE------------------------------------------------------------- library(DBI) knitr::opts_chunk$set(collapse = TRUE, comment = "#>") ## ----------------------------------------------------------------------------- #' Driver for Kazam database. #' #' @keywords internal #' @export #' @import DBI #' @import methods setClass("KazamDriver", contains = "DBIDriver") ## ----------------------------------------------------------------------------- #' @export #' @rdname Kazam-class setMethod("dbUnloadDriver", "KazamDriver", function(drv, ...) { TRUE }) ## ----------------------------------------------------------------------------- setMethod("show", "KazamDriver", function(object) { cat("\n") }) ## ----------------------------------------------------------------------------- #' @export Kazam <- function() { new("KazamDriver") } Kazam() ## ----------------------------------------------------------------------------- #' Kazam connection class. #' #' @export #' @keywords internal setClass("KazamConnection", contains = "DBIConnection", slots = list( host = "character", username = "character", # and so on ptr = "externalptr" ) ) ## ----------------------------------------------------------------------------- #' @param drv An object created by \code{Kazam()} #' @rdname Kazam #' @export #' @examples #' \dontrun{ #' db <- dbConnect(RKazam::Kazam()) #' dbWriteTable(db, "mtcars", mtcars) #' dbGetQuery(db, "SELECT * FROM mtcars WHERE cyl == 4") #' } setMethod("dbConnect", "KazamDriver", function(drv, ...) { # ... new("KazamConnection", host = host, ...) }) ## ----------------------------------------------------------------------------- #' Kazam results class. #' #' @keywords internal #' @export setClass("KazamResult", contains = "DBIResult", slots = list(ptr = "externalptr") ) ## ----------------------------------------------------------------------------- #' Send a query to Kazam. #' #' @export #' @examples #' # This is another good place to put examples setMethod("dbSendQuery", "KazamConnection", function(conn, statement, ...) { # some code new("KazamResult", ...) }) ## ----------------------------------------------------------------------------- #' @export setMethod("dbClearResult", "KazamResult", function(res, ...) { # free resources TRUE }) ## ----------------------------------------------------------------------------- #' Retrieve records from Kazam query #' @export setMethod("dbFetch", "KazamResult", function(res, n = -1, ...) { ... }) # (optionally) #' Find the database data type associated with an R object #' @export setMethod("dbDataType", "KazamConnection", function(dbObj, obj, ...) { ... }) ## ----------------------------------------------------------------------------- #' @export setMethod("dbHasCompleted", "KazamResult", function(res, ...) { }) DBI/inst/doc/spec.R0000644000176200001440000000022314561352217013452 0ustar liggesusers## ----echo = FALSE------------------------------------------------------------- knitr::asis_output(paste(readLines("spec.md"), collapse = "\n")) DBI/inst/doc/DBI-arrow.R0000644000176200001440000000547114561352215014256 0ustar liggesusers## ----setup, include=FALSE----------------------------------------------------- library(knitr) opts_chunk$set(echo = TRUE) knitr::opts_chunk$set(error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5")) knit_print.data.frame <- function(x, ...) { print(head(x, 6)) if (nrow(x) > 6) { cat("Showing 6 out of", nrow(x), "rows.\n") } invisible(x) } registerS3method("knit_print", "data.frame", "knit_print.data.frame") ## ----------------------------------------------------------------------------- library(DBI) con <- dbConnect(RSQLite::SQLite()) data <- data.frame( a = 1:3, b = 4.5, c = "five" ) dbWriteTable(con, "tbl", data) ## ----------------------------------------------------------------------------- stream <- dbReadTableArrow(con, "tbl") stream as.data.frame(stream) ## ----------------------------------------------------------------------------- stream <- dbGetQueryArrow(con, "SELECT COUNT(*) AS n FROM tbl WHERE a < 3") stream path <- tempfile(fileext = ".parquet") arrow::write_parquet(arrow::as_record_batch_reader(stream), path) arrow::read_parquet(path) ## ----------------------------------------------------------------------------- params <- data.frame(a = 3L) stream <- dbGetQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a", params = params) as.data.frame(stream) params <- data.frame(a = c(2L, 4L)) # Equivalent to dbBind() stream <- dbGetQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a", params = params) as.data.frame(stream) ## ----------------------------------------------------------------------------- rs <- dbSendQueryArrow(con, "SELECT $a AS batch, * FROM tbl WHERE a < $a") in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 1L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 2L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 3L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) in_arrow <- nanoarrow::as_nanoarrow_array(data.frame(a = 1:4L)) dbBindArrow(rs, in_arrow) as.data.frame(dbFetchArrow(rs)) dbClearResult(rs) ## ----------------------------------------------------------------------------- stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a < 3") dbWriteTableArrow(con, "tbl_new", stream) dbReadTable(con, "tbl_new") ## ----------------------------------------------------------------------------- stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a < 3") dbCreateTableArrow(con, "tbl_split", stream) dbAppendTableArrow(con, "tbl_split", stream) stream <- dbGetQueryArrow(con, "SELECT * FROM tbl WHERE a >= 3") dbAppendTableArrow(con, "tbl_split", stream) dbReadTable(con, "tbl_split") ## ----------------------------------------------------------------------------- dbDisconnect(con) DBI/inst/doc/spec.Rmd0000644000176200001440000000177114561335140014000 0ustar liggesusers--- title: "DBI specification" author: "Kirill Müller" output: rmarkdown::html_vignette abstract: > The DBI package defines the generic DataBase Interface for R. The connection to individual DBMS is provided by other packages that import DBI (so-called *DBI backends*). This document formalizes the behavior expected by the methods declared in DBI and implemented by the individual backends. To ensure maximum portability and exchangeability, and to reduce the effort for implementing a new DBI backend, the DBItest package defines a comprehensive set of test cases that test conformance to the DBI specification. This document is derived from comments in the test definitions of the DBItest package. Any extensions or updates to the tests will be reflected in this document. vignette: > %\VignetteIndexEntry{DBI specification} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r echo = FALSE} knitr::asis_output(paste(readLines("spec.md"), collapse = "\n")) ``` DBI/inst/doc/DBI-proposal.html0000644000176200001440000016232414561352216015530 0ustar liggesusers A Common Interface to Relational Databases from R and S – A Proposal

A Common Interface to Relational Databases from R and S – A Proposal

David James

March 16, 2000

For too long S and similar data analysis environments have lacked good interfaces to relational database systems (RDBMS). For the last twenty years or so these RDBMS have evolved into highly optimized client-server systems for data storage and manipulation, and currently they serve as repositories for most of the business, industrial, and research “raw” data that analysts work with. Other analysis packages, such as SAS, have traditionally provided good data connectivity, but S and GNU R have relied on intermediate text files as means of importing data (but see R Data Import/Export (2001) and Using Relational Database Systems with R (2000).) Although this simple approach works well for relatively modest amounts of mostly static data, it does not scale up to larger amounts of data distributed over machines and locations, nor does it scale up to data that is highly dynamic – situations that are becoming increasingly common.

We want to propose a common interface between R/S and RDBMS that would allow users to access data stored on database servers in a uniform and predictable manner irrespective of the database engine. The interface defines a small set of classes and methods similar in spirit to Python’s DB-API, Java’s JDBC, Microsoft’s ODBC, Perl’s DBI, etc., but it conforms to the “whole-object” philosophy so natural in S and R.

Computing with Distributed Data

As data analysts, we are increasingly faced with the challenge of larger data sources distributed over machines and locations; most of these data sources reside in relational database management systems (RDBMS). These relational databases represent a mature client-server distributed technology that we as analysts could be exploiting more that we’ve done in the past. The relational technology provides a well-defined standard, the ANSI SQL-92 X/Open CAE Specification: SQL and RDA (1994), both for defining and manipulating data in a highly optimized fashion from virtually any application.

In contrast, S and Splus have provided somewhat limited tools for coping with the challenges of larger and distributed data sets (Splus does provide an import function to import from databases, but it is quite limited in terms of SQL facilities). The R community has been more resourceful and has developed a number of good libraries for connecting to mSQL, MySQL, PostgreSQL, and ODBC; each library, however, has defined its own interface to each database engine a bit differently. We think it would be to everybody’s advantage to coordinate the definition of a common interface, an effort not unlike those taken in the Python and Perl communities.

The goal of a common, seamless access to distributed data is a modest one in our evolution towards a fully distributed computing environment. We recognize the greater goal of distributed computing as the means to fully integrate diverse systems – not just databases – into a truly flexible analysis environment. Good connectivity to databases, however, is of immediate necessity both in practical terms and as a means to help us transition from monolithic, self-contained systems to those in which computations, not only the data, can be carried out in parallel over a wide number of computers and/or systems Temple Lang (2000). Issues of reliability, security, location transparency, persistence, etc., will be new to most of us and working with distributed data may provide a more gradual change to ease in the ultimate goal of full distributed computing.

A Common Interface

We believe that a common interface to databases can help users easily access data stored in RDBMS. A common interface would describe, in a uniform way, how to connect to RDBMS, extract meta-data (such as list of available databases, tables, etc.) as well as a uniform way to execute SQL statements and import their output into R and S. The current emphasis is on querying databases and not so much in a full low-level interface for database development as in JDBC or ODBC, but unlike these, we want to approach the interface from the “whole-object” perspective J. M. Chambers (1998) so natural to R/S and Python – for instance, by fetching all fields and records simultaneously into a single object.

The basic idea is to split the interface into a front-end consisting of a few classes and generic functions that users invoke and a back-end set of database-specific classes and methods that implement the actual communication. (This is a very well-known pattern in software engineering, and another good verbatim is the device-independent graphics in R/S where graphics functions produce similar output on a variety of different devices, such X displays, Postscript, etc.)

The following verbatim shows the front-end:

> mgr <- dbManager("Oracle")
> con <- dbConnect(mgr, user = "user", passwd = "passwd")
> rs <- dbExecStatement(con,
          "select fld1, fld2, fld3 from MY_TABLE")
> tbls <- fetch(rs, n = 100)
> hasCompleted(rs)
[1] T
> close(rs)
> rs <- dbExecStatement(con,
          "select id_name, q25, q50 from liv2")
> res <- fetch(rs)
> getRowCount(rs)
[1] 73
> close(con)

Such scripts should work with other RDBMS (say, MySQL) by replacing the first line with

> mgr <- dbManager("MySQL")

Interface Classes

The following are the main RS-DBI classes. They need to be extended by individual database back-ends (MySQL, Oracle, etc.)

dbManager

Virtual class1 extended by actual database managers, e.g., Oracle, MySQL, Informix.

dbConnection

Virtual class that captures a connection to a database instance2.

dbResult

Virtual class that describes the result of an SQL statement.

dbResultSet

Virtual class, extends dbResult to fully describe the output of those statements that produce output records, i.e., SELECT (or SELECT-like) SQL statement.

All these classes should implement the methods show, describe, and getInfo:

show

(print in R) prints a one-line identification of the object.

describe

prints a short summary of the meta-data of the specified object (like summary in R/S).

getInfo

takes an object of one of the above classes and a string specifying a meta-data item, and it returns the corresponding information (NULL if unavailable).

> mgr <- dbManager("MySQL")
> getInfo(mgr, "version")
> con <- dbConnect(mgr, ...)
> getInfo(con, "type")

The reason we implement the meta-data through getInfo in this way is to simplify the writing of database back-ends. We don’t want to overwhelm the developers of drivers (ourselves, most likely) with hundreds of methods as in the case of JDBC.

In addition, the following methods should also be implemented:

getDatabases

lists all available databases known to the dbManager.

getTables

lists tables in a database.

getTableFields

lists the fields in a table in a database.

getTableIndices

lists the indices defined for a table in a database.

These methods may be implemented using the appropriate getInfo method above.

In the next few sections we describe in detail each of these classes and their methods.

Class dbManager

This class identifies the relational database management system. It needs to be extended by individual back-ends (Oracle, PostgreSQL, etc.) The dbManager class defines the following methods:

load

initializes the driver code. We suggest having the generator, dbManager(driver), automatically load the driver.

unload

releases whatever resources the driver is using.

getVersion

returns the version of the RS-DBI currently implemented, plus any other relevant information about the implementation itself and the RDBMS being used.

Class dbConnection

This virtual class captures a connection to a RDBMS, and it provides access to dynamic SQL, result sets, RDBMS session management (transactions), etc. Note that the dbManager may or may not allow multiple simultaneous connections. The methods it defines include:

dbConnect

opens a connection to the database dbname. Other likely arguments include host, user, and password. It returns an object that extends dbConnection in a driver-specific manner (e.g., the MySQL implementation creates a connection of class MySQLConnection that extends dbConnection). Note that we could separate the steps of connecting to a RDBMS and opening a database there (i.e., opening an instance). For simplicity we do the 2 steps in this method. If the user needs to open another instance in the same RDBMS, just open a new connection.

close

closes the connection and discards all pending work.

dbExecStatement

submits one SQL statement. It returns a dbResult object, and in the case of a SELECT statement, the object also inherits from dbResultSet. This dbResultSet object is needed for fetching the output rows of SELECT statements. The result of a non-SELECT statement (e.g., UPDATE, DELETE, CREATE, ALTER, …) is defined as the number of rows affected (this seems to be common among RDBMS).

commit

commits pending transaction (optional).

rollback

undoes current transaction (optional).

callProc

invokes a stored procedure in the RDBMS (tentative). Stored procedures are not part of the ANSI SQL-92 standard and possibly vary substantially from one RDBMS to another. For instance, Oracle seems to have a fairly decent implementation of stored procedures, but MySQL currently does not support them.

dbExec

submit an SQL “script” (multiple statements). May be implemented by looping with dbExecStatement.

dbNextResultSet

When running SQL scripts (multiple statements), it closes the current result set in the dbConnection, executes the next statement and returns its result set.

Class dbResult

This virtual class describes the result of an SQL statement (any statement) and the state of the operation. Non-query statements (e.g., CREATE, UPDATE, DELETE) set the “completed” state to 1, while SELECT statements to 0. Error conditions set this slot to a negative number. The dbResult class defines the following methods:

getStatement

returns the SQL statement associated with the result set.

getDBConnection

returns the dbConnection associated with the result set.

getRowsAffected

returns the number of rows affected by the operation.

hasCompleted

was the operation completed? SELECT’s, for instance, are not completed until their output rows are all fetched.

getException

returns the status of the last SQL statement on a given connection as a list with two members, status code and status description.

Class dbResultSet

This virtual class extends dbResult, and it describes additional information from the result of a SELECT statement and the state of the operation. The completed state is set to 0 so long as there are pending rows to fetch. The dbResultSet class defines the following additional methods:

getRowCount

returns the number of rows fetched so far.

getNullOk

returns a logical vector with as many elements as there are fields in the result set, each element describing whether the corresponding field accepts NULL values.

getFields

describes the SELECTed fields. The description includes field names, RDBMS internal data types, internal length, internal precision and scale, null flag (i.e., column allows NULL’s), and corresponding S classes (which can be over-ridden with user-provided classes). The current MySQL and Oracle implementations define a dbResultSet as a named list with the following elements:

connection:

the connection object associated with this result set;

statement:

a string with the SQL statement being processed;

description:

a field description data.frame with as many rows as there are fields in the SELECT output, and columns specifying the name, type, length, precision, scale, Sclass of the corresponding output field.

rowsAffected:

the number of rows that were affected;

rowCount:

the number of rows so far fetched;

completed:

a logical value describing whether the operation has completed or not.

nullOk:

a logical vector specifying whether the corresponding column may take NULL values.

The methods above are implemented as accessor functions to this list in the obvious way.

setDataMappings

defines a conversion between internal RDBMS data types and R/S classes. We expect the default mappings to be by far the most common ones, but users that need more control may specify a class generator for individual fields in the result set. (See Section [sec:mappings] for details.)

close

closes the result set and frees resources both in R/S and the RDBMS.

fetch

extracts the next max.rec records (-1 means all).

Data Type Mappings

The data types supported by databases are slightly different than the data types in R and S, but the mapping between them is straightforward: Any of the many fixed and varying length character types are mapped to R/S character. Fixed-precision (non-IEEE) numbers are mapped into either doubles (numeric) or long (integer). Dates are mapped to character using the appropriate TO_CHAR function in the RDBMS (which should take care of any locale information). Some RDBMS support the type CURRENCY or MONEY which should be mapped to numeric. Large objects (character, binary, file, etc.) also need to be mapped. User-defined functions may be specified to do the actual conversion as follows:

  1. run the query (either with dbExec or dbExecStatement):

    > rs <- dbExecStatement(con, "select whatever-You-need")

  2. extract the output field definitions

    > flds <- getFields(rs)

  3. replace the class generator in the, say 3rd field, by the user own generator:

    > flds[3, "Sclass"]            # default mapping
[1] "character"

    by

    > flds[3, "Sclass"] <- "myOwnGeneratorFunction"

  4. set the new data mapping prior to fetching

    > setDataMappings(resutlSet, flds)

  5. fetch the rows and store in a data.frame

    > data <- fetch(resultSet)

Open Issues

We may need to provide some additional utilities, for instance to convert dates, to escape characters such as quotes and slashes in query strings, to strip excessive blanks from some character fields, etc. We need to decide whether we provide hooks so these conversions are done at the C level, or do all the post-processing in R or S.

Another issue is what kind of data object is the output of an SQL query. Currently the MySQL and Oracle implementations return data as a data.frame; data frames have the slight inconvenience that they automatically re-label the fields according to R/S syntax, changing the actual RDBMS labels of the variables; the issue of non-numeric data being coerced into factors automatically “at the drop of a hat” (as someone in s-news wrote) is also annoying.

The execution of SQL scripts is not fully described. The method that executes scripts could run individual statements without returning until it encounters a query (SELECT-like) statement. At that point it could return that one result set. The application is then responsible for fetching these rows, and then for invoking dbNextResultSet on the opened dbConnection object to repeat the dbExec/fetch loop until it encounters the next dbResultSet. And so on. Another (potentially very expensive) alternative would be to run all statements sequentially and return a list of data.frames, each element of the list storing the result of each statement.

Binary objects and large objects present some challenges both to R and S. It is becoming more common to store images, sounds, and other data types as binary objects in RDBMS, some of which can be in principle quite large. The SQL-92 ANSI standard allows up to 2 gigabytes for some of these objects. We need to carefully plan how to deal with binary objects – perhaps tentatively not in full generality. Large objects could be fetched by repeatedly invoking a specified R/S function that takes as argument chunks of a specified number of raw bytes. In the case of S4 (and Splus5.x) the RS-DBI implementation can write into an opened connection for which the user has defined a reader (but can we guarantee that we won’t overflow the connection?). In the case of R it is not clear what data type binary large objects (BLOB) should be mapped into.

Limitations

These are some of the limitations of the current interface definition:

  • we only allow one SQL statement at a time, forcing users to split SQL scripts into individual statements;

  • transaction management is not fully described;

  • the interface is heavily biased towards queries, as opposed to general purpose database development. In particular we made no attempt to define “bind variables”; this is a mechanism by which the contents of S objects are implicitly moved to the database during SQL execution. For instance, the following embedded SQL statement

      /* SQL */
  SELECT * from emp_table where emp_id = :sampleEmployee

    would take the vector sampleEmployee and iterate over each of its elements to get the result. Perhaps RS-DBI could at some point in the future implement this feature.

Other Approaches

The high-level, front-end description of RS-DBI is the more critical aspect of the interface. Details on how to actually implement this interface may change over time. The approach described in this document based on one back-end driver per RDBMS is reasonable, but not the only approach – we simply felt that a simpler approach based on well-understood and self-contained tools (R, S, and C API’s) would be a better start. Nevertheless we want to briefly mention a few alternatives that we considered and tentatively decided against, but may quite possibly re-visit in the near future.

Open Database Connectivity (ODBC)

The ODBC protocol was developed by Microsoft to allow connectivity among C/C++ applications and RDBMS. As you would expect, originally implementations of the ODBC were only available under Windows environments. There are various effort to create a Unix implementation (see the Unix ODBC web-site and Harvey (1999)). This approach looks promising because it allows us to write only one back-end, instead of one per RDBMS. Since most RDBMS already provide ODBC drivers, this could greatly simplify development. Unfortunately, the Unix implementation of ODBC was not mature enough at the time we looked at it, a situation we expect will change in the next year or so. At that point we will need to re-evaluate it to make sure that such an ODBC interface does not penalize the interface in terms of performance, ease of use, portability among the various Unix versions, etc.

Java Database Connectivity (JDBC)

Another protocol, the Java database connectivity, is very well-done and supported by just about every RDBMS. The issue with JDBC is that as of today neither S nor R (which are written in C) interfaces cleanly with Java. There are several efforts (some in a quite fairly advanced state) to allow S and R to invoke Java methods. Once this interface is widely available in Splus5x and R we will need to re-visit this issue again and study the performance, usability, etc., of JDBC as a common back-end to the RS-DBI.

CORBA and a 3-tier Architecture

Yet another approach is to move the interface to RDBMS out of R and S altogether into a separate system or server that would serve as a proxy between R/S and databases. The communication to this middle-layer proxy could be done through CORBA Siegel (1996), Java’s RMI, or some other similar technology. Such a design could be very flexible, but the CORBA facilities both in R and S are not widely available yet, and we do not know whether this will be made available to Splus5 users from MathSoft. Also, my experience with this technology is rather limited.

On the other hand, this 3-tier architecture seem to offer the most flexibility to cope with very large distributed databases, not necessarily relational.

Resources

The latest documentation and software on the RS-DBI was available at www.omegahat.net (link dead now: https://www.omegahat.net/contrib/RS-DBI/index.html). The R community has developed interfaces to some databases: RmSQL is an interface to the mSQL database written by Torsten Hothorn; RPgSQL is an interface to PostgreSQL and was written by Timothy H. Keitt; RODBC is an interface to ODBC, and it was written by Michael Lapsley. (For more details on all these see R Data Import/Export (2001).)

The are R and S-Plus interfaces to MySQL that follow the propose RS-DBI API described here; also, there’s an S-Plus interface SOracle James (In preparation) to Oracle (we expect to have an R implementation soon.)

The idea of a common interface to databases has been successfully implemented in Java’s Database Connectivity (JDBC) (www.javasoft.com), in C through the Open Database Connectivity (ODBC) (www.unixodbc.org), in Python’s Database Application Programming Interface (www.python.org), and in Perl’s Database Interface (www.cpan.org).

Acknowledgements

The R/S database interface came about from suggestions, comments, and discussions with John M. Chambers and Duncan Temple Lang in the context of the Omega Project for Statistical Computing. Doug Bates and Saikat DebRoy ported (and greatly improved) the first MySQL implementation to R.

The S Version 4 Definitions

The following code is meant to serve as a detailed description of the R/S to database interface. We decided to use S4 (instead of R or S version 3) because its clean syntax help us to describe easily the classes and methods that form the RS-DBI, and also to convey the inter-class relationships.

## Define all the classes and methods to be used by an
## implementation of the RS-DataBase Interface.  Mostly,
## these classes are virtual and each driver should extend
## them to provide the actual implementation.

## Class: dbManager
## This class identifies the DataBase Management System
## (Oracle, MySQL, Informix, PostgreSQL, etc.)

setClass("dbManager", VIRTUAL)

setGeneric("load",
   def = function(dbMgr,...)
   standardGeneric("load")
   )
setGeneric("unload",
   def = function(dbMgr,...)
   standardGeneric("unload")
   )
setGeneric("getVersion",
   def = function(dbMgr,...)
   standardGeneric("getVersion")
   )

## Class: dbConnections
## This class captures a connection to a database instance.

setClass("dbConnection", VIRTUAL)

setGeneric("dbConnection",
   def = function(dbMgr, ...)
   standardGeneric("dbConnection")
   )
setGeneric("dbConnect",
   def = function(dbMgr, ...)
   standardGeneric("dbConnect")
   )
setGeneric("dbExecStatement",
   def = function(con, statement, ...)
   standardGeneric("dbExecStatement")
   )
setGeneric("dbExec",
   def = function(con, statement, ...)
   standardGeneric("dbExec")
   )
setGeneric("getResultSet",
   def = function(con, ..)
   standardGeneric("getResultSet")
   )
setGeneric("commit",
   def = function(con, ...)
   standardGeneric("commit")
   )
setGeneric("rollback",
   def = function(con, ...)
   standardGeneric("rollback")
   )
setGeneric("callProc",
   def = function(con, ...)
   standardGeneric("callProc")
   )
setMethod("close",
   signature = list(con="dbConnection", type="missing"),
   def = function(con, type) NULL
   )

## Class: dbResult
## This is a base class for arbitrary results from the RDBMS
## (INSERT, UPDATE, DELETE).  SELECTs (and SELECT-like)
## statements produce "dbResultSet" objects, which extend
## dbResult.

setClass("dbResult", VIRTUAL)

setMethod("close",
   signature = list(con="dbResult", type="missing"),
   def = function(con, type) NULL
   )

## Class: dbResultSet
## Note that we define a resultSet as the result of a
## SELECT  SQL statement.

setClass("dbResultSet", "dbResult")

setGeneric("fetch",
   def = function(resultSet,n,...)
   standardGeneric("fetch")
   )
setGeneric("hasCompleted",
   def = function(object, ...)
   standardGeneric("hasCompleted")
   )
setGeneric("getException",
   def = function(object, ...)
   standardGeneric("getException")
   )
setGeneric("getDBconnection",
   def = function(object, ...)
   standardGeneric("getDBconnection")
   )
setGeneric("setDataMappings",
   def = function(resultSet, ...)
   standardGeneric("setDataMappings")
   )
setGeneric("getFields",
   def = function(object, table, dbname,  ...)
   standardGeneric("getFields")
   )
setGeneric("getStatement",
   def = function(object, ...)
   standardGeneric("getStatement")
   )
setGeneric("getRowsAffected",
   def = function(object, ...)
   standardGeneric("getRowsAffected")
   )
setGeneric("getRowCount",
   def = function(object, ...)
   standardGeneric("getRowCount")
   )
setGeneric("getNullOk",
   def = function(object, ...)
   standardGeneric("getNullOk")
   )

## Meta-data:
setGeneric("getInfo",
   def = function(object, ...)
   standardGeneric("getInfo")
   )
setGeneric("describe",
   def = function(object, verbose=F, ...)
   standardGeneric("describe")
   )
setGeneric("getCurrentDatabase",
   def = function(object, ...)
   standardGeneric("getCurrentDatabase")
   )
setGeneric("getDatabases",
   def = function(object, ...)
   standardGeneric("getDatabases")
   )
setGeneric("getTables",
   def = function(object, dbname, ...)
   standardGeneric("getTables")
   )
setGeneric("getTableFields",
   def = function(object, table, dbname, ...)
   standardGeneric("getTableFields")
   )
setGeneric("getTableIndices",
   def = function(object, table, dbname, ...)
   standardGeneric("getTableIndices")
   )
Chambers, J. M. 1998. Programming with Data: A Guide to the s Language. New York: Springer.
Chambers, John M., Mark H. Hansen, David A. James, and Duncan Temple Lang. 1998. “Distributed Computing with Data: A CORBA-Based Approach.” In Computing Science and Statistics. Inteface Foundation of North America.
Harvey, Peter. 1999. “Open Database Connectivity.” Linux Journal Nov. (67): 68–72.
James, David A. In preparation. “An R/S Interface to the Oracle Database.” www.omegahat.org: Bell Labs, Lucent Technologies.
R Data Import/Export. 2001. R-Development Core Team.
Siegel, Jon. 1996. CORBA Fundamentals and Programming. New York: Wiley.
Temple Lang, Duncan. 2000. “The Omegahat Environment: New Possibilities for Statistical Computing.” Journal of Computational and Graphical Statistics to appear.
Using Relational Database Systems with R. 2000. R-Developemt Core Team.
X/Open CAE Specification: SQL and RDA. 1994. Reading, UK: X/Open Company Ltd.

  1. A virtual class allows us to group classes that share some common functionality, e.g., the virtual class “dbConnection” groups all the connection implementations by Informix, Ingres, DB/2, Oracle, etc. Although the details will vary from one RDBMS to another, the defining characteristic of these objects is what a virtual class captures. R and S version 3 do not explicitly define virtual classes, but they can easily implement the idea through inheritance.↩︎

  2. The term “database” is sometimes (confusingly) used both to denote the RDBMS, such as Oracle, MySQL, and also to denote a particular database instance under a RDBMS, such as “opto” or “sales” databases under the same RDBMS.↩︎

DBI/inst/doc/DBI-history.Rmd0000644000176200001440000001221414552712157015144 0ustar liggesusers--- title: "History of DBI" author: "David James" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{History of DBI} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- The following history of DBI was contributed by David James, the driving force behind the development of DBI, and many of the packages that implement it. The idea/work of interfacing S (originally S3 and S4) to RDBMS goes back to the mid- and late 1990's in Bell Labs. The first toy interface I did was to implement John Chamber's early concept of "Data Management in S" (1991). The implementation followed that interface pretty closely and immediately showed some of the limitations when dealing with very large databases; if my memory serves me, the issue was the instance-based of the language back then, e.g., if you attached an RDBMS to the `search()` path and then needed to resolve a symbol "foo", you effectively had to bring all the objects in the database to check their mode/class, i.e., the instance object had the metadata in itself as attributes. The experiment showed that the S3 implementation of "data management" was not really suitable to large external RDBMS (probably it was never intended to do that anyway). (Note however, that since then, John and Duncan Temple Lang generalized the data management in S4 a lot, including Duncan's implementation in his RObjectTables package where he considered a lot of synchronization/caching issues relevant to DBI and, more generally, to most external interfaces). Back then we were working very closely with Lucent's microelectronics manufacturing --- our colleagues there had huge Oracle (mostly) databases that we needed to constantly query via [SQL*Plus](https://en.wikipedia.org/wiki/SQL*Plus). My colleague Jake Luciani was developing advanced applications in C and SQL, and the two of us came up with the first implementation of S3 directly connecting with Oracle. What I remember is that the Linux [PRO*C](https://en.wikipedia.org/wiki/Pro*C) pre-compiler (that embedded SQL in C code) was very buggy --- we spent a lot of time looking for workarounds and tricks until we got the C interface running. At the time, other projects within Bell Labs began using MySQL, and we moved to MySQL (with the help of Doug Bates' student Saikat DebRoy, then a summer intern) with no intentions of looking back at the very difficult Oracle interface. It was at this time that I moved all the code from S3 methods to S4 classes and methods and begun reaching out to the S/R community for suggestions, ideas, etc. All (most) of this work was on Bell Labs versions of S3 and S4, but I made sure it worked with S-Plus. At some point around 2000 (I don't remember exactly when), I ported all the code to R regressing to S3 methods, and later on (once S4 classes and methods were available in R) I re-implemented everything back to S4 classes and methods in R (a painful back-and-forth). It was at this point that I decided to drop S-Plus altogether. Around that time, I came across a very early implementation of SQLite and I was quite interested and thought it was a very nice RDBMS that could be used for all kinds of experimentation, etc., so it was pretty easy to implement on top of the DBI. Within the R community, there were quite a number of people that showed interest on defining a common interface to databases, but only a few folks actually provided code/suggestions/etc. (Tim Keitt was most active with the dbi/PostgreSQL packages --- he also was considering what he called "proxy" objects, which was reminiscent of what Duncan had been doing). Kurt Hornick, Vincent Carey, Robert Gentleman, and others provided suggestions/comments/support for the DBI definition. By around 2003, the DBI was more or less implemented as it is today. I'm sure I'll forget some (most should be in the THANKS sections of the various packages), but the names that come to my mind at this moment are Jake Luciani (ROracle), Don MacQueen and other early ROracle users (super helpful), Doug Bates and his student Saikat DebRoy for RMySQL, Fei Chen (at the time a student of Prof. Ripley) also contributed to RMySQL, Tim Keitt (working on an early S3 interface to PostgrSQL), Torsten Hothorn (worked with mSQL and also MySQL), Prof. Ripley working/extending the RODBC package, in addition to John Chambers and Duncan Temple-Lang who provided very important comments and suggestions. Actually, the real impetus behind the DBI was always to do distributed statistical computing --- *not* to provide a yet-another import/export mechanism --- and this perspective was driven by John and Duncan's vision and work on inter-system computing, COM, CORBA, etc. I'm not sure many of us really appreciated (even now) the full extent of those ideas and concepts. Just like in other languages (C's ODBC, Java's JDBC, Perl's DBI/DBD, Python dbapi), R/S DBI was meant to unify the interfacing to RDBMS so that R/S applications could be developed on top of the DBI and not be hard coded to any one relation database. The interface I tried to follow the closest was the Python's DBAPI --- I haven't worked on this topic for a while, but I still feel Python's DBAPI is the cleanest and most relevant for the S language. DBI/inst/doc/DBI.Rmd0000644000176200001440000001632614552712323013450 0ustar liggesusers--- title: "Introduction to DBI" author: "James Wondrasek, Katharina Brunner, Kirill Müller" date: "27 February 2020" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{Introduction to DBI} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r setup, include=FALSE} knitr::opts_chunk$set( echo = TRUE, error = Sys.getenv("IN_PKGDOWN") != "true" || (getRversion() < "3.5"), # FIXME: Bring back when relational.fit clone is up eval = FALSE ) ``` ## Who this tutorial is for This tutorial is for you if you want to access or manipulate data in a database that may be on your machine or on a different computer on the internet, and you have found libraries that use a higher level of abstraction, such as [dbplyr](https://dbplyr.tidyverse.org/), are not suitable for your purpose. Depending on what you want to achieve, you may find it useful to have an understanding of SQL before using DBI. The DBI (**D**ata**B**ase **I**nterface) package provides a simple, consistent interface between R and database management systems (DBMS). Each supported DBMS is supported by its own R package that implements the DBI specification in `vignette("spec", package = "DBI")`. DBI currently supports about 30 DBMS, including: * MySQL, using the R-package [RMySQL](https://github.com/r-dbi/RMySQL) * MariaDB, using the R-package [RMariaDB](https://github.com/r-dbi/RMariaDB) * Postgres, using the R-package [RPostgres](https://github.com/r-dbi/RPostgres) * SQLite, using the R-package [RSQLite](https://github.com/r-dbi/RSQLite) For a more complete list of supported DBMS visit [https://github.com/r-dbi/backends](https://github.com/r-dbi/backends#readme). You may need to install the package specific to your DBMS. The functionality currently supported for each of these DBMS's includes: - manage a connection to a database - list the tables in a database - list the column names in a table - read a table into a data frame For more advanced features, such as parameterized queries, transactions, and more see `vignette("DBI-advanced", package = "DBI")`. ## How to connect to a database using DBI The following code establishes a connection to the Sakila database hosted by the Relational Dataset Repository at `https://relational.fit.cvut.cz/dataset/Sakila`, lists all tables on the database, and closes the connection. The database represents a fictional movie rental business and includes tables describing films, actors, customers, stores, etc.: ```{r} library(DBI) con <- dbConnect( RMariaDB::MariaDB(), host = "relational.fit.cvut.cz", port = 3306, username = "guest", password = "relational", dbname = "sakila" ) dbListTables(con) dbDisconnect(con) ``` Connections to databases are created using the `dbConnect()` function. The first argument to the function is the driver for the DBMS you are connecting to. In the example above we are connecting to a MariaDB instance, so we use the `RMariaDB::MariaDB()` driver. The other arguments depend on the authentication required by the DBMS. In the example host, port, username, password, and dbname are required. See the documentation for the DBMS driver package that you are using for specifics. The function `dbListTables()` takes a database connection as its only argument and returns a character vector with all table and view names in the database. After completing a session with a DBMS, always release the connection with a call to `dbDisconnect()`. ### Secure password storage The above example contains the password in the code, which should be avoided for databases with secured access. One way to use the credentials securely is to store it in your system's credential store and then query it with the [keyring](https://github.com/r-lib/keyring#readme) package. The code to connect to the database could then look like this: ```{r eval = FALSE} con <- dbConnect( RMariaDB::MariaDB(), host = "relational.fit.cvut.cz", port = 3306, username = "guest", password = keyring::key_get("relational.fit.cvut.cz", "guest"), dbname = "sakila" ) ``` ## How to retrieve column names for a table We can list the column names for a table with the function `dbListFields()`. It takes as arguments a database connection and a table name and returns a character vector of the column names in order. ```{r} con <- dbConnect(RMariaDB::MariaDB(), username = "guest", password = "relational", host = "relational.fit.cvut.cz", port = 3306, dbname = "sakila") dbListFields(con, "film") ``` ## Read a table into a data frame The function `dbReadTable()` reads an entire table and returns it as a data frame. It is equivalent to the SQL query `SELECT * FROM `. The columns of the returned data frame share the same names as the columns in the table. DBI and the database backends do their best to coerce data to equivalent R data types. ```{r} df <- dbReadTable(con, "film") head(df, 3) ``` ## Read only selected rows and columns into a data frame To read a subset of the data in a table into a data frame, DBI provides functions to run custom SQL queries and manage the results. For small datasets where you do not need to manage the number of results being returned, the function `dbGetQuery()` takes a SQL `SELECT` query to execute and returns a data frame. Below is a basic query that specifies the columns we require (`film_id`, `title` and `description`) and which rows (records) we are interested in. Here we retrieve films released in the year 2006. ```{r} df <- dbGetQuery(con, "SELECT film_id, title, description FROM film WHERE release_year = 2006") head(df, 3) ``` We could also retrieve movies released in 2006 that are rated "G". Note that character strings must be quoted. As the query itself is contained within double quotes, we use single quotes around the rating. See `dbQuoteLiteral()` for programmatically converting arbitrary R values to SQL. This is covered in more detail in `vignette("DBI-advanced", package = "DBI")`. ```{r} df <- dbGetQuery(con, "SELECT film_id, title, description FROM film WHERE release_year = 2006 AND rating = 'G'") head(df, 3) ``` The equivalent operation using `dplyr` reconstructs the SQL query using three functions to specify the table (`tbl()`), the subset of the rows (`filter()`), and the columns we require (`select()`). Note that dplyr takes care of the quoting. ```{r message=FALSE} library(dplyr) lazy_df <- tbl(con, "film") %>% filter(release_year == 2006 & rating == "G") %>% select(film_id, title, description) head(lazy_df, 3) ``` If you want to perform other data manipulation queries such as `UPDATE`s and `DELETE`s, see `dbSendStatement()` in `vignette("DBI-advanced", package = "DBI")`. ## How to end a DBMS session When finished accessing the DBMS, always close the connection using `dbDisconnect()`. ```{r} dbDisconnect(con) ``` ## Conclusion This tutorial has given you the basic techniques for accessing data in any supported DBMS. If you need to work with databases that will not fit in memory, or want to run more complex queries, including parameterized queries, please see `vignette("DBI-advanced", package = "DBI")`. ## Further Reading * An overview on [working with databases in R on Rstudio.com](https://db.rstudio.com/) * The DBI specification: `vignette("spec", package = "DBI")` * [List of supported DBMS](https://github.com/r-dbi/backends#readme) DBI/inst/doc/DBI-history.html0000644000176200001440000002332514561352216015367 0ustar liggesusers History of DBI

History of DBI

David James

The following history of DBI was contributed by David James, the driving force behind the development of DBI, and many of the packages that implement it.

The idea/work of interfacing S (originally S3 and S4) to RDBMS goes back to the mid- and late 1990’s in Bell Labs. The first toy interface I did was to implement John Chamber’s early concept of “Data Management in S” (1991). The implementation followed that interface pretty closely and immediately showed some of the limitations when dealing with very large databases; if my memory serves me, the issue was the instance-based of the language back then, e.g., if you attached an RDBMS to the search() path and then needed to resolve a symbol “foo”, you effectively had to bring all the objects in the database to check their mode/class, i.e., the instance object had the metadata in itself as attributes. The experiment showed that the S3 implementation of “data management” was not really suitable to large external RDBMS (probably it was never intended to do that anyway). (Note however, that since then, John and Duncan Temple Lang generalized the data management in S4 a lot, including Duncan’s implementation in his RObjectTables package where he considered a lot of synchronization/caching issues relevant to DBI and, more generally, to most external interfaces).

Back then we were working very closely with Lucent’s microelectronics manufacturing — our colleagues there had huge Oracle (mostly) databases that we needed to constantly query via SQL*Plus. My colleague Jake Luciani was developing advanced applications in C and SQL, and the two of us came up with the first implementation of S3 directly connecting with Oracle. What I remember is that the Linux PRO*C pre-compiler (that embedded SQL in C code) was very buggy — we spent a lot of time looking for workarounds and tricks until we got the C interface running. At the time, other projects within Bell Labs began using MySQL, and we moved to MySQL (with the help of Doug Bates’ student Saikat DebRoy, then a summer intern) with no intentions of looking back at the very difficult Oracle interface. It was at this time that I moved all the code from S3 methods to S4 classes and methods and begun reaching out to the S/R community for suggestions, ideas, etc. All (most) of this work was on Bell Labs versions of S3 and S4, but I made sure it worked with S-Plus. At some point around 2000 (I don’t remember exactly when), I ported all the code to R regressing to S3 methods, and later on (once S4 classes and methods were available in R) I re-implemented everything back to S4 classes and methods in R (a painful back-and-forth). It was at this point that I decided to drop S-Plus altogether. Around that time, I came across a very early implementation of SQLite and I was quite interested and thought it was a very nice RDBMS that could be used for all kinds of experimentation, etc., so it was pretty easy to implement on top of the DBI.

Within the R community, there were quite a number of people that showed interest on defining a common interface to databases, but only a few folks actually provided code/suggestions/etc. (Tim Keitt was most active with the dbi/PostgreSQL packages — he also was considering what he called “proxy” objects, which was reminiscent of what Duncan had been doing). Kurt Hornick, Vincent Carey, Robert Gentleman, and others provided suggestions/comments/support for the DBI definition. By around 2003, the DBI was more or less implemented as it is today.

I’m sure I’ll forget some (most should be in the THANKS sections of the various packages), but the names that come to my mind at this moment are Jake Luciani (ROracle), Don MacQueen and other early ROracle users (super helpful), Doug Bates and his student Saikat DebRoy for RMySQL, Fei Chen (at the time a student of Prof. Ripley) also contributed to RMySQL, Tim Keitt (working on an early S3 interface to PostgrSQL), Torsten Hothorn (worked with mSQL and also MySQL), Prof. Ripley working/extending the RODBC package, in addition to John Chambers and Duncan Temple-Lang who provided very important comments and suggestions.

Actually, the real impetus behind the DBI was always to do distributed statistical computing — not to provide a yet-another import/export mechanism — and this perspective was driven by John and Duncan’s vision and work on inter-system computing, COM, CORBA, etc. I’m not sure many of us really appreciated (even now) the full extent of those ideas and concepts. Just like in other languages (C’s ODBC, Java’s JDBC, Perl’s DBI/DBD, Python dbapi), R/S DBI was meant to unify the interfacing to RDBMS so that R/S applications could be developed on top of the DBI and not be hard coded to any one relation database. The interface I tried to follow the closest was the Python’s DBAPI — I haven’t worked on this topic for a while, but I still feel Python’s DBAPI is the cleanest and most relevant for the S language.