Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA | swissarmyknife(*) |
| Priority | Major |
| Complexity | Unknown |
| Component | Q Analyzer |
| Version | 14.0 |
MySQL connection or SQL Server connection
In v13 Aqua Data Studio would indicate red after position 77 in line# 3. But in the latest build it is getting displayed with black color. See attached screenshot
SELECT * FROM "Test_schema"."WORKSHEET" WHERE "SSN"='\&Varible_name'
go
SELECT '\&PID='column_name'','\&P_NAME='column_name','\&CITY='column_name'' FROM &variable_name="TEST_SHEMA_NAME"."TABLE_NAME"
go
Select * from &variable_name=schema_name.table_name
go
Select * from &variable_name=schema_name,table_name
go
Select * from &schema_name!table_name
go
Select * from &variable_name=schema_name!table_name
go
Select * from &schema_name,table_name
go
Select * from [&variable_name].table_name
go
I think the test case for this issue can be distilled down to:
SELECT 'abc', ' FROM [&abc].table_name
And in v13, we display as:
SELECT 'abc', ' FROM [&abc].table_name
This is a direct result of fixing issue 10416, where we want:
SELECT * from [Req'd]
The current syntax token parsing mechanism only preserves the previous token state. So without changing the parsing state stack significantly, we terminate the quote when we encounter a ']' character - without this we won't be able to fix 10416. I would recommend not changing the parsing code and leave this issue as is. After all, the query is probably wrong syntax in the first place.
Issue #10460 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 14.0.1-4 |
| No time estimate |
2 issue links |
depends upon #8853
Issue #8853need uniformity in syntax highlighting on ADS query analyzer for mongo |
relates to #10416
Issue #10416parsing column names within square brackets like [Req'd] - thinks the single quote is start of a string |
I think the test case for this issue can be distilled down to:
SELECT 'abc', ' FROM [&abc].table_name
And in v13, we display as:
SELECT 'abc', ' FROM [&abc].table_name
This is a direct result of fixing issue 10416, where we want:
SELECT * from [Req'd]
The current syntax token parsing mechanism only preserves the previous token state. So without changing the parsing state stack significantly, we terminate the quote when we encounter a ']' character - without this we won't be able to fix 10416. I would recommend not changing the parsing code and leave this issue as is. After all, the query is probably wrong syntax in the first place.