Add check constraints safely in SQLAlchemy

postgresqlsqlalchemyalembicmigrations
When adding check constraints that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',

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: "*.py"
      instructions: |
                
        When adding check constraints that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
        
        Bad:
        
        ```python
        def upgrade():
            # Directly creating a check constraint blocks writes during table scan
            op.create_check_constraint(
                'ck_users_age_positive',
                'users',
                'age >= 0'
            )
        ```
        
        Good:
        
        ```python
        # Migration 1: Create check constraint without validation
        
        def upgrade():
            # Create the check constraint without validating existing data (non-blocking)
            op.create_check_constraint(
                'ck_users_age_positive',
                'users',
                'age >= 0',
                postgresql_not_valid=True
            )
        ```
        
        ```python
        # Migration 2: Validate existing data
        
        def upgrade():
            op.execute('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 that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0'
    )
```
Good:
```python
# Migration 1: Create check constraint without validation
def upgrade():
    # Create the check constraint without validating existing data (non-blocking)
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0',
        postgresql_not_valid=True
    )
```
```python
# Migration 2: Validate existing data
def upgrade():
    op.execute('ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive')
```

File Path Patterns:

*.py

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 that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0'
    )
```
Good:
```python
# Migration 1: Create check constraint without validation
def upgrade():
    # Create the check constraint without validating existing data (non-blocking)
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0',
        postgresql_not_valid=True
    )
```
```python
# Migration 2: Validate existing data
def upgrade():
    op.execute('ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive')
```

File Path Patterns:

*.py

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 that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0'
    )
```
Good:
```python
# Migration 1: Create check constraint without validation
def upgrade():
    # Create the check constraint without validating existing data (non-blocking)
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0',
        postgresql_not_valid=True
    )
```
```python
# Migration 2: Validate existing data
def upgrade():
    op.execute('ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive')
```

File Path Patterns:

*.py

Use with Cline

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

When adding check constraints that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0'
    )
```
Good:
```python
# Migration 1: Create check constraint without validation
def upgrade():
    # Create the check constraint without validating existing data (non-blocking)
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0',
        postgresql_not_valid=True
    )
```
```python
# Migration 2: Validate existing data
def upgrade():
    op.execute('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 that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0'
    )
```
Good:
```python
# Migration 1: Create check constraint without validation
def upgrade():
    # Create the check constraint without validating existing data (non-blocking)
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0',
        postgresql_not_valid=True
    )
```
```python
# Migration 2: Validate existing data
def upgrade():
    op.execute('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 that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0'
    )
```
Good:
```python
# Migration 1: Create check constraint without validation
def upgrade():
    # Create the check constraint without validating existing data (non-blocking)
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0',
        postgresql_not_valid=True
    )
```
```python
# Migration 2: Validate existing data
def upgrade():
    op.execute('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 that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0'
    )
```
Good:
```python
# Migration 1: Create check constraint without validation
def upgrade():
    # Create the check constraint without validating existing data (non-blocking)
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0',
        postgresql_not_valid=True
    )
```
```python
# Migration 2: Validate existing data
def upgrade():
    op.execute('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 that could affect large tables, create the constraint with `NOT VALID` first to avoid blocking writes during the validation scan.
Bad:
```python
def upgrade():
    # Directly creating a check constraint blocks writes during table scan
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0'
    )
```
Good:
```python
# Migration 1: Create check constraint without validation
def upgrade():
    # Create the check constraint without validating existing data (non-blocking)
    op.create_check_constraint(
        'ck_users_age_positive',
        'users',
        'age >= 0',
        postgresql_not_valid=True
    )
```
```python
# Migration 2: Validate existing data
def upgrade():
    op.execute('ALTER TABLE users VALIDATE CONSTRAINT ck_users_age_positive')
```