Issue 78523 - Query: Turning native sql off shouldn't destroy the structure of the query
Summary: Query: Turning native sql off shouldn't destroy the structure of the query
Status: CONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2007-06-15 12:33 UTC by eberlein
Modified: 2013-02-07 22:38 UTC (History)
2 users (show)

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

Attachments
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 eberlein 2007-06-15 12:33:46 UTC 
If you have a select-query with a lot of combined "AND" and "OR" conditions with
parenthesis, then it is useful to work with line breaks and tabs to show the
structure.
If native sql must turned off (e.g. because of issue 78522), base deletes this
structure.
Most db-systems (all?) ignore white spaces, line breaks etc., so couldn't this
behavior be changed?
Another possibility is, to parsing the string at runtime and let him untouched
until the designer was used.
Comment 1 hwoarang 2007-07-30 19:22:20 UTC 
I can confirm the behavior, but I think this is an enhancement.

I tried with MSAccess (ODBC) and Oracle (JDBC): If I turn off the "Run SQL
command directly", all my tabs and line-breaks are removed when saving...

Thank you.

Hwoarang

OOom222 WinXP PRO
Comment 2 marc.neumann 2007-08-07 11:53:19 UTC 
HI,

I reassign this issue to the User Experience team for evaluating.

Bye Marc