## ✅ Eugene lint report
Script name: `examples/W14/bad/1.sql`
This is a human readable SQL lint report generated by [eugene](https://github.com/kaaveland/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
```sql
-- 1.sql
create table authors(
name text
)
```
## ✅ Eugene lint report
Script name: `examples/W14/bad/2.sql`
This is a human readable SQL lint report generated by [eugene](https://github.com/kaaveland/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
```sql
-- 2.sql
create unique index concurrently
authors_name_key on authors(name)
```
## ❌ Eugene lint report
Script name: `examples/W14/bad/3.sql`
This is a human readable SQL lint report generated by [eugene](https://github.com/kaaveland/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
```sql
-- 3.sql
set local lock_timeout = '2s'
```
### ❌ Statement number 2
```sql
alter table authors
add constraint authors_name_pkey
primary key using index authors_name_key
```
#### Triggered rules
##### `W14`: [Adding a primary key using an index](https://kaveland.no/eugene/hints/W14/)
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`.