✅ Eugene lint report

Script name: examples/E2/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(
    id integer generated always as identity
        primary key,
    name text
)

✅ Eugene lint report

Script name: examples/E2/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
set local lock_timeout = '2s'

✅ Statement number 2

alter table authors
    add constraint check_name_not_null
        check (name is not null) not valid

✅ Eugene lint report

Script name: examples/E2/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

alter table authors
    validate constraint check_name_not_null

✅ Eugene lint report

Script name: examples/E2/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
set local lock_timeout = '2s'

✅ Statement number 2

-- eugene trace knows name has a valid not null check, but eugene lint doesn't
-- eugene: ignore E2
alter table authors
    alter name set not null