* using log directory 'd:/Rcompile/CRANpkg/local/4.0/filehashSQLite.Rcheck'
* using R version 4.0.5 (2021-03-31)
* using platform: x86_64-w64-mingw32 (64-bit)
* using session charset: ISO8859-1
* checking for file 'filehashSQLite/DESCRIPTION' ... OK
* this is package 'filehashSQLite' version '0.2-4'
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking whether package 'filehashSQLite' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking DESCRIPTION meta-information ... NOTE
Malformed Description field: should contain one or more complete sentences.
Packages listed in more than one of Depends, Imports, Suggests, Enhances:
  'filehash' 'DBI'
A package should be listed in only one of these fields.
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... NOTE
Packages in Depends field not imported from:
  'RSQLite' 'methods'
  These packages need to be imported from (in the NAMESPACE file)
  for when this namespace is loaded but not attached.
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [5s] NOTE
createSQLite: no visible global function definition for 'dbDriver'
createSQLite: no visible global function definition for 'dbConnect'
createSQLite: no visible global function definition for
  'dbUnloadDriver'
createSQLite: no visible global function definition for 'dbGetQuery'
initializeSQLite: no visible global function definition for 'dbDriver'
initializeSQLite: no visible global function definition for 'dbConnect'
initializeSQLite: no visible global function definition for 'new'
dbDelete,filehashSQLite-character: no visible global function
  definition for 'dbGetQuery'
dbDisconnect,filehashSQLite: no visible global function definition for
  'dbUnloadDriver'
dbFetch,filehashSQLite-character: no visible global function definition
  for 'dbGetQuery'
dbInsert,filehashSQLite-character: no visible global function
  definition for 'dbGetQuery'
dbList,filehashSQLite: no visible global function definition for
  'dbGetQuery'
dbMultiFetch,filehashSQLite-character: no visible global function
  definition for 'dbGetQuery'
Undefined global functions or variables:
  dbConnect dbDriver dbGetQuery dbUnloadDriver new
Consider adding
  importFrom("methods", "new")
to your NAMESPACE file (and ensure that your DESCRIPTION Imports field
contains 'methods').
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ... [2s] OK
* checking for unstated dependencies in 'tests' ... OK
* checking tests ... [2s] OK
  Running 'reg-tests.R' [2s]
  Comparing 'reg-tests.Rout' to 'reg-tests.Rout.save' ...6,8d5
< Warning message:
< In result_fetch(res@ptr, n = n) :
<   SQL statements must be issued with dbExecute() or dbSendStatement() instead of dbGetQuery() or dbSendQuery().
15,19d11
< Warning messages:
< 1: In result_fetch(res@ptr, n = n) :
<   SQL statements must be issued with dbExecute() or dbSendStatement() instead of dbGetQuery() or dbSendQuery().
< 2: In result_fetch(res@ptr, n = n) :
<   SQL statements must be issued with dbExecute() or dbSendStatement() instead of dbGetQuery() or dbSendQuery().
27a20
> [1] TRUE
* checking PDF version of manual ... OK
* DONE
Status: 3 NOTEs