Closed ghost closed 1 year ago
I don't understand at all how usql which is a CLI client for multiple databases is related to git-bug which is an issue tracker. I can't think of any reasons to integrate these two apps and I don't see them in the issue description here either.
Hi nineinchnick, thank you for feedback.
I don't understand at all how usql which is a CLI client for multiple databases is related to git-bug which is an issue tracker. I can't think of any reasons to integrate these two apps and I don't see them in the issue description here either.
git-bug is a decentralized, distributed bugtracker... for example, you can synchronize issues in different platforms like GitHub and Gitlab for example... an... something usql(CLI client for multiple databases) can help to replicate issues of git-bug in different databases...
so... if one of these platforms goes down, as I distribute issues in different databases, I'm sure there is a process similar to what happens in protocols like matrix: interoperability, that is, git-bug doesn't stop working because there are bridges that communicate with different bases data or platforms - this would only be possible with a client like usql for different databases and a git-bug client that synchronizes some problems on different platforms
Replicating data between databases is out of the scope of usql.
Hi nineinchnick.
Replicating data between databases is out of the scope of usql.
thank you for feedback.
Hi everyone.
concept
context
feedback/question