अल्पविराम की स्थिति का विकल्प

Comma placement decides whether each comma goes at the end of a line (trailing, the default) or at the start of the next one (leading). This page shows both outputs, where the option applies, and the practical trade-offs so you can pick one style for your team.

What the option does

Whenever the formatter puts the items of a comma-separated list on separate lines, it has to choose which line gets the comma. The option makes that choice for every such list in the statement:

• the select list;
• GROUP BY and ORDER BY lists;
• function arguments, when a call is split one argument per line;
• value lists such as IN ('OPEN', 'FROZEN'), which are also split one value per line;
• the SET list of an UPDATE, the RETURNING list, and the column and VALUES lists of an INSERT;
• column definitions in CREATE TABLE (,amount NUMERIC(12, 2));
• the named queries of a WITH clause (,ranked AS ();
• select items that are CASE expressions (,CASE WHEN).

The same rule applies at any depth: inside a CTE or a subquery the commas sit at that block's own indentation column.

Nothing else changes: line breaks, indentation and keyword case are the same in both modes.

Possible values and default

Here is the same report query in both styles:

select c.id, c.email, c.country_code, count(o.id) as order_count, sum(o.total) as lifetime_value from customers c left join orders o on o.customer_id = c.id group by c.id, c.email, c.country_code order by lifetime_value desc, c.id

SELECT c.id,
    c.email,
    c.country_code,
    COUNT(o.id) AS order_count,
    SUM(o.total) AS lifetime_value
FROM customers c
    LEFT JOIN orders o
        ON  o.customer_id = c.id
GROUP BY c.id,
    c.email,
    c.country_code
ORDER BY lifetime_value DESC,
    c.id

SELECT c.id
    ,c.email
    ,c.country_code
    ,COUNT(o.id) AS order_count
    ,SUM(o.total) AS lifetime_value
FROM customers c
    LEFT JOIN orders o
        ON  o.customer_id = c.id
GROUP BY c.id
    ,c.email
    ,c.country_code
ORDER BY lifetime_value DESC
    ,c.id

In both outputs the first item stays on the line with its keyword (SELECT c.id, GROUP BY c.id, ORDER BY lifetime_value DESC). With leading commas, every following item starts with a comma at the indentation column, so the commas form a straight vertical line.

Leading commas are applied to function arguments and value lists in the same way:

SELECT id
    ,COALESCE(
        nickname
        ,first_name
    ) AS display_name
    ,round(
        balance
        ,2
    ) AS balance
FROM accounts
WHERE status IN (
    'OPEN'
    ,'FROZEN'
)

Trailing commas: pros and cons

Trailing commas follow normal punctuation, so the query reads like a list in prose. It is the style used in most database documentation, in SQL generated by tools, and by the majority of developers who never thought about the question. A newcomer reading your code will not pause on it.

The cost shows up at the end of the list. The last item has no comma, so it behaves differently from all the others. Comment it out while debugging, and the item before it is left with a comma right in front of FROM:

SELECT c.id,
    c.email,
    c.country_code,
    COUNT(o.id) AS order_count,
    -- SUM(o.total) AS lifetime_value
FROM customers c
    LEFT JOIN orders o
        ON  o.customer_id = c.id

Most databases, including PostgreSQL, MySQL, SQL Server and Oracle, reject that statement with a syntax error near FROM. It is one of the most common self-inflicted SQL errors, and it can happen again every time someone adds or removes the last column and forgets the comma on the line above.

Leading commas: pros and cons

Leading commas move the special case from the last item to the first one. Every item after the first carries its own comma, so removing or commenting out the last line leaves valid SQL:

SELECT c.id
    ,c.email
    ,c.country_code
    ,COUNT(o.id) AS order_count
    -- ,SUM(o.total) AS lifetime_value
FROM customers c
    LEFT JOIN orders o
        ON  o.customer_id = c.id

The vertical line of commas also makes a missing comma easy to spot. That matters more than it seems: in most databases AS is optional for column aliases, so a forgotten comma between two columns does not cause an error. It silently turns the second column into an alias of the first. With leading commas the gap in the comma column is visible at a glance; with trailing commas it hides at the ragged right edge.

The downsides are familiarity and taste. Many developers find a line that starts with punctuation odd, and code copied from documentation or other projects will be in the other style until it is formatted. The problem also does not disappear, it moves: removing or commenting out the first item still requires editing the SELECT line.

Effect on diffs and code review

The difference is easiest to see in version control. Using the layout above, this is how many lines change for common edits:

Columns are added at the end of a list far more often than at the start, so leading commas give slightly smaller diffs and fewer review comments about a stray comma. The effect is real but modest; consistency across the codebase matters more. The code review and version control guide covers how to switch styles without a noisy history.

Which one to choose

Both styles appear in published team style guides, and neither is wrong. Leading commas have a strong following among data and analytics teams that edit long select lists all day; trailing commas remain the more common default elsewhere. As a rule of thumb:

• Choose trailing if SQL is mostly read by application developers, if it is embedded in other code, or if you want output that looks like the documentation.
• Choose leading if your team writes long reporting queries, comments columns in and out while exploring data, or has been bitten by the missing-comma alias problem.

Whichever you pick, let the formatter apply it, so nobody has to remember the rule. The leading vs trailing commas guide goes deeper into the history and the arguments on both sides. The other options are documented on the indent spaces, maximum columns, keyword case and parentheses on new line pages.