-
-
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
EOF/script input, default repo, and plain-text output #44
Comments
Hello @jhheider, Thank you for your suggestion all of them are very good for the project, we just need to order them and check requirements for example we need to revamp the CLI args parser and remove clap so we can easy add git files for current path as default value. I will do small research and found requirements then create feature request issue for each point so you, me or anyone else can pick one and work on it Thank you, |
No problem! I know people like to ask for stuff, so hopefully you find these suggestions useful as customer-discovery, if nothing else. :) |
They are very useful, i will mention you once i created issues with full description |
Hello @jhheider, I have implemented two feature request
echo 'SELECT CURRENT_DATE()' | ./gitql.exe -r ../..
echo 'SELECT 1' | gitql TODO
|
These changes look amazing. Thanks for diving into them! |
Thanks for suggestions, enjoy more is coming :D |
|
Very cool project. Three features I could see being immediately useful:
echo SELECT 1 | gitql -r .
goes into a loop redisplaying its prompt forever.echo 'SELECT 1\nexit' | gitql -r .
worksecho SELECT 1 >foo.sql; gitql -r . foo.sql
would be useful.echo SELECT 1\\nexit | gitql
should probably look for the repo in . (and possibly walk up .. until it finds a .git or hits /).gitql -r . foo.sql --csv
would be very useful in pipelines to work with the resultant data without the ascii tables.I may work on some PRs for some of these as time permits (assuming they're not against some philosophy of the project). This is a very cool idea, and these would address a wider range of use cases.
The text was updated successfully, but these errors were encountered: