Qlik Community

Ask a Question

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
Join us at the Cloud Data and Analytics Tour! REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

SQL coding error ignored in refresh

Hi Community

I have a SQL select from an OLEDB connection Oracle with a deliberate error.  The syntax checker does not find this but more worrying is the fact that the script executes and just ignores the code entirely.  The log of the reload also shows up nothing.  I am using QV 11 SP1 ... anyone got any suggestions?

Test:

SELECT

p.PROJECT_ID AS ProjectId, p.PROJECT_NAME AS ProjectName, p.DISPLAY_STATUS AS Phase,

CASE

  WHEN k.request_type_id IN (30281, 30462,30431)

  THEN 'Simple Projects'

  ELSE 'GCM Projects'

    END AS Methodology

FROM 

KCRT_FG_PFM_PROJECT k,

PM_PROJECTS p,

KCRT_REQ_HEADER_DETAILS kc

WHERE

k.PRJ_PROJECT_ID = p.PROJECT_ID

AND p.STATUS = 0

AND p.DISPLAY_STATUS NOT IN ('On Hold')

AND kcbadbadbad.REQUEST_ID = p.PFM_REQUEST_ID ;   // <-- spot the deliberate error

regards

Ian

1 Solution

Accepted Solutions
Gysbert_Wassenaar

The select statement is not something qlikview parses, but just something that it hands to the dbms (in your case Oracle) to execute. Qlikview itself doesn't understand any of the multitude of sql dialects. Therefore it can't catch any errors. So, always try out your sql statements on the database yourself first.


talk is cheap, supply exceeds demand

View solution in original post

2 Replies
Gysbert_Wassenaar

The select statement is not something qlikview parses, but just something that it hands to the dbms (in your case Oracle) to execute. Qlikview itself doesn't understand any of the multitude of sql dialects. Therefore it can't catch any errors. So, always try out your sql statements on the database yourself first.


talk is cheap, supply exceeds demand

View solution in original post

Not applicable
Author

Thanks for this... makes sense