-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix incorrect query and args handling #11
Conversation
Still plumbing this in my project to test, but looking at the changes I don't think this is what you want to do? We still want to create the |
Update: I was able to build my project against your branch after battling it out a bit more about modules. I can confirm this is not the behaviour we want as the tag is removed even if |
sql.go
Outdated
span.SetLabel("query", query) | ||
if !c.OmitArgs { | ||
span.SetLabel("args", formatArgs(args)) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So...this was previously good! We don't want to remove this check as far as I understand. Instead we want to do this in other places which are adding the args
tag such as ExecContext
and QueryContext
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's odd ... the call to logQuery
a bit later is supposed to take care of that, I'll look into why that is broken
29ae18d
to
0aee700
Compare
Issues fixed, fix corrected, merging this :) |
😍 Yay, thanks Luna! 🏆 |
Closes #10