Fix view sync correctness, cascade delete, N+1 queries, and revert path for VSUM views#224
Merged
ma-mirzaei merged 3 commits into221-add-view-type-neojoin-filesfrom Mar 18, 2026
Merged
Conversation
…e, revert views, null handling, and add unique constraint Co-authored-by: ma-mirzaei <93537795+ma-mirzaei@users.noreply.github.com>
Co-authored-by: ma-mirzaei <93537795+ma-mirzaei@users.noreply.github.com>
Author
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Copilot
AI
changed the title
[WIP] Add support for VSUM views in NeoJoin files
Fix view sync correctness, cascade delete, N+1 queries, and revert path for VSUM views
Mar 18, 2026
ma-mirzaei
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Several correctness and robustness issues in the VSUM views feature introduced in #221/223. Key problems: FK constraint violations on view deletion, N+1 queries when computing sync plans, revert silently wiping views, unsafe
saveAllcast, and commented-out OTP email.Correctness Fixes
VsumViewService.delete()anddeleteByVsum()now deleteVsumViewMetaModelrows first. Without this, deleting a view with metamodel associations violated the FK constraint.deleteByVsumuses a single bulkDELETE ... WHERE vm.vsumView IN :viewsvia a new@Modifying @Query.VsumHistoryService.toSyncRequest()was not mappingrepresentation.getViews()→viewRequests, so every history revert synced views to an empty list. Fixed by mapping stored view snapshots back toViewRequestobjects.mailService.sendOtpMail(...)was commented out, breaking signup/resend-OTP flows. Restored.Performance Fix
buildViewSyncPlan: The oldtoViewKey(VsumView)calledfindAllByVsumView(view)per view in a loop. Replaced with a singlefindAllByVsumViewIn(views)fetch, then grouping by view ID in memory before building the key map.Safety / Stability
(List<VsumViewMetaModel>) vsumViewMetaModelRepository.saveAll(...)replaced withStreamSupport.stream(...).toList().metaModelIds:VsumViewMetaModelService.create()now short-circuits onnull/empty input instead of passingnullto a Spring Data...Inquery (which throws on some implementations).metaModelIdsordering:toList()on aSetstream is nondeterministic; added.sorted()so history snapshots are stable.Schema
V9migration: AddsUNIQUE (vsum_view_id, meta_model_id)onvsum_view_meta_modelto prevent duplicate associations, plus indexes on both FK columns.New Repository Methods
📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.