question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Review SQL errors for `select existing_column from...`

See original GitHub issue

Context

This ticket is related to https://github.com/CartoDB/cartodb/pull/13631.

Steps to Reproduce

  1. Open the SQL console
  2. Enter: SELECT cartodb_id FROM or SELECT 1 as X FROM
  3. 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.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:22 (12 by maintainers)

github_iconTop GitHub Comments

1reaction
ramiroaznarcommented, Apr 3, 2018

@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.

1reaction
ivanmalagoncommented, Apr 2, 2018

So… I’ll leave it here for the next responder.

The issue is

When a user wants to filter only certain columns, they must show up in the list of columns.

So if I edit the SQL and apply…

image

… 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)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
Read more >
Error Message 1 to 500 - SQL Server Helper
Error Severity Description 1 10 Version date of last upgrade: 10/11/90. 101 15 Query not allowed in Waitfor. 102 15 Incorrect syntax near '%.*ls'.
Read more >
Debugging SQL syntax errors - Metabase
Review for common syntax errors that are specific to your SQL dialect. Explanation. Your database needs to be able to “read” your query...
Read more >
ORA-00904: invalid identifier Error in Oracle 11g database
What do you do if you get this error while running in SQL script? ... ORA-00904: invalid identifier due to accessing non-existing column...
Read more >
Db2 11 - SQL error codes - IBM
SQL error codes for Java programs: For information on SQL error codes in the range ... THE SELECT STATEMENT CONTAINS BOTH AN UPDATE...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found