⚡ Bolt: fix N+1 query in getUserOrders

[fatelessdev]

💡 What: Refactored getUserOrders to fetch order items in a single query using inArray rather than iterating and calling the database per order via Promise.all.
🎯 Why: To resolve an N+1 query problem that slows down the user's order history page load times when they have multiple orders.
📊 Impact: Reduces database queries from N (where N is user orders) + 1 down to exactly 2 queries. Significantly improves page load time and reduces DB load.
🔬 Measurement: Verify by loading the order history for a user with multiple orders; database query logs will show only two queries instead of N+1.

---

PR created automatically by Jules for task 10657853377167194162 started by @f4teless

[google-labs-jules]

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[fatelessdev]

🤖 AI Code Review

📝 Summary & Verdict

This PR refactors the getUserOrders function to resolve an N+1 query problem by fetching all order items in a single batch query using Drizzle ORM's inArray operator, instead of querying for each order individually. It also adds a learning note in .jules/bolt.md documenting this optimization pattern.

Verdict: ✅ Approve
Estimated review effort: 🎯 1/5 | ⏱️ ~2 minutes

---

📝 Walkthrough

Walkthrough

The PR eliminates N+1 queries in getUserOrders by replacing a loop of individual database calls with a single batched query using inArray. It also adds a documentation note about this optimization pattern.

Changes

File(s)	Summary
.jules/bolt.md	Adds a learning note about resolving N+1 queries with Drizzle ORM using inArray.
lib/actions/orders.ts	Refactors getUserOrders to fetch order items in a single query and group them in memory.

---

📊 Visualization

sequenceDiagram
    participant Client
    participant getUserOrders
    participant Database

    Client->>getUserOrders: Request user orders
    getUserOrders->>Database: SELECT orders WHERE userId = ?
    Database-->>getUserOrders: orders[]
    getUserOrders->>Database: SELECT orderItems WHERE orderId IN (orderIds)
    Database-->>getUserOrders: orderItems[]
    getUserOrders->>Client: orders[] with items grouped

Loading

---

Actionable comments posted: 0

Caution

No critical issues found.

Warning

No major issues found.

---

🧹 Nitpick comments (0)

No nitpick comments.

---

Tip

No actionable issues found. The code looks good! ✅

---

💡 Suggestions & Improvements

• Performance: The current implementation is optimal for the given use case. Consider adding a limit/offset for pagination if the number of orders grows large.
• Maintainability: The learning note in .jules/bolt.md is a good practice for knowledge sharing. Ensure it's kept up-to-date with future optimizations.
• Best Practices: The code follows Drizzle ORM best practices by using inArray for batch queries and checking for empty arrays before querying.

---

🤖 Fix all issues with AI agent

No issues to fix. The PR is ready for merge.

---

Powered by LetsReview