Skip to content
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

Overlap with dblog? #131

Open
krlmlr opened this issue Aug 27, 2020 · 2 comments
Open

Overlap with dblog? #131

krlmlr opened this issue Aug 27, 2020 · 2 comments

Comments

@krlmlr
Copy link
Contributor

krlmlr commented Aug 27, 2020

URL: https://github.com/r-dbi/dblog

Blog post: https://www.r-dbi.org/blog/dbi-3-2/, section "Logging with the {dblog} package"

My package uses a different approach -- implementing a LoggingDBIDriver object that wraps another arbitrary DBIDriver object. So far it seems to work well.

I wonder if we should replace logging with custom callbacks that your package could register? That would expand dblog into a generic hooking mechanism. Or perhaps implement helpers that make it easier to wrap DBI backends?

@pachadotdev
Copy link
Collaborator

pachadotdev commented Aug 27, 2020 via email

@jonkeane
Copy link
Collaborator

Hello!

I will admit I did not know that {dblog} existed when I started work on {dittodb}, but it looks like a really neat package. The idea of callbacks sounds like a good one for {dittodb} capturing queries and results, and one that would probably be more stable in the long run.

I'm happy to help out in the effort to add that functionality and think that callback functionality would be something that would be useful even beyond {dittodb}. Do you plan on extending {dblog} to do that? Or Start a new package just for the callback wrapper/registration? (or I guess in principle it could be included in {DBI} itself?) Any way you approach it, I would be happy to help out with development/testing/etc.!

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

No branches or pull requests

3 participants