djm 0.0.3a0

Generate goose-style SQL migrations from Django migrations, plus base model mixins

DJM

Generate SQL migrations from Django models for goose, golang-migrate, SQLx (Rust), or Diesel (Rust). One app: define models in djm, run Django migrations, then export to SQL.

Why

I build a lot of POCs in Django. When one works and needs to turn into something with real business impact, I usually rewrite in Go or Rust. I only want to rewrite the business logic—not waste time turning existing tables into SQL migrations by hand. DJM exports the schema from Django so I can drop it into a Go (goose) or Rust (SQLx, Diesel) project and focus on the code that matters.

Requirements

• Python ≥3.13
• Django ≥6.0

Quick start

pip install djm
djm init myapp
cd myapp

Edit models in djm/models/, then:

pip install -e .   # or: uv sync
python manage.py makemigrations djm
python manage.py migrate
python manage.py goose   # or: python manage.py sqlx, or: python manage.py diesel

Use the generated SQL with your migration tool (goose, golang-migrate, SQLx, or Diesel).

CLI

Command	Description
djm init [path]	Create a new project (default: current directory).
djm goose [-o DIR]	Generate goose-style SQL (default: migrations).
djm sqlx [-o DIR]	Generate SQLx-style SQL (default: migrations).
djm diesel [-o DIR]	Generate Diesel CLI migrations (default: migrations).

Run djm goose, djm sqlx, and djm diesel from the project root (where manage.py is).

Project layout (after djm init)

Path	Purpose
djm/	App for your models; includes goose, sqlx, and diesel management commands.
base/	Abstract mixins: UUIDPrimaryKeyMixin, TimestampsMixin, SoftDeleteMixin, SortNumberMixin.
core/	Django project (settings, urls).

Generating SQL

Goose (one file per migration, up/down in one file):

python manage.py goose [--output-dir DIR] [--no-sql-extension]

SQLx (sqlx-cli reversible format: .up.sql and .down.sql per migration):

python manage.py sqlx [--output-dir DIR] [--no-sql-extension]

Diesel (Diesel CLI: one subdirectory per migration with up.sql and down.sql):

python manage.py diesel [--output-dir DIR]

Output is migrations/<name>/up.sql and migrations/<name>/down.sql. Use with diesel migration run and diesel migration redo.

All commands default to the same dir (migrations). Each marks the directory so the others won’t overwrite it. Use different --output-dir values if you generate for more than one tool (e.g. goose -o goose_migrations, diesel -o diesel_migrations).

Base mixins

Import from base.models:

• UUIDPrimaryKeyMixin – UUID primary key (uuid6).
• TimestampsMixin – created, updated.
• SoftDeleteMixin – deleted (nullable datetime).
• SortNumberMixin – order_no and default ordering.

Mixins are abstract; you don’t need base in INSTALLED_APPS unless you add migrations there.

Makefile

From project root:

• make help – list targets
• make install – install dependencies (uv sync)
• make migrate – apply Django migrations
• make goose – generate goose SQL (default: migrations)
• make sqlx – generate SQLx SQL (default: migrations)
• make diesel – generate Diesel CLI migrations (default: migrations)
• make test – run tests
• make clean – remove generated SQL and __pycache__
• make build – build wheel/sdist

Use make goose OUT=dir, make sqlx OUT=dir, or make diesel OUT=dir to override the output directory.

Development

From the repo:

pip install -e .
python manage.py test djm

Notes

• SQL is generated for the database in settings.DATABASES["default"]. Use PostgreSQL/MySQL in settings if you need that dialect.
• Down migrations use Django’s sqlmigrate --backwards under the hood.

Credits

This project was largely built with AI. I wrote only the initial rough version that generated SQL; the rest—SQLx support, refactors, tests, CLI, and docs—came from iterating with AI.