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
CREATE TABLE t (code CHAR(3));CREATE TABLE t (code BPCHAR(3));Correct
CREATE TABLE t (code TEXT);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
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.
Diagnostics
No issues found.
2 rules enabled.
Rule under test
no-char-type — plus no-syntax-error as a safety net.