postgresql/no-order-by-ordinal

Why this matters

`ORDER BY 1, 2` silently changes meaning when the SELECT list is reordered or a column is inserted. Worse, the intent is invisible at any callsite that consumes the query via a view or CTE. Reference columns by name or by an alias.

Examples

SELECT id, name FROM users ORDER BY 1;

SELECT id, name, email FROM users ORDER BY 1, 2 DESC;

SELECT id, name FROM users ORDER BY name;

SELECT id, name AS display_name FROM users ORDER BY display_name;

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-order-by-ordinal": "warn",
    },
  },
];

Options

This rule has no options.