log SQL queries

[scossin]

Thanks for the package, it's easy to use and to run.

We faced 2 problems when running it:

1. A SQL query that was too long to run
2. A SQL query generated an error in the log

To debug these problems, it is helpful to have the generated SQL queries to run them in a database IDE. I think it would be easier to debug with easy access to the generated SQL queries, so I would like to suggest the following:

1. If a SQL error occurs, log the SQL query with the error:

ParallelLogger::logError(sprintf("Analysis %d -- ERROR %s", mainSql$analysisId, e))
ParallelLogger::logError(sprintf("\t SQL executed:"))
ParallelLogger::logError(mainSql$sql)

2. Add a debug mode to log the SQL queries
   The default INFO threshold could be passed as a parameter to the CatalogueExport::catalogueExport() function and if set to "debug", SQL queries would go to the log.
   For example:

ParallelLogger::logInfo(sprintf("[Main Analysis] [START] %d (%s)", 
      as.integer(mainSql$analysisId), 
      analysisDetails$ANALYSIS_NAME[analysisDetails$ANALYSIS_ID == mainSql$analysisId]))
ParallelLogger::logDebug(mainSql$sql)

So if a SQL query is too long to run, it's easier to see what is the SQL query that is posing a problem.