Beautifer enhancement

[PhilG]

The beautifier is agood tool, but sometimes it doesn't really help, for very long sql instruction it cuts the line at sometime stranges place.

My sugestion is to have some hints :
/*NO BEAUTY*/
code I don't want to beautify
...
/*END NO BEAUTY*/
so that we can keep it as we want and continue to use this great tool on the rest of code
Is there some possibility to prevent it to add a LF just after the "." in a statemment like "record.item" making the statement difficult to read.

Thanks

 

[Marco Kalter]

The "don't beautify" directive is on the list of enhancement requests. The record.item bug is on the to-do list.

 

[Frank Kintrup]

Originally posted by Marco Kalter:
The "don't beautify" directive is on the list of enhancement requests. The record.item bug is on the to-do list.

Is the long awaited "don't beautify" feature implemented yet? I did not find any hints in any of the release notes published after your response to this topic...

Frank

 

[Marco Kalter]

This is planned for 8.0.

 

[kamrath]

Marco... Are you planning other Beautifier enhancements for 8.0 also? E.g...

* WITH clause can't be beautified at all;

* CASE is handled miserably; sometimes not at all.

 

[Gustavo]

* BULK clause can't be beautified at all.

The trigger declaration is not beautified (everything before DECLARE).

 

[Gustavo]

Also, we could have a special handler for decode. Beautifier can't do this:

Select decode(expr,
              pattern1,  result1,
              pattern2,  result2,
              .
              .
              .
              pattern10, result10,
              else_result)
From   dual;

Note resultXX are also aligned.

 

[Sachin]

I dont think the beautifier can handle this:

SELECT --abb
col1
FROM tab1;

If you remove the "--abb", then it formats it properly.

 

[til]

@sachin:
That is a misplaced comment in my view. What would you expect the beautifier to do in this case?