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

Compatibility with MySQL Workbench #722

Open
dpordomingo opened this issue Mar 6, 2019 · 0 comments
Open

Compatibility with MySQL Workbench #722

dpordomingo opened this issue Mar 6, 2019 · 0 comments
Labels
empathy Issue filed as as part of empathy sessions feature

Comments

@dpordomingo
Copy link
Contributor

discovered at https://github.com/src-d/empathy-sessions/issues/37

considering the old #361 (comment), I'm not sure if you already discarded the interoperability with MySQL Workbench, so feel free to direct close if it makes no sense at all 🗡️

I tried to connect to gitbase using MySQL Workbench 6.3 (even it's not explicitly supported by gitbase) and I found some issues that made Workbench to crash:

  • current_user() is not supported
  • show status is not supported
  • show engines is not supported

I could mock data for all of them in local gitbase, and doing so Workbench was able to start with a warning:

Incompatible/nonstandard server version or connection protocol detected ().

A connection to this database can be established but some MySQL Workbench features may not work
properly since the database is not fully compatible with the supported versions of MySQL.

MySQL Workbench is developed and tested for MySQL Server versions 5.1, 5.5, 5.6 and 5.7

> Continue anyway           > Abort 

If you continue 😉 , Workbench opens the pannel with the connection, but there is no tables shown in the left panel, plus a log:

# 15:32:31  Error loading schema content
#           Error Code: 0
#           MySQL_ResultSet::getString: invalid value of 'columnIndex'

And fetching commits also fails:

select * from commits
# 15:35:27  select * from commits LIMIT 0, 10
#           Fetching...
# 15:35:27  select * from commits LIMIT 0, 10
#           Error Code: 0
#           0) . Please reportn charsetnr (

I wonder if you could give some hint to let someone work on this during some OSD 🤔 ... or just discourage it if you see it an impossible thing.

@smola smola added the empathy Issue filed as as part of empathy sessions label Mar 6, 2019
@kuba-- kuba-- added the feature label Jun 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
empathy Issue filed as as part of empathy sessions feature
Projects
None yet
Development

No branches or pull requests

4 participants