Eugene 🔒 lint report of examples/E8/bad/1.sql
This is a human readable SQL script safety report generated by eugene.
Keep in mind that lints can be ignored by adding a -- eugene: ignore E123
comment to the SQL statement
or by passing --ignore E123 on the command line.
The migration script passed all the checks ✅
Statement number 1
SQL
-- 1.sql
create table authors (
id integer generated always as identity
primary key,
name text not null
)
No checks matched for this statement. ✅
Eugene 🔒 lint report of examples/E8/bad/2.sql
This is a human readable SQL script safety report generated by eugene.
Keep in mind that lints can be ignored by adding a -- eugene: ignore E123
comment to the SQL statement
or by passing --ignore E123 on the command line.
The migration script did not pass all the checks ❌
Statement number 1
SQL
-- 2.sql
set local lock_timeout = '2s'
No checks matched for this statement. ✅
Statement number 2
SQL
alter table authors
add constraint authors_name_excl
exclude (name with =)
Lints
Creating a new exclusion constraint
ID: E8
Found a new exclusion constraint. This blocks all reads and writes to the table while the constraint index is being created. A safer way is: There is no safe way to add an exclusion constraint to an existing table.
Statement takes AccessExclusiveLock
on public.authors
, blocking reads and writes until constraint authors_name_excl
is validated and has created index.