-
Notifications
You must be signed in to change notification settings - Fork 86
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
Introduce compatibility with Murmur SQL databases #22
Comments
At the moment, Murmur can read Murmur SQL databases, but it only imports them into our own freeze files. That works could possibly be leveraged. |
Note: the different DBs don't need to be implemented all at once. If someone wants to implement SQLite only, just to get things started, that would be great. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #21.
It would be nice if the Murmur "personality" was able to directly store its state into a Murmur SQL database.
That means we'd have to support the same DBs as Murmur: SQLite, MySQL and Postgres.
Everything should use
database/sql
, taking syntax differences into account for each DB variant.We can worry about which backends to actually ship Murmur with separately. However, the lessons learned during development would come in handy there -- which Go libs worked best? etc.
I've always wanted to play with https://github.com/cznic/sqlite. It's SQLite machine translated to Go. But anything works, including a simple cgo bridge to libsqlite3.
The text was updated successfully, but these errors were encountered: