Adjust expectations regarding OpenTelemetry JDBC operation names after Hibernate ORM bump to 6.5

[michalvavrik]

Summary

After quarkusio/quarkus#40102 actual DB query changes as now, during the UPDATE with JDBC MSSQL, the alias is used. The DB statement now looks like this: update ae1_0 set amount=?,updatedAt=? from account ae1_0 where ae1_0.accountNumber=? which results in alias being used instead of database name.

I could not find anything in OTel specs in this regards, the closes I got is the first link open-telemetry/opentelemetry-java-instrumentation#7821, but it seems like a grey area and I don't think it's a bug.

Please select the relevant options.

• Bug fix (non-breaking change which fixes an issue)
• Dependency update
• Refactoring
• Backport
• New scenario (non-breaking change which adds functionality)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices