All rules

Schema

postgresql/no-char-type

Avoid CHAR(n) — it pads on write and trims on read.

  • Type suggestion
  • Recommended warn
  • Fixable no

Why this matters

PostgreSQL pads stored `char(n)` values to `n` with trailing spaces and silently trims them on read. The padding surprises comparisons and sorts. Use `text` (and a `CHECK` constraint when you need a length).

Examples

Incorrect

Incorrect
CREATE TABLE t (code CHAR(3));
Incorrect
CREATE TABLE t (code BPCHAR(3));

Correct

Correct
CREATE TABLE t (code TEXT);
Correct
CREATE TABLE t (code TEXT CHECK (length(code) = 3));

Configure it

// eslint.config.js
import postgresql from "eslint-plugin-postgresql";

export default [
  {
    files: ["**/*.sql"],
    languageOptions: {
      parser: postgresql.configs.recommended.languageOptions.parser,
    },
    plugins: { postgresql },
    rules: {
      "postgresql/no-char-type": "warn",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only no-char-type is enabled.

Pre-filled with the first incorrect example. Toggle off in the rule shelf to see how the diagnostic disappears.

0 errors 0 warnings parse 0ms · rules 0ms
Diagnostics

No issues found.

2 rules enabled.

Rule under test no-char-type — plus no-syntax-error as a safety net.
eslint-plugin-postgresql

An ESLint plugin that lints .sql files with real PostgreSQL grammar and a curated set of best-practice rules.

© 2026 eslint-plugin-postgresql contributors Built on libpg-query · PostgreSQL 17