✅ Eugene lint report

Script name: examples/W14/good/1.sql

This is a human readable SQL lint report generated by eugene. Keep in mind that lint rules can be ignored in the following two ways:

  1. By appending comment directives like -- eugene: ignore E123 to the SQL statement.
  2. By passing --ignore E123 on the command line.

✅ Statement number 1

-- 1.sql
create table authors(
    name text
)

✅ Eugene lint report

Script name: examples/W14/good/2.sql

This is a human readable SQL lint report generated by eugene. Keep in mind that lint rules can be ignored in the following two ways:

  1. By appending comment directives like -- eugene: ignore E123 to the SQL statement.
  2. By passing --ignore E123 on the command line.

✅ Statement number 1

-- 2.sql
create unique index concurrently
    authors_name_key on authors(name)

✅ Eugene lint report

Script name: examples/W14/good/3.sql

This is a human readable SQL lint report generated by eugene. Keep in mind that lint rules can be ignored in the following two ways:

  1. By appending comment directives like -- eugene: ignore E123 to the SQL statement.
  2. By passing --ignore E123 on the command line.

✅ Statement number 1

-- 3.sql
set local lock_timeout = '2s'

✅ Statement number 2

-- eugene: ignore E2
-- This is a demo of W14, so we can ignore E2 instead of the
-- multi-step migration to make the column NOT NULL safely
alter table authors
    alter column name set not null

❌ Eugene lint report

Script name: examples/W14/good/4.sql

This is a human readable SQL lint report generated by eugene. Keep in mind that lint rules can be ignored in the following two ways:

  1. By appending comment directives like -- eugene: ignore E123 to the SQL statement.
  2. By passing --ignore E123 on the command line.

❌ Statement number 1

-- 4.sql
alter table authors
    add constraint authors_name_pkey
        primary key using index authors_name_key

Triggered rules

E9: Taking dangerous lock without timeout

Statement takes lock on public.authors, but does not set a lock timeout.

W14: Adding a primary key using an index

New primary key constraint using index on public.authors, may cause postgres to SET NOT NULL on columns in the index. This lint may be a false positive if the columns are already NOT NULL, ignore it by commenting the statement with -- eugene: ignore: W14.