postgresql/consistent-text-over-varchar

Why this matters

PostgreSQL stores `text` and `varchar(n)` the same way. The length on `varchar(n)` is enforced by a per-table constraint that you cannot relax without rewriting the table. Use `text` with a `CHECK (length(col) <= N)` when you need a cap. Or invert the rule with the `style` option for projects that intentionally cap every string column at the type level.

Examples

CREATE TABLE users (name VARCHAR(255));

CREATE TABLE users (name TEXT);

CREATE TABLE users (name TEXT CHECK (length(name) <= 255));

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/consistent-text-over-varchar": [
        "warn",
        {
          style: "always",
        },
      ],
    },
  },
];

Options

style "always" | "never" default: "always"

`always` (default) requires `text` over `varchar(n)`. `never` requires `varchar(n)` (or another bounded string type) over `text`.