Issue 57514

Summary: CASE WHEN isn't recognized by OO Base's frontend
Product: Base Reporter: fqs7432 <afolger>
Component: codeAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 2.0   
Target Milestone: ---   
Hardware: All   
OS: Linux, all   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description fqs7432 2005-11-08 13:51:25 UTC
The function SELECT CASE WHEN works in queries and views, but if a query  
contains such a statement, the design view of the query is no longer available  
and the report generator will refuse to show the fields of that query.
Comment 1 christoph.lukasiak 2006-05-08 17:05:08 UTC
clu->fqs7432: i am not shure, if i understand you right - you create a query in
sql view (native?) and then you want to switch back in design view? if i
understand you right, the design view does not 'understand' your sql string and
do not know how to 'translate' it in the query design ui (that is no bug - the
sql view is made to give you more possibilities to fit your query to your
database/driver - the ui cannot understand every 'selvmade' sql code)

does this help you further?
Comment 2 fqs7432 2006-05-12 16:21:16 UTC
Well, you understood what I posted about. One could argue that the design view 
need not understand all SQL. However, this prevents the report builder from 
using a query/view that uses such statements. Right now, I use the following 
workaround: I create a view with all sql under the sun I like. I then use a 
query to query everything in the view, and sort it according to my fancy. 
Finally, I build the report on the latter query.

I consider CASE WHEN and UNION SELECT important enough to warrant recognition 
by the design view.
Comment 3 christoph.lukasiak 2006-05-15 09:30:48 UTC
clu->fqs7432: i agree with you that this is a wanted feature, so i send it to
the proper adress as feature enhancement