Fix broken global vuln audit view for MSSQL #3700
Merged
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.
Description
Fixes broken global vulnerability audit view for MSSQL.
Tested with MSSQL, PostgreSQL, and H2.
Addressed Issue
Fixes #3692
Additional Details
MSSQL does not support
DISTINCT
for columns of typeTEXT
, whichDESCRIPTION
andRECOMMENDATION
are.Because the database schema is controlled by DataNucleus, and DataNucleus doesn't allow us to customize column types for specific RDBMSes, changing the respective columns to
VARCHAR(MAX)
is not possible.DISTINCT
was needed because finding rows are joined with thePROJECT_ACCESS_TEAMS
table, to support portfolio ACLs. If a user is member of multiple teams, the query would yield a duplicate row for each permitted team the user is a member of.The need for
DISTINCT
is eliminated by converting the ACL check from aLEFT JOIN
to anEXISTS
subquery.Checklist
This PR implements an enhancement, and I have provided tests to verify that it works as intendedThis PR introduces changes to the database model, and I have added corresponding update logicThis PR introduces new or alters existing behavior, and I have updated the documentation accordingly