You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: