Issue 57513 - OO Base frontend does not recognize UNION SELECT statements
Summary: OO Base frontend does not recognize UNION SELECT statements
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0
Hardware: All Linux, all
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-08 13:46 UTC by fqs7432
Modified: 2013-02-07 22:43 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
ODB file with two small tables, one query and one report to demonstrate the problem. (14.73 KB, application/vnd.sun.xml.base)
2005-11-08 13:47 UTC, fqs7432 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description fqs7432 2005-11-08 13:46:52 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. 
 
I tried to fool the report generator, by generating a report before the query 
contained the union select part (the second select statement, which follows 
the word UNION, included), and afterwards modifying the query, but the report 
won't generate any report, merely the layout template, if used once the query 
was made to include the UNION SELECT part.
Comment 1 fqs7432 2005-11-08 13:47:57 UTC 
Created attachment 31261 [details]
ODB file with two small tables, one query and one report to demonstrate the problem.
Comment 2 fqs7432 2005-11-08 13:49:58 UTC 
Sorry, the text in the first paragraph contains an error. Instead of "The 
function SELECT CASE WHEN" it should read "The UNION SELECT statement"
Comment 3 christoph.lukasiak 2006-05-09 10:57:48 UTC 
several 'handmade' sql strings cannot be 'translated' in the query design ui -
this is one of them - to improve the query design in this direction make sense

send further to: 'requirements'