-
Notifications
You must be signed in to change notification settings - Fork 73
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
Common database service #4
Comments
@nsa-yoda This looks really interesting. Let me look into this. How we will interact with the database is still somewhat of a question mark for me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As the primary developer for @sphireinc, I created a common Database interface and related base-level implementations for:
For the most part, they're just thin wrappers that create a connection given the common interface. For the implementations, I would remove the HealthCheck stuff and anything else that comes from the "ServerStatusCommon.types" package, and probably any of the
Query
functions as they're largely internal and not general.This is the interface:
and, the Scylla implementation:
Would something like this be beneficial for the framework? If so, I would be more than happy to "donate" the watered down code, no strings attached.
The text was updated successfully, but these errors were encountered: