Beautifier Wish

[Bink]

I don't currently use Beautifier because I don't like the way it formats the code, rather I use UltraEdit and manually format the lines.

A very simplistic example:

I prefer the lines and spacing:
"." = SPACE

SELECT
...Field1,
...Field2
FROM
...Table1,
WHERE
...Field1 = 'VALUE'
AND
...Field2 = 'ANOTHER_VALUE'
ORDER BY
...Field2,
...Field1;

PL/SQL Developer formats it like:

SELECT Field1,
Field2
FROM Table1,
WHERE Field1 = 'VALUE' AND Field2 = 'ANOTHER_VALUE'
ORDER BY Field2,
Field1;

I know its nit-picky but I like the code to be spread out so it is really easy to read. Readability is key when doing application maintenance so I usually have to reformat other's code before I analyze for problems.

I hope there will be more expansive preferences available for the next version.

Bink

[This message has been edited by Bink (edited 10 September 2003).]

 

[Marco Kalter]

Thank you for your suggestion. We will indeed provide more control over various layour aspects in the next release.

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

 

[MikeEvans]

I agree with Bink - for production code readbility is most important. Incidentally I use a similar format (all items start a new line), but with the variation:-

where
........column1 = value1
....and column2 = value2
....and (...column3 = foo
.........or.column3 = bar)
-- and similarly for nestings

(so all conditions line up on tabs)

The Beautifier mode is extremely useful, however, for turning the output of unsympathetically concatenated Dynamic [PL/
]SQL strings, or pasted in Oracle tkprof SQL statements into something a lot more readable, for very no effort. And for this I am most grateful

 

[roselan]

this is definitvly the n