Skip to content
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

Improve/replace srcd sql client #154

Closed
smacker opened this issue Dec 4, 2018 · 7 comments · Fixed by #353
Closed

Improve/replace srcd sql client #154

smacker opened this issue Dec 4, 2018 · 7 comments · Fixed by #353
Assignees

Comments

@smacker
Copy link
Contributor

smacker commented Dec 4, 2018

I had expected to have the same experience as with standard mysql client. Few things I missed:

  • Can't switch to display results per column (\G in the normal client)
  • No pager
  • When I use some special keys it messes with the output (starting removing lines and so on)
@carlosms
Copy link
Contributor

carlosms commented Dec 5, 2018

Maybe we could detect if you have the mysql client installed and launch it, and keep the current code as a fallback. This way we don't add a hard requirement, but still improve the experience using the regular client when possible.

cc @campoy

@smacker
Copy link
Contributor Author

smacker commented Dec 5, 2018

We can also run docker exec -it mysql-cli/image mysql.

@smacker
Copy link
Contributor Author

smacker commented Mar 15, 2019

@smacker smacker self-assigned this Mar 15, 2019
@se7entyse7en
Copy link
Contributor

Ok, I've just self-assigned #271, but I haven't actually started working on it. Given that all those issues don't seem to be urgent, maybe better to not start the issues that this one will fix?

@marnovo
Copy link
Member

marnovo commented Mar 15, 2019

Giving the green light.

Backlog issue created at: https://github.com/src-d/backlog/issues/1387

From Slack:

Santiago Mola [12:01 PM]
can you look at this? src-d/sourced-ce#154
GitHub
Improve/replace srcd sql client · Issue #154 · src-d/engine
I had expected to have the same experience as with standard mysql client. Few things I missed: Can't switch to display results per column (\G in the normal client) No pager When I use some spec...

since I told them to take significant fixes in, they wanted to start with this, which should solve quite a few usability issues and bugs in one go

Marcelo Novaes [12:23 PM]
Ok, so in practice this means killing a custom REPL and replacing with the mysql one OR working ours to be more akin to mysql one?

Santiago Mola [12:25 PM]
Yes, it's replacing our current REPL with the official mysql client

Marcelo Novaes [12:25 PM]
Haha could be written in plain English like that 😂

Santiago Mola [12:26 PM]
mysql official repl is not awesome but works and it's what DP team actually uses
I'd say it's a good move until the day we decide we want to do our own super awesome REPL

Marcelo Novaes [12:30 PM]
Sounds sensible, do we have an estimation? Can we get this working/integrated/tested before the release?

Santiago Mola [12:34 PM]
there should be a PR for it on Monday, so yes
Monday/Tuesday, given the OSD

Marcelo Novaes [12:34 PM]
Great, I’ll paste the conversation there and give the green light.

@carlosms
Copy link
Contributor

Ok, I've just self-assigned #271, but I haven't actually started working on it. Given that all those issues don't seem to be urgent, maybe better to not start the issues that this one will fix?

I think #271 is not related to the mysql client change, it must have been a typo. @smacker?

@smacker
Copy link
Contributor Author

smacker commented Mar 15, 2019

true. Must be mixed up with some other number.

@smacker smacker mentioned this issue Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants