# Fix Migration Rollback Issue

## Problem
The migration rollback is failing because migration 0011 tries to alter the `job_category` field, but when rolling back to 0002, this field doesn't exist in the target model state.

## Solution
Use the `--fake` flag to mark migrations as unapplied without actually running the database operations:

```bash
python manage.py migrate jobs 0002_job_abroad_job_category_job_job_role --fake
```

This will:
- Mark migrations 0003 through 0013 as unapplied in the django_migrations table
- NOT modify the database schema (since it's already correct)
- Allow you to proceed with your migration workflow

## Alternative Solution
If you want to keep the current state, simply don't roll back:

```bash
# Check current migration status
python manage.py showmigrations jobs

# If you need to apply new migrations, just run:
python manage.py migrate jobs
```

## Why This Happened
Migration 0002 only adds `abroad_job_category_id` and `job_role_id` fields via raw SQL.
The `job_category` field was added in a later migration (likely 0006 or later).
When rolling back, Django can't properly handle the field state transitions.