Failure in exists query for JavaDB

[DaspawnW]

Description

During a trial to implement a hack to get the Java DB as a dedicated server #3560 I detected that the signature of the Exists method doesn't match with the SQL Query that is performed. I'm not a golang developer so maybe my bug report is wrong, but I also so far found no description that proofs that I'm wrong.

Desired Behavior

The Exists function in the javadb/client.go file calls the SelectIndexByArtifactIDAndGroupID(artifactID, groupID) out of the trivy-java-db in the argument order artifactID, groupID.

Actual Behavior

The current behavior is that the function gets called by javadb/client.go in the opposite order with groupID, artifactID.

Reproduction Steps

1. Compare https://github.com/aquasecurity/trivy/blob/main/pkg/javadb/client.go#L119 with https://github.com/aquasecurity/trivy-java-db/blob/main/pkg/db/db.go#L162

Target

None

Scanner

None

Output Format

None

Mode

None

Debug Output

nn

Operating System

nn

Version

latest main branch

Checklist

• Run trivy --reset
• Read the troubleshooting

[afdesk]

@DaspawnW thanks for the report!
created #4620