All rules

Safety

postgresql/no-cross-join

Warn on CROSS JOIN.

  • Type suggestion
  • Recommended warn
  • Fixable no

Why this matters

If the intent really is a cartesian product, write `JOIN ... ON true` so the intent reads back. PostgreSQL rejects `INNER JOIN b` without `ON`/`USING`, so the explicit `CROSS JOIN` is the only form this rule sees in practice.

Examples

Incorrect

Incorrect
SELECT * FROM a CROSS JOIN b;

Correct

Correct
SELECT * FROM a JOIN b ON a.id = b.id;
Correct
SELECT * FROM a JOIN b ON true; -- intentional cartesian

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-cross-join": "warn",
    },
  },
];

Options

This rule has no options.

Try this rule

Edit the SQL — only no-cross-join 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-cross-join — 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