no-select-into · eslint-plugin-postgresql

Why this matters

`SELECT ... INTO target` silently creates a new table. The syntax is confusable with PL/pgSQL's `SELECT INTO variable` and is omitted from most SQL primers. `CREATE TABLE target AS SELECT ...` reads back as the intent.

Examples

Incorrect

SELECT id, name INTO archived_users FROM users WHERE inactive;

Correct

CREATE TABLE archived_users AS SELECT id, name FROM users WHERE inactive;

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-select-into": "warn",
    },
  },
];

Options

This rule has no options.

Edit the SQL — only no-select-into 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-select-into — plus no-syntax-error as a safety net.