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

Unable to create a connection using a Mysql 4 database #697

Closed
djib123456 opened this issue Jul 2, 2019 · 15 comments

Comments

Projects
None yet
2 participants
@djib123456
Copy link

commented Jul 2, 2019

bugreport_heidiSQL.txt

Steps to reproduce this issue

  1. Step 1: Install and start Mysql4 on your computer
  2. Step 2: Create a database in Mysql 4
  3. Step 3: Start HeidiSQL and try to connect to the previously created database
  4. Then you get a error message saying : << Column 'Name' not available >>

Current behavior

Error message saying : << Column 'Name' not available >>

Expected behavior

We should be able to connect without issue, just like in the previous Heidi versions.

Environment

No particular setup is related to that issue, I use a basic windows computer, everything was working perfectly, then I updated HeidiSQL, and all my bases using Mysql 4 are not usable anymore (only in HeidiSQL).

  • **HeidiSQL version: 10.2.0.5599 **
@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 2, 2019

The code from the callstack is only executed when the server has a version > 5.0.10. Could you please post the result of SELECT VERSION() here.

@djib123456

This comment has been minimized.

Copy link
Author

commented Jul 2, 2019

The result is 4.0.27-nt

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 3, 2019

Ok, that should normally avoid running that SHOW TRIGGERS query. Unless the version variables say something else. Could you please telll what the "version" and "version_comment" says on that server:

SELECT @@version, @@version_comment
@djib123456

This comment has been minimized.

Copy link
Author

commented Jul 3, 2019

I get the error " unknown system variable 'version_comment' "

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 3, 2019

Ah well, then what is @@version then? I suppose the same as what SELECT VERSION() returned?

@djib123456

This comment has been minimized.

Copy link
Author

commented Jul 3, 2019

Yes, it is the same result

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 3, 2019

Just started my good old MySQL 4.0 instance, and I can now reproduce the error. Even worse, in some cases HeidiSQL is terminated without any error message.

@ansgarbecker ansgarbecker added bug and removed needs-info labels Jul 3, 2019

@ansgarbecker ansgarbecker added this to the v10.3 milestone Jul 3, 2019

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 3, 2019

When forcing HeidiSQL to use libmysql.dll instead of the newer libmariadb.dll, that works as expected.

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 3, 2019

If you rename or delete libmariadb.dll from your HeidiSQL folder, you should be fine for the moment. This is a workaround, not a solution. The newer lib is required for other things like TLS >1.0 connections.

@djib123456

This comment has been minimized.

Copy link
Author

commented Jul 4, 2019

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 4, 2019

Just tried some newer libmysql libraries:

  • libmysql.dll from server 5.7.26 - same problems as libmariadb.dll with a 4.0 server
  • libmysql.dll from C Connector 6.1.11 - same problems

I suppose #677 is the way to go - or even some approach which detects the server version automatically.

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 5, 2019

The next build has a library dropdown on the session manager, so you can select the right dll from there, if the default one (libmariadb.dll) does not work.

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 5, 2019

@djib123456 could you please update to the latest build and check if your connection works, after selecting "libmysql.dll" in the new "Library" dropdown on the session manager?

@djib123456

This comment has been minimized.

Copy link
Author

commented Jul 8, 2019

I just tried and it is working when I choose "libmysql.dll", thank you for your quick fix

@ansgarbecker ansgarbecker removed the needs-info label Jul 8, 2019

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 8, 2019

Great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.