⚡ Bolt: Add DB index for machine name sorting #786
Conversation
This change adds a database index to the `name` column of the `machines` table. The `name` column is frequently used for sorting machines in the main dashboard, machine list, and report pages. Adding an index avoids sequential scans and improves query performance as the dataset grows. - Updates `src/server/db/schema.ts` to include `idx_machines_name` - Generates migration file `drizzle/0002_sharp_anthem.sql`
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
⚡ Performance Optimization
What: Added a B-tree index to the
machines.namecolumn in the database schema.Why: Multiple key pages (Issues, Machine List, Reports) sort machines by name. Without an index, the database performs a sequential scan and sort on every request. This optimization enables the database to retrieve sorted results directly from the index, significantly reducing query cost and latency.
Impact: Eliminates O(N log N) sorting cost during queries, making machine lists load consistently fast regardless of database size.
Verification:
orderByusage insrc/app.PR created automatically by Jules for task 15166968855803363377 started by @timothyfroehlich