eugene 0.8.3

Careful with That Lock, Eugene
Documentation
## ✅ Eugene lint report

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

## ❌ Eugene lint report

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

### ✅ Statement number 2

```sql
alter table authors
    alter column name set not null
```

### ❌ Statement number 3

```sql
-- eugene: ignore E2, E4
alter table authors
    alter column email set not null
```

#### Triggered rules

##### `W12`: [Multiple `ALTER TABLE` statements where one will do]https://kaveland.no/eugene/hints/W12/

Multiple `ALTER TABLE` statements on `public.authors`. Combine them into a single statement to avoid scanning the table multiple times..