Niklas

> Note that in all `CacheStampedeBlocker` warnings following the `MetaAnalyzer` error, the reported key is actually properly URL-encoded. The PURL specification requires URL encoding of special characters. However, when accessing...

@rkg-mm Limitation of the ORM we use. It maps the `CLOB` JDBC type (required for "string of unlimited size") to `TEXT` for SQL Server: https://github.com/datanucleus/datanucleus-rdbms/blob/ae929d4a97961ebc53a21a4d0bf4c845ebdf4705/src/main/java/org/datanucleus/store/rdbms/adapter/SQLServerAdapter.java#L173-L175 It's not a decision we...

Based on the query in the exception, it seems to be these: https://github.com/DependencyTrack/dependency-track/blob/cf4f2d4d9b9341ada5da3691e0fe4e13bf0baf7d/src/main/java/org/dependencytrack/model/Vulnerability.java#L175-L179 https://github.com/DependencyTrack/dependency-track/blob/cf4f2d4d9b9341ada5da3691e0fe4e13bf0baf7d/src/main/java/org/dependencytrack/model/Vulnerability.java#L187-L191

I'm wondering if we need `DISTINCT` at all here. The query doesn't look like it would produce duplicate rows, as it operates on the concept of findings (Component Vulnerability pairs)....

Perhaps there is a way to solve this in a "two-stage" CTE, where we: 1. Select only the unique IDs of all applicable findings (this can use `DISTINCT`) 2. Based...

I'll try to reproduce later today.

Confirmed to be broken for MSSQL.

Working around this now by using a subquery instead of a `LEFT JOIN` to perform the ACL check: #3700.

@aravindparappil46 The coverage check is failing, primarily because the change itself is so tiny. We can bypass it, but another solution could be to remove the `set*` methods from the...

> Do let me know if you'd prefer removing all of the setters [...] I think that would be good to avoid future confusion. You could also simply convert `ProjectVersion`...