Sonarly Claude Code
726969aa33
https://sonarly.com/issue/3775?type=bug The `FindAllCoreViews` query generates a single SQL statement with 6 LEFT JOINs across 5 independent one-to-many relationships, creating a cartesian product explosion that takes 1618ms. Caching masks the issue for most requests, but cache misses cause ~2s page loads. Fix: The `findByWorkspaceId` method in `view.service.ts` loaded 6 relations via TypeORM's default `join` strategy, which generates a **single SQL statement with 6 LEFT JOINs**. When 5 of those are independent one-to-many relationships (viewFields, viewFilters, viewSorts, viewGroups, viewFilterGroups), the result set explodes combinatorially — a view with 20 fields × 5 filters × 3 sorts × 5 groups × 2 filter groups yields 3,000 rows for a single view. Two changes were made: **1. Add `relationLoadStrategy: 'query'`** — instructs TypeORM to issue one `SELECT … WHERE viewId IN (…)` per relation instead of a single monolithic JOIN query. This avoids the cartesian product entirely. Available since TypeORM 0.3.12; the project uses 0.3.20. **2. Remove the `'workspace'` relation** — the `workspace` ManyToOne (inherited from `WorkspaceRelatedEntity`) adds 30+ workspace columns to every row of the result set. It is not needed: `ViewDTO` only exposes `workspaceId` (a scalar column already on the view row), and no call site downstream uses `view.workspace`. ```typescript file=packages/twenty-server/src/engine/metadata-modules/view/services/view.service.ts lines=380-395 const views = await this.viewRepository.find({ where: { workspaceId, deletedAt: IsNull(), ...(viewTypes && viewTypes.length > 0 && { type: In(viewTypes) }), }, order: { position: 'ASC' }, relations: [ 'viewFields', 'viewFilters', 'viewSorts', 'viewGroups', 'viewFilterGroups', ], relationLoadStrategy: 'query', }); ``` After the fix TypeORM will issue 6 lean, targeted queries (one per relation) rather than one 120-column cartesian-product query, reducing the expected cache-miss latency from ~1600ms to well under 100ms.
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See: 🚀 Self-hosting 🖥️ Local Setup
Why Twenty
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in Open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Personalize layouts with filters, sort, group by, kanban and table views
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!