Skip to content

Support JDBC spans for Druid-wrapped Oracle statements#144

Merged
lrwh merged 1 commit into
guancefrom
lr_oracle_10g
Mar 23, 2026
Merged

Support JDBC spans for Druid-wrapped Oracle statements#144
lrwh merged 1 commit into
guancefrom
lr_oracle_10g

Conversation

@lrwh
Copy link
Copy Markdown
Collaborator

@lrwh lrwh commented Mar 23, 2026

Description
This PR fixes missing business SQL spans for Oracle JDBC when the application uses Druid connection wrappers.

Changes in this PR:

  • add Druid wrapped connection and prepared statement classes to JDBC instrumentation matching
  • prevent duplicate prepared statement spans by adding call-depth protection
  • add a regression test covering Druid-wrapped prepared statement tracing

Result:

  • business Oracle SQL executed through Druid/MyBatis can now produce JDBC prepared statement spans correctly

Add Druid JDBC wrapper coverage for connection/prepared statement instrumentation, prevent duplicate prepared statement spans via call-depth tracking, and add a Druid regression test for prepared statement tracing.
@lrwh lrwh merged commit c9df885 into guance Mar 23, 2026
@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants