Split check constraints

postgresqlprismasupabasemysqldrizzlemigrations
When adding check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration

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 check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
        
        1. First create the check constraint without validation
        2. Then validate existing data in a separate migration
        
        Bad:
        
        ```sql
        -- In a single migration
        ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
        CHECK (age >= 0);
        ```
        
        Good:
        
        ```sql
        -- In first migration: add without validating
        ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
        CHECK (age >= 0)
        NOT VALID;
        
        -- In second migration: validate existing data
        ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
        ```

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 check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0);
```
Good:
```sql
-- In first migration: add without validating
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0)
NOT VALID;
-- In second migration: validate existing data
ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
```

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 check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0);
```
Good:
```sql
-- In first migration: add without validating
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0)
NOT VALID;
-- In second migration: validate existing data
ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
```

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 check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0);
```
Good:
```sql
-- In first migration: add without validating
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0)
NOT VALID;
-- In second migration: validate existing data
ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
```

File Path Patterns:

*.sql

Use with Cline

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

When adding check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0);
```
Good:
```sql
-- In first migration: add without validating
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0)
NOT VALID;
-- In second migration: validate existing data
ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
```

Use with OpenAI Codex

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

When adding check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0);
```
Good:
```sql
-- In first migration: add without validating
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0)
NOT VALID;
-- In second migration: validate existing data
ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
```

Use with Cursor

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

When adding check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0);
```
Good:
```sql
-- In first migration: add without validating
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0)
NOT VALID;
-- In second migration: validate existing data
ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
```

Use with Claude Code

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

When adding check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0);
```
Good:
```sql
-- In first migration: add without validating
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0)
NOT VALID;
-- In second migration: validate existing data
ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
```

Install this rule for Windsurf

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

When adding check constraints in migrations, split the operation into two steps to avoid blocking writes during the table scan:
1. First create the check constraint without validation
2. Then validate existing data in a separate migration
Bad:
```sql
-- In a single migration
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0);
```
Good:
```sql
-- In first migration: add without validating
ALTER TABLE users ADD CONSTRAINT ck_users_age_positive
CHECK (age >= 0)
NOT VALID;
-- In second migration: validate existing data
ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive;
```