Skip to content

Widen assets.size to BIGINT#1429

Open
genematx wants to merge 2 commits into
bluesky:mainfrom
genematx:asset-size-bigint-eugene
Open

Widen assets.size to BIGINT#1429
genematx wants to merge 2 commits into
bluesky:mainfrom
genematx:asset-size-bigint-eugene

Conversation

@genematx

@genematx genematx commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

The assets.size column was defined as Integer (int32), so registering a single file larger than ~2.1 GB failed on PostgreSQL with value out of int32 range during INSERT. Change the ORM column to BigInteger and add an alembic migration that runs ALTER TABLE assets ALTER COLUMN size TYPE BIGINT on PostgreSQL.

SQLite is unaffected because its INTEGER affinity already stores 64-bit values.

Checklist

  • Add a Changelog entry
  • Add the ticket number which this PR closes to the comment section

genematx added 2 commits July 9, 2026 14:35
The `assets.size` column was defined as `Integer` (int32), so registering a
single file larger than ~2.1 GB failed on PostgreSQL with
`value out of int32 range` during INSERT. Change the ORM column to
`BigInteger` and add an alembic migration that runs
`ALTER TABLE assets ALTER COLUMN size TYPE BIGINT` on PostgreSQL.
SQLite is unaffected because its `INTEGER` affinity already stores
64-bit values.
@genematx genematx requested a review from danielballan July 9, 2026 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant