Split unique constraints in PostgreSQL

postgresqlprismasupabasedrizzlemigrations
When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```

Install this rule for wispbit

Add this rule to wispbit and it will run when you open a pull request

Install this rule for Coderabbit

Copy the configuration below and add it to your repository as .coderabbit.yml in your project root.

reviews:
  path_instructions:
    - path: "*.sql"
      instructions: |
                
        When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
        
        Bad:
        
        ```sql
        -- Creates a unique constraint directly, which blocks reads and writes
        ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
        ```
        
        Good:
        
        ```sql
        -- First create a unique index concurrently (non-blocking)
        CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
        
        -- Then add the constraint using the existing index
        ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
        ```

Install this rule for Greptile

Greptile rules can be added through the web interface. Please see this documentation for details on how to add custom rules and context.

When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```
Good:
```sql
-- First create a unique index concurrently (non-blocking)
CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
-- Then add the constraint using the existing index
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
```

File Path Patterns:

*.sql

Install this rule for GitHub Copilot

Copilot instructions can be added through the interface. See the documentation for details on how to create coding guidelines.

When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```
Good:
```sql
-- First create a unique index concurrently (non-blocking)
CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
-- Then add the constraint using the existing index
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
```

File Path Patterns:

*.sql

Install this rule for Graphite Diamond

Diamond custom rules can be added through the interface. See the documentation for details on how to create custom rules.

When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```
Good:
```sql
-- First create a unique index concurrently (non-blocking)
CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
-- Then add the constraint using the existing index
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
```

File Path Patterns:

*.sql

Use with Cline

Copy the rule below and ask Cline to review your code using this rule

When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```
Good:
```sql
-- First create a unique index concurrently (non-blocking)
CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
-- Then add the constraint using the existing index
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
```

Use with OpenAI Codex

Copy the rule below and ask OpenAI Codex to review your code using this rule

When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```
Good:
```sql
-- First create a unique index concurrently (non-blocking)
CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
-- Then add the constraint using the existing index
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
```

Use with Cursor

Copy the rule below and ask Cursor to review your code using this rule

When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```
Good:
```sql
-- First create a unique index concurrently (non-blocking)
CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
-- Then add the constraint using the existing index
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
```

Use with Claude Code

Copy the rule below and ask Claude Code to review your code using this rule

When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```
Good:
```sql
-- First create a unique index concurrently (non-blocking)
CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
-- Then add the constraint using the existing index
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
```

Install this rule for Windsurf

To set up rules for Windsurf Reviews, please see this documentation 

When adding unique constraints in PostgreSQL, create the unique index concurrently first before adding the constraint to avoid blocking reads and writes.
Bad:
```sql
-- Creates a unique constraint directly, which blocks reads and writes
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE (email);
```
Good:
```sql
-- First create a unique index concurrently (non-blocking)
CREATE UNIQUE INDEX CONCURRENTLY users_email_unique_idx ON users (email);
-- Then add the constraint using the existing index
ALTER TABLE users ADD CONSTRAINT users_email_unique UNIQUE USING INDEX users_email_unique_idx;
```