Detailed error messages when queries from SQL Editor fail

[emschwartz]

Feature request

Is your feature request related to a problem? Please describe.

If a query fails when run from the SQL editor, it shows the message Error: failed to run query. Bad request.

Describe the solution you'd like

It would be useful if it could show additional error details in the error popup or somewhere else in the UI.

Describe alternatives you've considered

Alternatively, it could just log the additional details in the JS console.

[awalias]

fixed

[lustremedia]

Dear @awalias

This is not FIXED!

I just ran into an issue on the SQL editor saying:

structure of query does not match function result type

while creating a function! It said nothing else ...
As I am new to BOTH postgresql and Supabase I was lost!

I was looking for answers on the web but could not find any answers on that particular problem set.
I found out that I should look into the DETAILS of the error message, but on SUPABASE there were NO DETAILS on the error message.

I finally, after 2 hours of searching, found the details of the error message in the response type of the request in the web console (F12)

This user experience was really bad ... and it wasted 3 hours of my time!

WHY do you NOT put out the details of the error message in the frontend?

The least you could do is: Put out an additional message on the frontent saying to look into the developer console for details!

[awalias]

hey @lustremedia feel free to open a new feature request here for more detailed error messages when debugging SQL functions: #461 (comment)

be sure to add details about the error message that you found in the console that was not propogated to the output box on the SQL editor and the frontend team will take a look at it. thanks!

[lustremedia]

@awalias Thanks for reaching out, I hope my frustration did not come across too harsh :/ Did you want me to open a NEW feature request or just a comment on this one here?

That is all it showed:

This is what I found later and was of course an easy fix, but took me a while ...

[awalias]

ok yeah I'll reopen this one - it's close enough :)

[joshenlim]

hey there @lustremedia! this should now be fixed - i'm not sure if i'm able to reproduce exactly what you ran into, but I can verify that the dashboard will show the detailed errors from the query

I'll go ahead to close this issue but please do let us know otherwise! If you might still be facing this issue, do help us by providing us some steps to reproduce the issue that you're running into 🙏