Endline layout vs. Block lay-out

[aotte]

OK, everybody, get your religious war shields out of your desks.

First though, I love the beautifier. It saves me tons of time when I have to look at other peoples code, regardless my improvement wishes.

All examples using 3 space indentation.

The beautifier uses endline layout for SQL code, which means that the code is indented to align a block with the keyword that began it. And I don't know about everybody else, but my eyes and brain go for a spin having to deal with it, when you have subqueries, and nested table functions.

Below is a simplified example:

SELECT *
FROM   TABLE(get_dims(CURSOR
                      (SELECT *
                       FROM   TABLE(get_lowest_level(CURSOR
                                                     (SELECT *
                                                      FROM   src
                                                      WHERE  change_dttm >=
                                                             TRUNC(SYSDATE))))))) i

I was wondering whether we could get an option to do a faked block lay-out for SQL code, just like the beautifier does for PL code. Something along the lines of this....

SELECT *
FROM   TABLE(get_dims(CURSOR
   (SELECT *
   FROM    TABLE(get_lowest_level(CURSOR
      (SELECT *
      FROM    src
      WHERE change_dttm >= TRUNC(SYSDATE))))))) i

What would be nice though, if we could add specific comments - like the documenter - for code that we manually changed the lay-out off, so that the beautifier knows to leave it alone.

-- [NO_BEAUTY]
SELECT * FROM DUAL WHERE DUMMY NOT IN ('X');
-- [/NO_BEAUTY]

------------------
Hakuna Matata,

Arnoud.

[This message has been edited by aotte (edited 07 May 2003).]

[This message has been edited by aotte (edited 07 May 2003).]

 

[Marco Kalter]

I have added these suggestions to the list of enhancement requests.

Thanks.

------------------
Marco Kalter
Allround Automations