pgSQL: Non-query syntax errors are dropped sliently

[Voileexperiments]

If you play with other pgSQL sandboxes online (e.g SQL fiddle or Rextester), if you declare a function with syntax errors in it they'll be reported properly. However, in CW it's dropped silently.

I can't express how many hours I've post trying to do SQL katas that involves creating a function when what I only get is PG::UndefinedFunction: ERROR: function my_function() does not exist at the select statement when my function declaration is not correct. And because I don't have any error messages about the function itself, I can only take stabs in the dark to try to fix it. This is horrible.

Edit: It seems that all query-related errors are caught properly, but all function-related are dropped silently. Besides function declarations, EXECUTE is also exhibiting this behaviour.

[kazk]

I think this is because run_sql calls run_cmd which executes the command inside try_connection that swallows errors:

https://github.com/Codewars/codewars-runner-cli/blob/898b466ad65a78a2fd46c5fdd8c6652144af97b0/frameworks/ruby/sql.rb#L138-L146

run_sql seems to handle query related error:

https://github.com/Codewars/codewars-runner-cli/blob/898b466ad65a78a2fd46c5fdd8c6652144af97b0/frameworks/ruby/sql.rb#L99-L102

---

I honestly don't know what's going on here by just skimming. I'll try to take a look at it later when I have time.

/cc @jhoffner