You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JDBC detector matches results with no actual connection string (e.g., jdbc:postgresql://), resulting in extraneous verification attempts with no/default information.
Should we check this in the code logic and filter out the invalid ones? e.g
// isEmptyConnectionString check if the connectionString has something after "://"funcisEmptyConnectionString(connStrstring) bool {
parts:=strings.Split(connStr, "://")
returnlen(parts[1]) >0
}
The JDBC detector matches results with no actual connection string (e.g.,
jdbc:postgresql://
), resulting in extraneous verification attempts with no/default information.MySQL
Postgres
The text was updated successfully, but these errors were encountered: