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

Using rusqlite #11

Open
jalcine opened this issue Feb 27, 2022 · 2 comments
Open

Using rusqlite #11

jalcine opened this issue Feb 27, 2022 · 2 comments

Comments

@jalcine
Copy link

jalcine commented Feb 27, 2022

I already use https://lib.rs/crates/rusqlite (indirectly) in my current projects, and I'd like to use metrics to collect stats about the app, would you be open to a PR to allow people to configure which SQLite backend they'd like to use? It could also reduce the number of dependencies since diesel is for multiple databases, and it's only being used for SQLite here.

@jfro
Copy link
Member

jfro commented Mar 1, 2022

I actually ended up choosing diesel because the dependencies were minimal. It has a bunch but 90% of them are optional. So diesel + sqlite feature is just byteorder, libsqlite3-sys, and common macro crates.

Do you think having optional backends will be much work? the APIs are a bit different so not sure how messy it'd get, but not opposed to the general idea.

@jalcine
Copy link
Author

jalcine commented Mar 1, 2022

I don't think so if the operations are made into some sort of facade that could be then implemented for each implementation. I can take some time this weekend to look into it!

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

2 participants