Should column types be aligned vertically in CREATE TABLE?

It's a genuine trade-off, not a right answer — vertical alignment reads nicely, but every time a column is renamed or a type gets longer, the whole block needs re-aligning, which turns a one-line change into a noisy diff. Many modern style guides skip alignment for that reason.

Trailing or leading commas in CREATE TABLE?

Trailing commas are far more common in DDL than in SELECT lists — since every column line needs a comma except the last, a trailing comma reads naturally top-to-bottom.

Should constraints be named explicitly?

Yes, whenever the database allows it. An unnamed constraint gets an autogenerated name that can differ across environments, which makes a later ALTER TABLE ... DROP CONSTRAINT need a lookup first; a named constraint can be referenced directly.

Where should PRIMARY KEY go for a single-column key?

Either inline on the column (id integer PRIMARY KEY) or as its own named line at the end works — inline is more common for a single obvious key, while a trailing, named constraint is preferred once the key spans more than one column.

Does formatting a CREATE TABLE change how the database executes it?

No — whitespace, line breaks, and comment placement have no effect on how a CREATE TABLE is parsed or the resulting schema; formatting is purely for the humans reading and reviewing it.

SQL CREATE TABLE Formatting: A Practical Guide

sqlfmt▍

SQL CREATE TABLE Formatting: A Practical Guide — sqlfmt

A CREATE TABLE statement gets read far more often than it gets written — in code review, in a migration diff, months later when someone's trying to remember what a column means. A consistent layout is what makes that reading fast.

Key takeaways

One column definition per line, always — a CREATE TABLE with columns packed onto one line stops being readable past three or four of them.
Inline constraints (NOT NULL, DEFAULT, a single-column UNIQUE) stay on the column's own line; multi-column and named constraints get their own line at the end.
Trailing commas are the norm for CREATE TABLE column lists in most style guides, since every line except the last needs one.
Naming a constraint explicitly (CONSTRAINT pk_orders PRIMARY KEY (id)) makes a future ALTER TABLE ... DROP CONSTRAINT possible without hunting for an autogenerated name first.

One column per line

Hard to review

CREATE TABLE orders (id serial PRIMARY KEY, customer_id integer NOT NULL, total numeric(10,2) NOT NULL, created_at timestamptz NOT NULL DEFAULT now());

Readable

CREATE TABLE orders (
  id integer PRIMARY KEY GENERATED ALWAYS AS IDENTITY,
  customer_id integer NOT NULL,
  total numeric(10, 2) NOT NULL,
  created_at timestamptz NOT NULL DEFAULT now()
);

PostgreSQL

CREATE TABLE order_items (
  order_id integer NOT NULL,
  product_id integer NOT NULL,
  quantity integer NOT NULL,
  CONSTRAINT pk_order_items PRIMARY KEY (order_id, product_id),
  CONSTRAINT fk_order_items_order FOREIGN KEY (order_id) REFERENCES orders (id)
);

PostgreSQL

CREATE TABLE orders (
  id integer PRIMARY KEY GENERATED ALWAYS AS IDENTITY,
  customer_id integer NOT NULL,
  status text NOT NULL DEFAULT 'pending',
  total numeric(10, 2) NOT NULL,
  created_at timestamptz NOT NULL DEFAULT now(),
  CONSTRAINT fk_orders_customer FOREIGN KEY (customer_id) REFERENCES customers (id)
);

How to Format SQL CREATE TABLE Statements

Quick answer

FAQs

Should column types be aligned vertically in CREATE TABLE?

Trailing or leading commas in CREATE TABLE?

Should constraints be named explicitly?

Where should PRIMARY KEY go for a single-column key?

Does formatting a CREATE TABLE change how the database executes it?

How to Format SQL Subqueries and Derived Tables

How to Format SQL INSERT, UPDATE, and DELETE Statements

How to Format SQL Stored Procedures and Functions

Key takeaways

One column per line

Where inline constraints go

Naming multi-column constraints explicitly

Indentation and alignment

A full example

Quick answer

FAQs

Should column types be aligned vertically in CREATE TABLE?

Trailing or leading commas in CREATE TABLE?

Should constraints be named explicitly?

Where should PRIMARY KEY go for a single-column key?

Does formatting a CREATE TABLE change how the database executes it?

Keep reading

How to Format SQL Subqueries and Derived Tables

How to Format SQL INSERT, UPDATE, and DELETE Statements

How to Format SQL Stored Procedures and Functions

Key takeaways

One column per line

Where inline constraints go

Naming multi-column constraints explicitly

Indentation and alignment

A full example

Related reading