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
Yeah, this is sort of a limitation of how things work at the moment, with us detecting the SQL statement based on the protocol information. When prepared statement is run, the client supplies the statement ID + the arguments, so the SQL is not actually visible.
I think we need to look into if we can do the same thing we did for gRPC. Namely, if we see the prepare command, then we can create internal mapping SQL statement <> ID and then we can substitute it when someone calls the prepared statement.
Teeing off of #1695
A lot of the spans say
PREPARED STATEMENT .
while we should be capturing the underlying SQL calls.The text was updated successfully, but these errors were encountered: