Repository navigation
Fix TypeORM migration name format mismatch in database initialization - #39
Merged
Merged
Conversation
Co-authored-by: buzz-code <72219643+buzz-code@users.noreply.github.com>
…rts successfully Co-authored-by: buzz-code <72219643+buzz-code@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix db initialization for TypeORM migration
Fix TypeORM migration name format mismatch in database initialization
Dec 21, 2025
buzz-code
marked this pull request as ready for review
December 21, 2025 16:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TypeORM's migration runner was attempting to re-execute 124 already-applied migrations, causing the backend container to crash on startup with "table already exists" errors. The root cause: migration names in the database lacked the timestamp suffix that TypeORM expects when matching against source code class names.
Changes
db/data.sql: Corrected all 124 migration entries from format(timestamp, 'ClassName')to(timestamp, 'ClassName{timestamp}')to match TypeORM's class naming conventionExample:
This aligns with TypeORM's expectation that migration class names follow the pattern
{DescriptiveName}{Timestamp}as defined in the source files (e.g.,export class KlassAddReferenceId1675356165986 implements MigrationInterface).The migration runner now correctly recognizes all migrations as executed, preventing re-execution attempts and startup failures.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.