Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Introduces Quick Saved Views — a layer on top of Saved Views that enables frontends to present certain views with special, faster access (e.g., pinned views with optional record counts).
QuickSavedViewentity with per-user settings (sortOrder,doCount) linked many-to-one toSavedViewSavedViewsMetaDataProvidergains opt-inisQuickSavedViewEnabledflag, plus auserLevelRecordSecurityLockoption applicable to all saved view tablesQuerySavedViewProcessenriches saved view results with quick view values (type,sortOrder,doCount) when enabled; gracefully no-ops when disabledbuildJoinCrossProductFromJoinContext) to correctly include security-required joins in cross-product construction — needed for queries involving record security locks via joinsDetails
QuickSavedView entity
savedViewId, scoped per user viauserId(savedViewId, userId)prevents duplicatessortOrdercontrols display position;doCounttells frontend whether to execute count queriesSavedViewsMetaDataProvider enhancements
withIsQuickSavedViewEnabled(true)registers the QuickSavedView table and its joinwithUserLevelRecordSecurityLock(lock)applies record security across SavedView, SharedSavedView, and QuickSavedView tablesMemoryRecordStore fix
JoinsContext(which includes security joins) rather than only explicitQueryJoininputsTest plan
lookupQuickViews()for custom behavior🤖 Generated with Claude Code