-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add pgwire PostgreSQL wire protocol interface to CLI #10
Comments
Hello @shah, That's sound very cool and can be used in many projects, thanks you so much for suggestion, My first plan is to start improving the core of GQL and then working on supporting for clients but i think it will be good to start checking PosgreSQL wire protocol and maybe start this module side by side with the core. Thank you, |
GQL now has support for queering multi repositories :D |
That's great news, @AmrDeveloper I appreciate the quick acceptance! |
Hey @AmrDeveloper , your code works great with multiple repositories but we could use a column called |
Nice idea, i will implement it, Thanks for suggestion |
Done, i implemented it now and will be released soon |
@AmrDeveloper , hi there. |
I will release it by the end of this week at most because i am working on big improvements in error handling, functions and performance |
@shah « We have a need to query our Git repos using SQL but with a PosgreSQL wire protocol (so we can use it with psql or any other PostgreSQL client application). » |
GitQL 0.22.0 now has more features from postgreSQL and we can work on the write soon Thank you |
Hello @AmrDeveloper this is a fantastic library, thanks for putting it together!
We have a need to query our Git repos using SQL but with a PosgreSQL wire protocol (so we can use it with
psql
or any other PostgreSQL client application).If you're willing, we'd love to see you add a
server
mode in GQL using Rust pgwire crate.pgwire
does all the hard work of setting up a PostgreSQL wire compatible server and can accept SQL through the wire and pass it into your GQL crates/code.Something like this:
NAME
,NAME2
would be schema names (case insensitive)The above would launch a server listening on port 5432 that would make gql pretend to be a PostgreSQL server. Then, any SQL sent to the GQL server through any PostgreSQL client would be sent to GQL and responses returned using PostgreSQL wire protocol.
We would be able to use
NAME
andNAME2
schema names to combine multiple repos' output.The text was updated successfully, but these errors were encountered: