Skip to content

fix: Melhoria de desempenho com uso de indices no endpoint fetchInstance #2568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
iagocotta wants to merge 1 commit into
base: develop
Choose a base branch
from
+16 −0
Open

fix: Melhoria de desempenho com uso de indices no endpoint fetchInstance #2568

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions ...mysql-migrations/20260527000000_add_index_instance_client_name_token_number/migration.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
-- CreateIndex
CREATE INDEX `Instance_clientName_idx` ON `Instance`(`clientName`);

-- CreateIndex
CREATE INDEX `Instance_token_idx` ON `Instance`(`token`);

-- CreateIndex
CREATE INDEX `Instance_number_idx` ON `Instance`(`number`);
8 changes: 8 additions & 0 deletions ...resql-migrations/20260527000000_add_index_instance_client_name_token_number/migration.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
-- CreateIndex
CREATE INDEX IF NOT EXISTS "Instance_clientName_idx" ON "Instance"("clientName");

-- CreateIndex
CREATE INDEX IF NOT EXISTS "Instance_token_idx" ON "Instance"("token");

-- CreateIndex
CREATE INDEX IF NOT EXISTS "Instance_number_idx" ON "Instance"("number");
Comment on lines +2 to +8
Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot May 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue (bug_risk): Using IF NOT EXISTS in migrations can hide schema drift and make future index changes harder.

This can let an index with the wrong definition (columns, collation, options) slip through, since the migration appears to succeed even though the index shape doesn’t match what you expect. Given that Prisma migrations are linear and controlled, it’s safer to omit IF NOT EXISTS so any mismatch fails loudly and surfaces schema drift early.