Fix discord_id type mismatch between model (CharField) and migration (BIGINT) #78

New Issue

cal · 2026-03-27T04:06:52Z

cal commented

2026-03-27 04:06:52 +00:00

Problem

CustomCommandCreator.discord_id is declared as CharField(max_length=20, unique=True) in the model (db_engine.py line 2227) but the migration created it as BIGINT UNIQUE NOT NULL.

The ORM sends values as quoted strings while the column is integer. PostgreSQL will implicitly cast, but this prevents index usage and is a data consistency risk.

Fix

Align the model and migration — either change the model to BigIntegerField or alter the column to VARCHAR(20). Discord snowflake IDs are commonly stored as strings to avoid JavaScript precision issues.

Severity

Medium — index bypass and data consistency risk.

## Problem `CustomCommandCreator.discord_id` is declared as `CharField(max_length=20, unique=True)` in the model (`db_engine.py` line 2227) but the migration created it as `BIGINT UNIQUE NOT NULL`. The ORM sends values as quoted strings while the column is integer. PostgreSQL will implicitly cast, but this prevents index usage and is a data consistency risk. ## Fix Align the model and migration — either change the model to `BigIntegerField` or alter the column to `VARCHAR(20)`. Discord snowflake IDs are commonly stored as strings to avoid JavaScript precision issues. ## Severity Medium — index bypass and data consistency risk.

Claude added the

ai-working

label 2026-03-27 06:01:16 +00:00

cal referenced this issue from a commit

2026-03-27 06:03:46 +00:00

fix: align CustomCommandCreator.discord_id model with BIGINT column (#78)

Claude referenced a pull request that will close this issue

2026-03-27 06:03:59 +00:00

fix: align CustomCommandCreator.discord_id model with BIGINT column (#78) #88

Claude removed the

ai-working

label 2026-03-27 06:04:06 +00:00

Claude commented

2026-03-27 06:04:10 +00:00

PR #88 opens the fix: #88

Two targeted changes:

app/db_engine.py — CharField(max_length=20) → BigIntegerField to match the BIGINT column from the migration
app/routers_v3/custom_commands.py — removed str(discord_id) cast in get_creator_by_discord_id() that was working around the type mismatch

No migration needed — the DB column is already BIGINT; only the ORM model was wrong.

PR #88 opens the fix: https://git.manticorum.com/cal/major-domo-database/pulls/88 Two targeted changes: 1. `app/db_engine.py` — `CharField(max_length=20)` → `BigIntegerField` to match the `BIGINT` column from the migration 2. `app/routers_v3/custom_commands.py` — removed `str(discord_id)` cast in `get_creator_by_discord_id()` that was working around the type mismatch No migration needed — the DB column is already `BIGINT`; only the ORM model was wrong.

Claude added the

ai-pr-opened

label 2026-03-27 06:04:14 +00:00

Sign in to join this conversation.