When using an SQLCreator or an SQLExecutor, and something goes wrong (for example the query takes longer than the timeout-limit, or something like that), you can use the Rejected port on the transformer to catch that - which is imperative when using in a webapp, because you’ll need to give the end-user feedback. On the Rejected-port you’ll get the _reader_error attribute, but the way that one is populated is not very helpful. The contents of that attribute are always
An error has occurred. Check the logfile above for details
It would be very helpful and much more meaningful if the contents of the Provider error, which is always in the previous log file line, was added. Because then I could catch that and show that to the user:
(-2147217871) Query timeout expired
which is much more helpful than “check the logfile above” (there is no above - there is nothing, because this has been handled through HTMLReportGenerators to return to the end user’s browser).
On FME Form it’s not a big problem, because you’ll have the logfile right there - but when you then upload your workspace and create a webapp, I’d like to be able to provide more meaningful feedback to my users (and myself).