Bye bye, heavyweight formatter. Long live the lightweight formatter. Are you using Oracle’s SQL Developer or SQLcl? Then install these settings<\/a> and press Ctrl-F7 to produce code that conforms to the Trivadis PL\/SQL & SQL Coding Style<\/a>. A compromise between conformity and individuality.<\/p>\n\n\n\n A typical PL\/SQL & SQL formatter replaces whitespace between lexical tokens by default with a single space. A whitespace consists of a series of spaces, tabs and line breaks. As a result, the original whitespace between the tokens is lost. The grammars for SQL*Plus, PL\/SQL and SQL are huge. As a consequence, a single space is not the desired result in many cases. Therefore, a formatter comes with a large set of rules and options to override the default (single space between tokens).<\/p>\n\n\n\n A key feature of a heavyweight formatter is that it produces the same result regardless of how the original code was formatted. There is no room for individuality unless it is part of a rule and its configuration. This makes a complete formatter a heavyweight.<\/p>\n\n\n\n Here is a Heavyweight Formatter<\/h2>\n\n\n\n
create view<\/code> example. Once formatted with spaces between the tokens and once with line breaks between the tokens.<\/p>\n\n\n\n