SQL errors aren’t visible to the user

[mbostock]

For example, given the following malformed query:

SELECT '%${"test"}%'

Which can be run from the command line like so:

notebooks query --database postgres 'SELECT '"'"'%' '"test"' '%'"'"

You get the following error:

PostgresError: could not determine data type of parameter $1

But Desktop actually views this error as succeeding (because it isn’t checking the return code of the query command, I guess?), though then typically gets a 404 trying to load the query results (unless they previously succeeded, somehow, in which case the old results are still displayed and no error is visible).