[R-sig-DB] Release candidates for DBI and RSQLite

[Seth Falcon]

Hello all,

I've made available release candidates for DBI and RSQLite (URLs are 
below) and would appreciate feedback from users able to test these new 
versions.  My plan is to push updates to CRAN at the end of this week.

Here is a list of what's new (extracted from each package's NEWS file):

*** DBI ***
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
   '"'.

*** RSQLite ***

Version 0.8-0

- Upgrade to SQLite 3.6.19

- Apply some code and Rd cleanups contributed by Mattias Burger.
   Avoid partial argument name matching, use TRUE/FALSE not T/F and
   improve Rd markup.

- Integrate RUnit unit tests so that they run during R CMD check.
   Small improvements to make the tests run more quietly.  You can run
   the unit tests by calling RSQLite:::.test_RSQLite() (require latest
   version of the RUnit package).  Also had to disable some unit tests
   on Windows.  Investigation of details is on the TODO list.

- Add sqliteCopyDatabase, a function that uses SQLite's online backup
   API to allow a specified database to be copied to a file.  This can
   be used to create a file copy of an in memory database.

- Increase the default max connections from 16 to 200 in SQLite().
   Connections to SQLite are inexpensive and there is no longer any
   hard-coded limit to the number of connections you can have.
   However, memory is allocated at driver initialization time based on
   the maximum, so it is best not to use very large values unless you
   really need the connections.

- sqliteTransactionStatement, which is used by dbCommit, dbRollback,
   and dbBeginTransaction, now passes silent=TRUE to try() to suppress
   error messages.  Without this, code that could otherwise handle a
   failed commit gracefully had no way to suppress the error message.
   You can use dbGetException to see the error when
   sqliteTransactionStatement returns FALSE.

- dbConnect/sqliteNewConnection now throws an error if dbname argument
   is NA.  Previously, if as.character(NA) was provided, a database
   with filename "NA" was created.

- dbConnect/sqliteNewConnection now accepts two new arguments:

   flags:
       provides additional control over connetion details.  For
       convenience, you can specify one of SQLITE_RWC (default),
       SQLITE_RW, or SQLITE_RO to obtain a connection in
       read/write/create, read/write, or read only mode, respectively.
       See http://sqlite.org/c3ref/open.html for details.
   vfs:
       controls the virtual filesystem used by SQLite.  The default,
       NULL, lets SQLite select the appropriate vfs for the system.
       You can specify one of "unix-posix", "unix-afp", "unix-flock",
       "unix-dotfile", or "unix-none".  For details, see
       http://www.sqlite.org/compile.html.  This functionality is not
       available on Windows and non-NULL values of the vfs argument
       will be ignored with a warning.



URLs:

source:  http://bioconductor.org/packages/misc/DBI_0.2-41.tar.gz
windows: http://bioconductor.org/packages/misc/DBI_0.2-41.zip

source:  http://bioconductor.org/packages/misc/RSQLite_0.7-97.tar.gz
windows: http://bioconductor.org/packages/misc/RSQLite_0.7-97.zip


+ seth

-- 
Seth Falcon | @sfalcon | http://userprimary.net/users