Add fallback logic for trends visualization query #23
Conversation
- Wraps the advanced raw SQL query in a try/catch block. - Implements a fallback strategy using Drizzle's query builder (limit 500, ordered by latest) if the primary query fails. - Performs in-memory aggregation of the fallback data to match the expected format. - Returns static mock data if both database attempts fail.
|
👋 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. |
Codacy's Analysis Summary0 new issue (≤ 0 issue) Review Pull Request in Codacy →
|
Implemented a robust fallback mechanism for the trends visualization data loading. If the primary raw SQL query fails (e.g. due to dialect issues or permissions), the system now attempts a simpler Drizzle query to fetch the latest 500 reports and aggregates them in-memory. If that also fails (e.g. database down), it gracefully degrades to static mock data.
PR created automatically by Jules for task 4466707858109669170 started by @lightmyfireadmin