feat(database): add database indexes to schema_version entity and mig… - #1398
Merged
RUKAYAT-CODER merged 1 commit intoAug 30, 2026
Merged
Conversation
|
@ajulaybeeb Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Thank you for contributing to the project. |
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.
Summary
@Indexdecorators tosrc/entities/schema_version.entity.tscoveringschemaName,checksum,createdAt, and composite("schemaName", "createdAt").src/migrations/1804000000000-add-schema-version-indexes.tsto create these indexes on existing databases with idempotentIF NOT EXISTSclauses and reversibledown()method.Why
The
schema_versiontable lacked indexes on its primary lookup, filtering, and sorting columns (schemaName,checksum,createdAt). As the table grows, lookups by schema name and chronological history ordering force sequential scans. Adding targeted B-tree indexes ensures high-performance lookups and prevents schema drift between the TypeORM entity and the database.Implementation
src/entities/schema_version.entity.ts:Indexfromtypeorm.@Index('IDX_schema_version_schemaName', ['schemaName']).@Index('IDX_schema_version_checksum', ['checksum']).@Index('IDX_schema_version_createdAt', ['createdAt']).@Index('IDX_schema_version_schemaName_createdAt', ['schemaName', 'createdAt']).src/migrations/1804000000000-add-schema-version-indexes.ts:AddSchemaVersionIndexes1804000000000withup()creating all 4 indexes anddown()dropping them.Testing
src/migrations/migration-timestamps.spec.ts.Scope / Risk
schema_versionentity and the new migration file.IF NOT EXISTSto safely run across all environments.Issue
Closes #1239