NEW COMMAND

akron db makemigrations

Automatically generate migration files by comparing your current schema with the last snapshot.

Syntax

1akron db makemigrations [OPTIONS]

Options

Option	Description	Default
--name	Custom name for the migration file	Auto-generated

How It Works

Schema Change Detection

Reads your current akron.json schema definition
Compares it with the last saved schema snapshot
Identifies changes (new tables, modified columns, etc.)
Generates migration steps to transform the database
Creates a migration file in .akron/ directory
Updates the schema snapshot for future comparisons

Examples

Auto-generated Migration Name

Generate migration with automatic naming:

1akron db makemigrations

Expected Output

✅ Generated migration: migration_0001
   File: .akron/migration_0001.json
   Steps: 3

📋 Migration preview:
   1. Create table 'users'
   2. Create table 'posts'
   3. Create table 'comments'

Custom Migration Name

Generate migration with descriptive name:

1akron db makemigrations --name "add_user_authentication"

Expected Output

✅ Generated migration: add_user_authentication
   File: .akron/add_user_authentication.json
   Steps: 2

📋 Migration preview:
   1. Add column 'password_hash' to 'users'
   2. Add column 'last_login' to 'users'

No Changes Detected

When schema hasn't changed:

1akron db makemigrations

Expected Output

✅ No changes detected in schema.

Migration File Structure

Generated Migration File

Example migration file structure:

1{
"name": "add_user_posts",
"timestamp": "2023-12-01T10:30:00.000000",
"steps": [
  {
    "action": "create_table",
    "table": "users",
    "schema": {
      "id": "int",
      "email": "str",
      "username": "str",
      "created_at": "datetime"
    }
  },
  {
    "action": "create_table",
    "table": "posts",
    "schema": {
      "id": "int",
      "title": "str",
      "content": "text",
      "author_id": "int"
    }
  }
],
"checksum": "sha256_hash_of_current_schema"
27}

Supported Migration Actions

Table Operations

create_table - Create new tables
drop_table - Remove existing tables

Column Operations

add_column - Add new columns
drop_column - Remove columns
modify_column - Change column types

Best Practices

✅ Do

• Use descriptive migration names for complex changes
• Generate migrations frequently for small, incremental changes
• Review the migration preview before applying
• Keep your akron.json file in version control

❌ Don't

• Make manual changes to migration files
• Delete migration files after they've been applied
• Skip generating migrations for schema changes
• Make breaking changes without considering data migration

Next Steps

After generating migrations:

Review the generated migration file for accuracy
Run akron db migrate --dry-run to preview changes
Apply migrations with akron db migrate
Check status with akron db status

→ Apply Migrations → Check Status → Schema Management Guide