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
@roblaszczak, @m110 I hope to contribute an SQLite driver some time this summer. I am opening this issue to collect ideas and to hear suggestions from you and the community. Two questions to kick off:
I noticed that all the drivers are in separate repositories, and I find it a bit odd as opposed to keeping them together in the same repo with their own go.mod file. Another project wouldn't be able to use them as they are too specific. Nonetheless, how would like me to go about implementation? Follow the same pattern?
I enjoy working with https://github.com/zombiezen/go-sqlite driver. It does not use the standard library sql interfaces and carries SQLite-specific benefits because of it. Also no CGO. Is it ok if I use it for watermill implementation at least initially? I can do an additional standard lib-compatible one later - it should not be hard to re-implement once it is done.
The text was updated successfully, but these errors were encountered:
@roblaszczak, @m110 I hope to contribute an SQLite driver some time this summer. I am opening this issue to collect ideas and to hear suggestions from you and the community. Two questions to kick off:
I noticed that all the drivers are in separate repositories, and I find it a bit odd as opposed to keeping them together in the same repo with their own go.mod file. Another project wouldn't be able to use them as they are too specific. Nonetheless, how would like me to go about implementation? Follow the same pattern?
I remember discussing with someone who is all "drivers" in one repo in a similar project, and it's a pain 😅
It kinda works now when all drivers are separate, so we'll prefer not to make a precedence.
I enjoy working with https://github.com/zombiezen/go-sqlite driver. It does not use the standard library sql interfaces and carries SQLite-specific benefits because of it. Also no CGO. Is it ok if I use it for watermill implementation at least initially? I can do an additional standard lib-compatible one later - it should not be hard to re-implement once it is done.
So https://github.com/zombiezen/go-sqlite sounds like a nice alternative! It would be just perfect to not expose details of that library anywhere - so we could eventually swap the driver in the future if possible.
@roblaszczak, @m110 I hope to contribute an SQLite driver some time this summer. I am opening this issue to collect ideas and to hear suggestions from you and the community. Two questions to kick off:
go.mod
file. Another project wouldn't be able to use them as they are too specific. Nonetheless, how would like me to go about implementation? Follow the same pattern?The text was updated successfully, but these errors were encountered: