Miguel Oliveira created CALCITE-1372:
----------------------------------------

             Summary: Calcite generate wrong field names in JDBC adapter
                 Key: CALCITE-1372
                 URL: https://issues.apache.org/jira/browse/CALCITE-1372
             Project: Calcite
          Issue Type: Bug
          Components: core
    Affects Versions: 1.8.0
         Environment: This bug was detected using an Oracle datasource.
            Reporter: Miguel Oliveira
            Assignee: Julian Hyde
            Priority: Critical


For example, this query: 

{quote}
SELECT v1272.`QUESTN_LBL` `Label (Question Metrics)`,v1274.`LBL` `Label 
(Question)`,v1272.`CLICKTHRU_CNT` `Click Thru Count (Question 
Metrics)`,v1272.`CLICKTHRU_RATIO` `Click Thru Ratio (Question 
Metrics)`,v1272.`DATE` `Date (Question Metrics)`,v1272.`HAS_RESPONSES` `Has 
Responses (Question Metrics)`,v1272.`LOCALE_KEY` `Locale (Question 
Metrics)`,v1272.`QUESTN_CNT` `Question Count (Question 
Metrics)`,v1272.`QUESTN_KEY` `NAVIGATION_8_QUESTION` FROM DW_REPORTING.QUESTION 
v1272  LEFT JOIN DW_REPORTING.METRICS v1274 ON v1272.`QUESTN_KEY` = 
v1274.`QUESTN_KEY` WHERE UPPER(CAST(v1274.`LBL` AS VARCHAR(1000))) LIKE 
UPPER('% den %') 
{quote}

Generates the following SQL query:

{quote} SELECT "QUESTN_LBL" "Label (Question Metrics)", "LBL" "Label 
(Question)", "CLICKTHRU_CNT" "Click Thru Count (Question Met", 
"CLICKTHRU_RATIO" "Click Thru Ratio (Question Met", "DATE" "Date (Question 
Metrics)", "HAS_RESPONSES" "Has Responses (Question Metric", "LOCALE_KEY" 
"Locale (Question Metrics)", "QUESTN_CNT" "Question Count (Question Metri", 
"QUESTN_KEY" "NAVIGATION_8_QUESTION", "ID", "QUESTN_KEY0" "QUESTN_KEY"
FROM (SELECT "ID", "QUESTN_KEY", "LOCALE_KEY", "QUESTN_LBL", "DATE", 
"QUESTN_CNT", "CLICKTHRU_CNT", "CLICKTHRU_RATIO", "HAS_RESPONSES"
FROM "DW_REPORTING"."QUESTION") "t"
LEFT JOIN (SELECT "QUESTN_KEY", "LBL"
FROM "DW_REPORTING"."METRICS") "t0" ON "t"."QUESTN_KEY" = "t0"."QUESTN_KEY"
WHERE UPPER("t0"."LBL") LIKE UPPER('% den %')
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to