SQL Formatter Options

SQLinForm Options Help

SQLinForm formats SQL through 220 options, grouped the same way in every edition – the VS Code extension, JetBrains, SSMS, Notepad++ and the online formatter. Each page below documents one group: what every option does, its default, and a before/after example. The option IDs are the keys stored inside a profile file, so they are the same wherever you use SQLinForm.

Global formatting

Settings that apply to every statement, whatever the SQL command.

Statements

Linebreaks and indentation clause by clause, per SQL command.

Lists and expressions

Constructs that appear inside a clause rather than around it.

DDL and procedural code

CREATE statements, and the code inside stored procedures and functions.

Beyond formatting

Working with SQL that lives inside application source code.

220 options across 24 pages. Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

General Options

The General Options apply to every statement SQLinForm formats, regardless of the SQL command. Start here: pick your database dialect, decide how deep one indentation level is, and tell the formatter which characters mark strings and statement boundaries in your code. Everything on the other option pages builds on these settings.

General Options

select
  dept_nbr,
  dept_name
from
  dept

select
    dept_nbr,
    dept_name
from
    dept

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Upper/Lower Keywords

These options control letter casing. Most teams settle on one convention – keywords in upper case, table and column names in lower case – and let the formatter enforce it, so that casing never has to be discussed in a code review again. You can also maintain your own keyword list for words the parser does not recognise as SQL keywords.

Upper/Lower Keywords

Select Dept_Nbr, Dept_Name
From Dept
Where Dept_Zip = '64521'

SELECT dept_nbr, dept_name
FROM dept
WHERE dept_zip = '64521'

select nvl(bonus, 0), decode(job, 'M', 'Mgr')
from   employee

select NVL(bonus, 0), DECODE(job, 'M', 'Mgr')
from   employee

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Alignment

Alignment is what turns a correctly indented statement into a readable one. SQLinForm can line up commas, aliases, equal signs, arithmetic operators and concatenation operators into vertical columns, so that the eye can scan a long column list or a wide WHERE clause without reading every character.

Alignment

select emp_nbr, emp_name, dept,
       hire_date, salary, bonus
from   employee

select emp_nbr  , emp_name, dept ,
       hire_date, salary  , bonus
from   employee

select dept_nbr as nbr,
       employee_name as name,
       salary_amount as sal
from   employee

select dept_nbr      as nbr,
       employee_name as name,
       salary_amount as sal
from   employee

where dept_name = 'Sales'
  and employee_nbr >= 100
  and zip = '64521'

where dept_name    =  'Sales'
  and employee_nbr >= 100
  and zip          =  '64521'

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Output Format

These options govern the shape of the formatted result rather than any single SQL keyword: how long a line may become before it is wrapped, and which parts of your script the formatter must leave completely untouched.

Output Format

-- FORMAT_OFF
select  a ,   b   from  t  where  a=1
-- FORMAT_ON

select b,
       c
from   t2

select employee_name, dept_name, salary_amount, hire_date

select employee_name, dept_name,
       salary_amount, hire_date

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Comments

SQLinForm never changes the text of a comment, but it can decide where a comment sits: on its own line or trailing, aligned into a column, converted between line and block style, or removed entirely. Useful when you inherit a script whose comments have drifted out of place over the years.

Comments

select dept_nbr, -- department key
       dept_name
from   dept

select dept_nbr,
       -- department key
       dept_name
from   dept

select dept_nbr, -- key
       employee_name, -- full name
       salary -- gross amount
from   employee

select dept_nbr,      -- key
       employee_name, -- full name
       salary         -- gross amount
from   employee

-- monthly headcount report
select dept_nbr,   -- key
       count(*)    /* headcount */
from   employee

select dept_nbr,
       count(*)
from   employee

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

White Spaces

Fine-grained control over the spaces around punctuation – commas, brackets and operators – plus how blank lines from the original script are treated and whether the whole statement is shifted to the right. These are the smallest adjustments SQLinForm offers, and often the ones that make a house style feel finished.

White Spaces

where a=1
  and b<>2
  and c>=3

where a = 1
  and b <> 2
  and c >= 3

select dept_nbr
from   dept

    select dept_nbr
    from   dept

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

SQL Linebreaks

Two settings that act on the statement as a whole: a length threshold below which a short statement is left on one line, and how the statement delimiter is placed. They are deliberately separate from the per-keyword linebreak options, because they override them.

SQL

select
    count(*)
from
    dept

select count(*) from dept

select dept_nbr from dept;
select emp_nbr from employee;

select dept_nbr from dept
;

select emp_nbr from employee
;

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Keyword Indention & Alignment

How the master keywords – SELECT, FROM, WHERE, GROUP BY, ORDER BY, INSERT, UPDATE, DELETE – relate to the column lists beneath them. This is the single biggest lever on the overall silhouette of a formatted statement: left-aligned block style, or right-justified so that every keyword ends at the same column.

Keyword Indention

select dept_nbr,
       dept_name
from   dept
left outer join employee
on     dept.dept_nbr = employee.dept_nbr
where  dept_zip = '64521'

select          dept_nbr,
                dept_name
from            dept
left outer join employee
on              dept.dept_nbr = employee.dept_nbr
where           dept_zip = '64521'

Keyword Alignment

select dept_nbr,
       dept_name
from   dept
where  dept_zip = '64521'
group by dept_nbr

  select dept_nbr,
         dept_name
    from dept
   where dept_zip = '64521'
group by dept_nbr

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

SELECT

Linebreak options for every clause of a SELECT statement, clause by clause: SELECT, FROM, INTO, WHERE, HAVING, GROUP BY, ORDER BY, WINDOW, OFFSET and the set operators UNION, EXCEPT and INTERSECT. Each clause has a Linebreak Before and a Linebreak After switch, which together decide whether the keyword gets its own line.

SELECT

select dept_nbr,
       dept_name
from   dept

select
    dept_nbr,
    dept_name
from   dept

FROM

select dept_nbr from dept, employee

select dept_nbr
from
    dept,
    employee

INTO

insert into employee (emp_nbr, emp_name)
values (1, 'Smith')

insert
into
    employee (emp_nbr, emp_name)
values (1, 'Smith')

WHERE

The WHERE clause has two independent levels: the position of the WHERE keyword itself, and the treatment of the AND / OR operators that join the individual conditions.

select dept_nbr
from   dept where dept_zip = '64521'

select dept_nbr
from   dept
where
    dept_zip = '64521'

where dept_zip = '64521' and dept_nbr > 100 and active = 1

where dept_zip = '64521'
      and dept_nbr > 100
      and active = 1

HAVING

HAVING mirrors WHERE exactly, but filters after aggregation. The options are deliberately separate so you can format the two clauses differently.

select dept_nbr, sum(salary)
from   employee
group by dept_nbr having sum(salary) > 100000

select dept_nbr, sum(salary)
from   employee
group by dept_nbr
having
    sum(salary) > 100000

having sum(salary) > 100000 and count(*) > 5

having sum(salary) > 100000
       and count(*) > 5

GROUP BY

select dept_nbr, job, sum(salary)
from   employee group by dept_nbr, job

select dept_nbr, job, sum(salary)
from   employee
group by
    dept_nbr,
    job

ORDER BY

select dept_nbr from dept order by dept_name desc, dept_nbr

select dept_nbr
from   dept
order by
    dept_name desc,
    dept_nbr

WINDOW

select rank() over w from employee window w as (order by salary desc)

select rank() over w
from   employee
window w as (order by salary desc)

OFFSET

select emp_name from employee order by emp_name offset 10 rows fetch next 20 rows only

select emp_name
from   employee
order by emp_name
offset 10 rows fetch next 20 rows only

UNION, EXCEPT, INTERSECT

select dept_nbr from dept union select dept_nbr from dept_archive

select dept_nbr
from   dept

union

select dept_nbr
from   dept_archive

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Sub-Select & CTE

A subquery or a common table expression is a complete SELECT nested inside another statement. These options decide how that nested statement is set off from its surroundings: how its brackets are placed and whether its body is indented one level deeper or aligned to the opening bracket.

Sub-Select & CTE

select dept_nbr
from   dept
where  dept_nbr in (
select dept_nbr
from   employee
)

select dept_nbr
from   dept
where  dept_nbr in (
           select dept_nbr
           from   employee
       )

where dept_nbr in (select dept_nbr from employee)

where dept_nbr in
(
    select dept_nbr
    from   employee
)

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

JOIN

Formatting for JOIN clauses and their ON conditions. Because a query with five joins is mostly join syntax, these options have a disproportionate effect on how quickly a reader can see which tables are combined and on which columns.

JOIN

from dept inner join employee on dept.dept_nbr = employee.dept_nbr

from dept
inner join
    employee
on dept.dept_nbr = employee.dept_nbr

inner join employee on dept.dept_nbr = employee.dept_nbr

inner join employee
on
    dept.dept_nbr = employee.dept_nbr

on dept.dept_nbr = emp.dept_nbr and dept.region = emp.region

on  dept.dept_nbr = emp.dept_nbr
and dept.region   = emp.region

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

INSERT, UPDATE, DELETE

Formatting for the three DML statements. The INSERT options mostly concern the two bracketed lists – columns and values – which are easiest to compare when they are stacked with one entry per line. The UPDATE and DELETE options control the SET clause and the comma placement inside it.

INSERT

An INSERT holds two parallel bracketed lists. They are easiest to verify when both use the same layout, so that the n-th column and the n-th value sit on the same line number.

insert into employee (emp_nbr, emp_name, dept_nbr) values (1, 'Smith', 10)

insert into employee
(
    emp_nbr,
    emp_name,
    dept_nbr
)
values
(
    1,
    'Smith',
    10
)

(
    emp_nbr, emp_name, dept_nbr, hire_date
)
values
(
    1, 'Smith', 10, '2026-01-15'
)

(
    emp_nbr,
    emp_name,
    dept_nbr,
    hire_date
)
values
(
    1,
    'Smith',
    10,
    '2026-01-15'
)

(
    emp_nbr,
    emp_name,
    dept_nbr
)

(
    emp_nbr
  , emp_name
  , dept_nbr
)

UPDATE, DELETE

update employee set salary = salary * 1.05, bonus = 500 where dept_nbr = 10

update
    employee
set
    salary = salary * 1.05,
    bonus  = 500
where dept_nbr = 10

delete from employee where dept_nbr = 10

delete
from   employee
where  dept_nbr = 10

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

MERGE

A MERGE statement combines a target, a source, a join condition and several conditional branches in one command, which makes it one of the longest statements in everyday SQL. These options break it into its constituent clauses – MERGE, USING, ON, WHEN and THEN – so the structure stays visible.

MERGE

merge
into   employee tgt
using  employee_staging src
on     (tgt.emp_nbr = src.emp_nbr)
when matched then
    update set tgt.salary = src.salary
when not matched then
    insert (emp_nbr, emp_name)
    values (src.emp_nbr, src.emp_name)

into employee tgt using employee_staging src

into employee tgt
using
    employee_staging src

using employee_staging src on (tgt.emp_nbr = src.emp_nbr)

using employee_staging src
on (tgt.emp_nbr = src.emp_nbr)

on (tgt.emp_nbr = src.emp_nbr and tgt.region = src.region)

on (tgt.emp_nbr = src.emp_nbr
        and tgt.region = src.region)

when matched and src.salary > 0 and src.active = 1 then

when matched
     and src.salary > 0
     and src.active = 1 then

when matched then
    update set tgt.salary = src.salary

when matched
then
    update set tgt.salary = src.salary

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Comma Separated Lists

The comma-separated list is the most common construct in SQL: the SELECT column list, GROUP BY, ORDER BY, INSERT columns and values. These options decide how many entries share a line, whether the comma sits at the end of a line or leads the next one, and how a leading comma is aligned. Leading commas are a widespread convention because adding or removing the last column then touches only one line.

Comma Separated Lists in SQL Statemets

select emp_nbr, emp_name, dept_nbr,
       hire_date, salary, bonus
from   employee

select emp_nbr,
       emp_name,
       dept_nbr,
       hire_date,
       salary,
       bonus
from   employee

select emp_nbr, emp_name, dept_nbr
from   employee

select emp_nbr,
       emp_name,
       dept_nbr
from   employee

select emp_nbr,
       emp_name,
       dept_nbr
from   employee

select emp_nbr
     , emp_name
     , dept_nbr
from   employee

select first_name || ' ' || last_name as full_name
from   employee

select first_name
       || ' '
       || last_name as full_name
from   employee

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

My Lists for SQL Functions

Some function calls hold long argument lists that deserve their own layout – a DECODE with twenty branches, an IN list of literals, a COALESCE across many columns. Here you can name up to three groups of function keywords and give each group its own formatting, independent of the general list options.

My List for SQL Functions 1

select decode(status, 1, 'new', 2, 'open', 3, 'done', 'other')
from   ticket

select decode(status,
              1, 'new',
              2, 'open',
              3, 'done',
              'other')
from   ticket

My List for SQL Functions 2

where dept_nbr in (10, 20, 30, 40, 50, 60)

where dept_nbr in (
          10, 20,
          30, 40,
          50, 60
      )

My List for SQL Functions 3

select coalesce(bonus, commission, allowance, 0)
from   employee

select coalesce(bonus,
                commission,
                allowance,
                0)
from   employee

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Conditions in Brackets

When a WHERE or HAVING clause groups conditions with brackets, the brackets carry the logic: they decide what binds to what. These options make that grouping visible at a glance by placing linebreaks around the brackets and indenting their contents.

Conditions in Brackets

where (dept_nbr = 10 or dept_nbr = 20) and active = 1

where (
          dept_nbr = 10
          or dept_nbr = 20
      )
      and active = 1

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Analytic Expressions - OVER

Window functions such as ROW_NUMBER() OVER (PARTITION BY … ORDER BY …) pack a whole sub-language into one bracketed expression, frequently inside an already long column list. These options give the OVER clause its own layout so that the partitioning and ordering can be read separately from the function call.

Analytic Expressions - OVER

select rank() over (partition by dept_nbr order by salary desc) as rnk
from   employee

select rank() over
       (
           partition by dept_nbr
           order by salary desc
       ) as rnk
from   employee

over (partition by dept_nbr, job order by salary desc, hire_date)

over (partition by dept_nbr,
                   job
      order by salary desc,
               hire_date)

over
(
partition by dept_nbr
order by salary desc
)

over
(
    partition by dept_nbr
    order by salary desc
)

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

CASE

A CASE expression is a decision table written inline, and it benefits more than any other construct from consistent formatting: with each WHEN on its own line, the branches can be compared vertically. These options cover the CASE, WHEN, THEN, ELSE and END keywords, the conditions inside a WHEN, and a threshold that keeps very short CASE expressions on one line.

CASE Keywords

These options place the five keywords that make up a CASE expression. Read them as pairs: Linebreak Before decides whether the keyword starts a new line, Linebreak After whether its operand starts a new line.

select emp_name, case when salary > 5000 then 'high' else 'low' end as band
from   employee

select emp_name,
       case
           when salary > 5000 then 'high'
           else 'low'
       end as band
from   employee

case when salary > 5000 then 'high' when salary > 2000 then 'mid' else 'low' end

case
    when salary > 5000 then 'high'
    when salary > 2000 then 'mid'
    else 'low'
end

case
    when salary > 5000 then 'high'
    when salary > 2000 then 'mid'
end

case
    when salary > 5000
    then 'high'
    when salary > 2000
    then 'mid'
end

case
    when salary > 5000 then 'high' else 'low'
end

case
    when salary > 5000 then 'high'
    else 'low'
end

CASE Conditions

Applies to the boolean expression inside a WHEN, not to the CASE expression as a whole.

when (salary > 5000 and job = 'MGR') then 'senior'

when (
         salary > 5000
         and job = 'MGR'
     ) then 'senior'

when salary > 5000 and job = 'MGR' and active = 1 then 'senior'

when salary > 5000
     and job = 'MGR'
     and active = 1 then 'senior'

Small CASE Statements

select case
           when flag = 1 then 'Y'
           else 'N'
       end as active
from   employee

select case when flag = 1 then 'Y' else 'N' end as active
from   employee

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

ANSI DDL

Formatting for CREATE TABLE and related DDL. A table definition is read far more often than it is written – it is the reference for everyone working with the table – so a stable, column-per-line layout with aligned data types pays off over the lifetime of the schema.

ANSI DDL

create table dept
(
    dept_nbr  integer not null,
    dept_name varchar(60),
    dept_zip  char(5)
)

create table dept
(
    dept_nbr  integer not null
  , dept_name varchar(60)
  , dept_zip  char(5)
)

create table dept
(
    dept_nbr integer, dept_name varchar(60), dept_zip char(5)
)

create table dept
(
    dept_nbr  integer,
    dept_name varchar(60),
    dept_zip  char(5)
)

create table dept (dept_nbr integer, dept_name varchar(60))

create table dept
(
    dept_nbr  integer,
    dept_name varchar(60)
)

create table dept
(
dept_nbr  integer,
dept_name varchar(60)
)

create table dept
(
    dept_nbr  integer,
    dept_name varchar(60)
)

create table sales
(
    sale_id   integer,
    sale_date date
)
tablespace
    ts_sales
partition by
    range (sale_date)

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Procedure & Function Parameters

The parameter list in the header of a stored procedure or function is its public interface. These options place the brackets and the commas of that list, so that every parameter with its mode and data type occupies its own line.

Proceddure / Function Parameters

create procedure raise_salary (p_emp_nbr in integer, p_pct in number, p_result out varchar2) as

create procedure raise_salary
(
    p_emp_nbr in  integer,
    p_pct     in  number,
    p_result  out varchar2
)
as

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

IF THEN ELSE & Conditions

Procedural code inside a stored procedure follows different rules from a SELECT statement. These options format IF / THEN / ELSE blocks, the BEGIN…END blocks nested within them, and the boolean conditions those blocks test.

IF THEN ELSE

if v_salary > 5000 then

if
    v_salary > 5000 then

if v_salary > 5000 then v_band := 'high';

if v_salary > 5000
then
    v_band := 'high';

if v_salary > 5000 then
v_band := 'high';
else
v_band := 'low';
end if;

if v_salary > 5000 then
    v_band := 'high';
else
    v_band := 'low';
end if;

Conditions

if v_salary > 5000 and v_job = 'MGR' and v_active = 1 then

if v_salary > 5000
   and v_job = 'MGR'
   and v_active = 1 then

if (v_salary > 5000 and v_job = 'MGR' and v_dept = 10) then

if
(
    v_salary > 5000
    and v_job   = 'MGR'
    and v_dept  = 10
)
then

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Stored Procedure Variables

Three alignment options for the variable declarations and assignments in procedural code. A declaration block with aligned data types reads like a table, which makes an omitted or mistyped declaration easy to spot.

Stored Procedure Variables

declare
    v_emp_nbr integer;
    v_employee_name varchar2(60);
    v_salary number(9,2);
begin
    v_salary := 0;
    v_employee_name := 'unknown';

declare
    v_emp_nbr       integer;
    v_employee_name varchar2(60);
    v_salary        number(9,2);
begin
    v_salary        := 0;
    v_employee_name := 'unknown';

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Stored Procedure Statements

Comma placement for lists that appear in procedural statements – the argument list of a procedure call, an INTO target list, and similar constructs outside a regular SELECT.

Stored Procedure Statements

exec dbo.usp_update_employee
    @emp_nbr   = 4711,
    @emp_name  = 'Smith',
    @dept_nbr  = 10,
    @salary    = 5200.00,
    @hire_date = '2026-01-15';

exec dbo.usp_update_employee
    @emp_nbr   = 4711
  , @emp_name  = 'Smith'
  , @dept_nbr  = 10
  , @salary    = 5200.00
  , @hire_date = '2026-01-15';

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.

Extract & Generate SQL

SQLinForm can work on SQL that is embedded in application source code: it extracts the statement from the surrounding string concatenation, formats it, and writes it back wrapped in the syntax of your programming language. These options define the string delimiter to look for and the code template to emit.

Extract SQL from Code

Used by the Extract SQL from Source Code command: SQLinForm strips the surrounding programming-language syntax, formats the SQL it finds, and can then re-wrap it using the settings below.

sql.append("select dept_nbr, dept_name ");
sql.append("from dept where dept_zip = '64521'");

select dept_nbr,
       dept_name
from   dept
where  dept_zip = '64521'

Generate SQL Code

select dept_nbr,
       dept_name
from   dept

StringBuilder sql = new StringBuilder();
sql.Append("select dept_nbr, ");
sql.Append("       dept_name ");
sql.Append("from   dept ");

-- ID161 first line prefix : StringBuilder sql = new StringBuilder();
-- ID163 body line prefix  : sql.append("
-- ID164 body line suffix  : ");
-- ID166 last line suffix  : ").toString();

StringBuilder sql = new StringBuilder();
sql.append("select dept_nbr, ");
sql.append("       dept_name ");
sql.append("from   dept ").toString();

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.