You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This error is very annoying because it occurs at the end of all the SQL queries before the CATALOGUE_RESULTS tables are created so it seems difficult to recover from this error.
To Reproduce
Run an analysis with the CatalogueExport::catalogueExport() containing a SQL error in one of the queries, with default parameters and numThreads=1
The text was updated successfully, but these errors were encountered:
Yes in principle no queries should fail and we may need to stop if they do to avoid these issues. Not sure about the 6 elements will try to reproduce (never happened earlier even when queries did fail for me).
I am not able to reproduce this when I simulate an error in the query on the current dev version
it then adds this row:
2021-03-07 17:07:20 [Main thread] ERROR CatalogueExport 3 Analysis 0 -- ERROR Error: Error executing SQL: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'synpuf.personP'. An error report has been created at /Users/Rijnbeek/Documents/Github/EHDEN/CatalogueExport/errorReportSql.txt
Describe the bug
CatalogueExport/R/CatalogueExport.R
Line 921 in a7cdbd8
The error occurs if the log file doesn't contain 6 elements.
The log file doesn't contain 6 elements if only one of the queries doesn't work: an error is logged and the line added doesn't contain 6 elements:
This error is very annoying because it occurs at the end of all the SQL queries before the CATALOGUE_RESULTS tables are created so it seems difficult to recover from this error.
To Reproduce
Run an analysis with the CatalogueExport::catalogueExport() containing a SQL error in one of the queries, with default parameters and numThreads=1
The text was updated successfully, but these errors were encountered: