-
Notifications
You must be signed in to change notification settings - Fork 179
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
[database] reporting stored procedures/prepared statements #1491
Comments
Discussed at DB SIG call, decided to rename collection to target and wider its scope. Related: |
if we don't go ahead with #1527, we may also consider introducing something like I don't think I've worked with "named" prepared statements, do you have an example of that? thanks |
Microsoft SQL Server returns an integer handle that isn't worth recording IMO. I believe SQLite does something similar. MySQL, MariaDB, and PostgresSQL support named prepared statements. Invocation is similar to stored procedures.
|
See #1482 (comment)
E.g. query like
CALL procedure-name
should result in the following attributes:db.query.text = "CALL procedure-name"
db.operation.name = "CALL"
db.collection.name = "procedure-name"
We should document that collection name can contain stored procedure/prepared statement name
The text was updated successfully, but these errors were encountered: