cartodb: Review SQL errors for `select existing_column from...`
Context
This ticket is related to https://github.com/CartoDB/cartodb/pull/13631.
Steps to Reproduce
- Open the SQL console
- Enter:
SELECT cartodb_id FROMorSELECT 1 as X FROM - Check the SQL Error
Current Result
Now it returns an Error in SQL query: ... error.
Expected result
They should return a The column does not exist warning. This may be related with the Maps API responses.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 22 (12 by maintainers)
@Jesus89 @ivanmalagon After talking to @rjimenezda, we are going to close this issue. Better errors should be given to explain to the users how to remake their SQL queries. But this could be added to bigger project as started here.
So… I’ll leave it here for the next responder.
The issue is
So if I edit the SQL and apply…
… even if the layer is wrong (we can’t visualize the points because there are no geom columns, users expect those columns to appear in the list.
It’s a bit tricky since the layer is wrong and that won’t have the same behaviour for all combinations.
I leave ongoing work on the branch https://github.com/CartoDB/cartodb/tree/13642-sql-messages
Bear in mind the acceptance of previous tasks related to this one: https://github.com/CartoDB/cartodb/pull/13631 https://github.com/CartoDB/cartodb/pull/13628 (Acceptance of user flow)
I don’t want to hijack or speak out of turn, but I hope this is useful idea at least - it would be awesome if some of text from the error message was a clickable link … to a page in our documentation, which explains the required columns and how the user can fix it etc.
New users may not have a clue what they are supposed to do to fix it, and if we can steer them in the right direction and make them feel less stupid, I think we would get better experience in these cases?