-
Notifications
You must be signed in to change notification settings - Fork 39
Logging SQL queries and results #78
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
Comments
You are correct, currently there are no logging callbacks available. I hope to add some in the future, but I haven't decided on a specific interface and the exact points when a callback is called yet. Any input is appreciated, feel free to list your ideas and what callbacks you envision. |
Thank you for the clarification. I imagine a logging interface similar to the following:
The user would set the log handler by calling
In the future, the logging interface could be made more fine-grained, e.g. by allowing logging to be configured per-connection or maybe even per-query. However initially I would be happy to have just a way to enable/disable logging globally. |
Even after overwriting all the log functions I still with the examples from test/log I still get a print: |
This looks like an exception, so maybe you didn't catch it and by default its |
I'm quite sure it's not an exception but I'll try to make a complete example tomorrow 👍 It's from a create table if not exists statement |
Hi,
I have a project that uses taopq and I am looking for a way to add logging of the PostgreSQL queries/results that taopq emits.
I checked the code but did not see a way to log the generated SQL queries and/or the returned results, e.g. through a calling callback. In case I am not missing something, are there any plans to add logging to the library in the future?
The text was updated successfully, but these errors were encountered: